
Composer
Give your coding agent a live architecture canvas to create and revise system diagrams while you design the product.
Overview
Composer is an MCP server for the Build phase that provides an architecture canvas for AI coding agents to design and evolve diagrams.
What is this MCP server?
- stdio MCP via npx @usecomposer/mcp (v0.1.7)
- Architecture canvas the agent can design and evolve interactively
- Purpose-built for AI coding agents planning system structure
- Lightweight npm package from olivergrabner/composer-mcp on GitHub
- Diagram-first workflow instead of one-off ASCII sketches in chat
- npm package version 0.1.7
- stdio transport via @usecomposer/mcp
- Single-package MCP registry entry from composer-mcp repository
Community signal: 3 GitHub stars.
What problem does it solve?
Solo builders struggle to keep system diagrams current when the agent only produces fleeting text or ASCII in the chat window.
Who is it for?
Builders using Claude Code or Cursor who want agent-driven C4-style or system diagrams without leaving the MCP workflow.
Skip if: Teams needing polished product design mockups, slide decks, or non-technical stakeholder branding work.
What do I get? / Deliverables
After adding Composer, your agent can maintain an evolving architecture canvas that stays aligned with design conversations and code changes.
- Agent-maintained architecture diagrams on the Composer canvas
- Iterative visual updates as components and integrations change
- Shareable structural view alongside your codebase
Recommended MCP Servers
Journey fit
Architecture diagrams are created while you are building and explaining structure, so Build is the natural home for a composer-style canvas MCP. Docs subphase captures visual architecture artifacts that accompany code, ADRs, and onboarding material for a solo shipped product.
How it compares
Agent-facing architecture canvas MCP, not a generic whiteboard SaaS or documentation skill.
Common Questions / FAQ
Who is Composer for?
Composer is for solo developers and agent users who want their coding assistant to draw and update architecture diagrams on a dedicated canvas.
When should I use Composer?
Use it during Build when you are shaping services, data flows, or module boundaries and want diagrams the agent can revise as the design changes.
How do I add Composer to my agent?
Add a stdio MCP entry that runs npx @usecomposer/mcp per the registry package, then restart your Claude Code or Cursor MCP configuration.