Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
6,000+ web scrapers for your AI agent, start free logo6,000+ web scrapers for your AI agent, start free

Apify gives your agent live web data: 6,000+ prebuilt scrapers and actors, MCP-ready. Sign up free with $5 in usage credits.

Try Apify free
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 48,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

Give your AI coding agent an architecture canvas to design and evolve diagrams.

README.md

<p align="center"> <img src="https://github.com/OliverGrabner/composer-mcp/raw/main/demo.gif" alt="Composer demo" /> </p>

<p align="center"> <img src="https://usecomposer.com/logo_warm_trio_no_bg.svg" width="14" alt="Composer logo" /> <strong>Composer MCP Server</strong> </p>

<p align="center"> Give your AI coding agent an architecture canvas.<br/> Design, visualize, and evolve software architecture diagrams - right from your IDE. </p>

<p align="center"> <a href="https://www.npmjs.com/package/@usecomposer/mcp"><img src="https://img.shields.io/npm/v/@usecomposer/mcp?color=D27754&label=npm" alt="npm version" /></a> <a href="https://opensource.org/licenses/MIT"><img src="https://img.shields.io/badge/license-MIT-blue.svg" alt="MIT License" /></a> <a href="https://modelcontextprotocol.io"><img src="https://img.shields.io/badge/MCP-compatible-green.svg" alt="MCP Compatible" /></a> </p>

---

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.

Your IDE  <-->  MCP Server (this package)  <-->  Composer API  <-->  Your Diagram

Getting Started

Connect your IDE

Claude Code:

claude mcp add --transport http composer https://mcp.usecomposer.com

Cursor — create .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "composer": {
      "type": "http",
      "url": "https://mcp.usecomposer.com"
    }
  }
}

Your browser will open for authorization on first use.

<details> <summary><strong>Claude Code</strong></summary>

claude mcp add --transport http composer https://mcp.usecomposer.com

</details>

<details> <summary><strong>Cursor</strong></summary>

Create .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "composer": {
      "type": "http",
      "url": "https://mcp.usecomposer.com"
    }
  }
}

</details>

<details> <summary><strong>Codex</strong></summary>

codex mcp add composer -- npx -y @usecomposer/mcp --stdio

</details>

<details> <summary><strong>VS Code (Copilot Chat)</strong></summary>

Create .vscode/mcp.json in your project root:

{
  "servers": {
    "composer": {
      "type": "http",
      "url": "https://mcp.usecomposer.com"
    }
  }
}

</details>

<details> <summary><strong>VS Code (Cline)</strong></summary>

Open Cline sidebar > Settings (gear icon) > MCP Servers > Add Remote Server:

{
  "mcpServers": {
    "composer": {
      "type": "http",
      "url": "https://mcp.usecomposer.com"
    }
  }
}

</details>

<details> <summary><strong>VS Code (Continue)</strong></summary>

Add to .continue/config.yaml:

mcpServers:
  - name: composer
    url: https://mcp.usecomposer.com

</details>

<details> <summary><strong>Windsurf</strong></summary>

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "composer": {
      "serverUrl": "https://mcp.usecomposer.com"
    }
  }
}

Note: Windsurf uses "serverUrl" instead of "url".

</details>

<details> <summary><strong>OpenCode</strong></summary>

Create opencode.json in your project root:

{
  "mcp": {
    "composer": {
      "type": "remote",
      "url": "https://mcp.usecomposer.com"
    }
  }
}

</details>

Tools

Diagram Management

| Tool | Description | |------|-------------| | list_diagrams | List all your diagrams. Call this first to find which diagram to work on | | create_diagram | Create a new diagram and auto-select it for this session | | select_diagram | Select which diagram to work on for this session | | rename_diagram | Rename the currently selected diagram |

Note: Call list_diagrams then select_diagram (or create_diagram) before using other tools.

Read

| Tool | Description | |------|-------------| | get_graph | Get the full architecture diagram - all nodes and edges | | get_node | Get details for a single node including connected edges | | search_graph | Search nodes and edges by keyword | | get_screenshot | Get a PNG thumbnail of the diagram from the last auto-save |

Write

| Tool | Description | |------|-------------| | upsert_node | Create or update a node (service, database, queue, etc.) | | upsert_edge | Create or update a connection between two nodes | | define_api | Define API endpoints on a backend service node | | delete_element | Delete a node or edge from the diagram | | link_path | Link a node to a file or folder in your codebase |

Plan & Verify

| Tool | Description | |------|-------------| | verify_diagram | Check for issues like missing endpoints or orphaned nodes | | plan_import | Step-by-step workflow for importing an existing codebase | | get_guide | Reference guide for node types, protocols, and best practices |

Node Types

client · frontend · backend · database · cache · queue · storage · external

Edge Protocols

REST · gRPC · GraphQL · WebSocket · TCP · UDP · async · event · internal

Example Prompts

Once connected, try asking your AI agent:

| Prompt | What it does | |--------|-------------| | "Import this codebase into Composer" | 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

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

Links

License

MIT

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use AI & ML servers.