MCP Integration

Archflow exposes Archie's tools via the Model Context Protocol (MCP), letting you access your architecture data and AI tools directly from your IDE or AI coding assistant.

What is MCP?

The Model Context Protocol is an open standard that allows AI assistants to connect to external tools and data sources. Archflow's MCP server gives your IDE assistant access to 100+ architecture tools --- the same tools Archie uses within the Archflow UI.

Supported Clients

MCP integration works with any MCP-compatible client, including:

• Claude Code (CLI)
• Cursor
• Windsurf
• Any other MCP-compatible IDE or tool

Setup

1. Generate an API Key

1. Open your project in Archflow
2. Go to Settings → MCP / API tab
3. Click Generate API Key
4. Copy the key (it won't be shown again)

2. Configure Your Client

The Settings page provides copy-paste configurations for each supported client.

Claude Code (CLI)

claude mcp add archflow https://your-domain.com/api/mcp \
  --transport http \
  --header "Authorization: Bearer <your-api-key>"

Claude Code / Cursor / Windsurf (JSON config)

Add to your MCP configuration file (.mcp.json or equivalent):

{
  "mcpServers": {
    "archflow": {
      "url": "https://your-domain.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <your-api-key>"
      }
    }
  }
}

The MCP server uses Streamable HTTP transport --- zero additional configuration needed beyond the URL and auth header.

Available Tools

Once connected, your IDE assistant has access to the same tool categories as Archie:

• Query tools --- Read systems, connections, workflows, deployments
• Analysis tools --- Complexity analysis, blast radius, architecture health
• Documentation tools --- Search and generate documentation
• Creation tools --- Create systems and connections (with project context)
• Arc42 tools --- Read and generate architecture profiles
• Context tools --- Context map and bounded context relationships

API Key Management

From the Settings → MCP / API tab:

• Generate new API keys
• Rotate existing keys (generates a new key and invalidates the old one)
• Revoke keys you no longer need
• View key creation date and last used timestamp

API keys are scoped to a specific project. Each project has its own set of MCP keys.

Use Cases

Architecture-Aware Coding

Ask your IDE assistant questions about your architecture while coding:

• "What systems connect to the payment service?"
• "Show me the deployment configuration for the API server"
• "What's the blast radius if I change this service's API?"

Documentation from Your IDE

Generate and update architecture documentation without leaving your editor:

• "Document this system's API contracts"
• "Update the Arc42 quality requirements section"

Architecture Governance

Verify architectural decisions against your documented architecture:

• "Does this new service follow our integration patterns?"
• "Which bounded contexts would be affected by this change?"

Next Steps