Skip to main content

Docs MCP Overview

The ART MCP (Model Control Protocol) Server extends the ART platform into AI-powered development workflows.

By connecting an MCP-compatible AI assistant in your IDE to the ART MCP Server, the assistant gains structured access to ART’s real-time capabilities. This allows ART systems to be designed, generated, and refined directly from the editor using natural language.

MCP is not a separate product. It is part of how ART can be used and interacted with during development.

Why Use ART MCP in Your IDE?

ART provides real-time communication primitives such as channels, presence, security controls, orchestration, and agents. MCP exposes these capabilities to AI assistants in a controlled and predictable way.

With ART MCP enabled in your IDE, you can:

  • Design real-time systems using prompts instead of manual wiring
  • Generate ART-aligned code and configuration inside the editor
  • Explore ART features interactively without switching tools
  • Iterate on architecture and behaviour while staying within ART’s platform model

This makes ART usable earlier in the development cycle and easier to reason about during iteration.

What ART MCP provides to your IDE

The ART MCP Server exposes ART knowledge and tools that AI assistants can use during generation, including:

  • Understanding of ART primitives such as channels, presence, interceptors, orchestration, and agents
  • Access to ART documentation and feature metadata
  • Guidance for generating code using ART ADKs across supported languages
  • Platform-consistent behaviour across IDEs and assistants

The goal is not generic code generation, but ART-specific system generation.

How ART MCP works inside the IDE

ART MCP acts as a bridge between the AI assistant and the ART platform.

1. MCP tool manifest

The MCP Server exposes a manifest that defines ART-specific tools and capabilities available to the assistant.

2. Prompt-driven interaction

When you prompt the assistant, it uses the MCP manifest to decide how ART features should be applied.

Example: Create a real-time collaboration flow with shared state and access rules using ART.

3. ART-aware generation

The MCP Server provides ART-specific context and structure, enabling the assistant to generate code and configurations that align with ART’s design.

4. Output inside your workflow

The assistant returns results directly in the IDE, ready to be refined, extended, or integrated into your project.

ART platform integration

Everything generated through MCP runs on the ART platform.

  • Real-time messaging and state are handled by ART
  • Security, encryption, and access control remain ART features
  • Agents operate within ART’s runtime

MCP influences how ART is used during development, not how it runs in production.

Using ART with MCP over time

ART MCP is designed to support the full development lifecycle:

  • Early exploration and system design through prompts
  • Iterative refinement of real-time flows
  • Gradual transition to deeper manual control when needed

ART remains the platform throughout. MCP simply makes it easier to work with.