Give your AI coding agent an architecture canvas to design and evolve diagrams.
Composer MCP Server (io.github.OliverGrabner/composer)
This MCP server provides an “architecture canvas” for AI coding agents to design, visualize, and evolve software architecture diagrams from within an IDE.
🛠️ Key Features
Architecture canvas for diagram design
Visualization and ongoing evolution of software architecture diagrams
🚀 Use Cases
Creating and updating software architecture diagrams while working in an IDE
Using diagram workflows as part of AI-assisted coding tasks
⚡ Developer Benefits
Enables AI coding agents to work with architecture diagrams in the same development environment
⚠️ Limitations
Available source material does not specify supported diagram formats, tool names, or any additional capabilities beyond design/visualize/evolve.
Give your AI coding agent an architecture canvas.
Design, visualize, and evolve software architecture diagrams - right from your IDE.
Composer is a visual system design tool that lets AI coding agents create and modify interactive architecture diagrams through MCP (Model Context Protocol). Your agent gets tools to add services, databases, queues, and connections, and you get a live canvas at usecomposer.com that updates in real-time.
code
Your IDE <--> MCP Server (this package) <--> Composer API <--> Your Diagram
Getting Started
Connect your IDE
Claude Code:
bash
claude mcp add --transport http composer https://mcp.usecomposer.com
Cursor — create .cursor/mcp.json in your project root:
Scans your repo and builds the architecture diagram
"Create a new Composer diagram called Backend Architecture"
Creates and auto-selects a new diagram
"Add a Redis cache between the API and the database in Composer"
Adds a new node and edges to the diagram
"Add analytics monitoring to the Composer diagram"
Adds observability nodes and connections
"Update the APIs I defined in Composer"
Refreshes endpoint definitions on backend nodes
"Verify my Composer diagram"
Checks for missing endpoints, orphaned nodes, etc.
"Link each Composer node to its source code"
Associates diagram nodes with file paths
How It Works
Authentication is handled via OAuth 2.1 — your browser opens for a one-time consent flow, and you're connected. Tool calls are proxied to the Composer API at mcp.usecomposer.com. Your diagram data lives on Composer's servers. The MCP server itself is stateless.
Changes made through MCP are immediately visible on the Composer canvas via real-time WebSocket sync.
Development
bash
git clone https://github.com/olivergrabner/composer-mcp
cd composer-mcp
npm install
npm run dev # Watch mode (rebuilds on change)
npm run build # Production build