BV-Venky/excalidraw-architect-mcp
aware component styling, and stateful editing. 50+ technology mappings including databases, message queues, caches, and more. No API keys required.
Ask AI about BV-Venky/excalidraw-architect-mcp
Powered by Claude · Grounded in docs
I know everything about BV-Venky/excalidraw-architect-mcp. Ask me about installation, configuration, usage, or troubleshooting.
0/500
Reviews
Documentation
Excalidraw Architect MCP
An MCP server that generates beautiful Excalidraw architecture diagrams with perfect auto-layout, stateful editing, and architecture-aware component styling.
No API keys. No local models. Works with any AI IDE that supports MCP (Cursor, Windsurf, Antigravity etc.).
The Problem
AI IDEs/LLMs generate diagrams as Mermaid or ASCII art. When they try Excalidraw, they hallucinate coordinates - boxes overlap, arrows cross, and the result needs manual cleanup.
The Solution
Tell the AI what to draw. This MCP handles where and how.
- Perfect layouts every time - Sugiyama algorithm with adaptive spacing; no overlapping boxes
- Architecture-aware styling - Say "Kafka" and get a stream-styled node, not a generic rectangle
- Talk to your diagrams - Add, remove, or rewire components on an existing diagram with natural language
- Hub node visualization - Gateways and load balancers auto-stretch to span their connected services
See It In Action
Every frame below is generated entirely by AI using this MCP -- zero manual positioning.
E-Commerce Platform Architecture

Payment Processing Flow

Quick Start
Install
pip install excalidraw-architect-mcp
Or run without installing (requires uv):
uvx excalidraw-architect-mcp
Configure MCP in Your IDE
Cursor - Add to .cursor/mcp.json:
{
"mcpServers": {
"excalidraw-architect": {
"command": "excalidraw-architect-mcp",
"transport": "stdio"
}
}
}
Windsurf / Other IDEs - Same pattern; point to the excalidraw-architect-mcp command over stdio.
Install the Diagram Design Skill (recommended)
This repo includes a Diagram Design Skill that teaches the AI how to structure diagrams for the best results -- node count limits, topology rules, edge label guidelines, and common patterns.
For Cursor users:
mkdir -p ~/.cursor/skills/excalidraw-diagram-design && \
curl -o ~/.cursor/skills/excalidraw-diagram-design/SKILL.md \
https://raw.githubusercontent.com/BV-Venky/excalidraw-architect-mcp/main/.skills/excalidraw-diagram-design/SKILL.md
For other IDEs: Download the SKILL.md file and add it to your IDE's prompt context or system instructions.
The AI will automatically pick up the skill and apply it when generating diagrams. Feel free to modify the rules to suit your preferences -- tweak node limits, add your own patterns, or adjust styling guidelines.
A note on diagram complexity: As the number of components and connections grows, diagrams inevitably become harder to read -- this is true for humans drawing by hand too, not just automated layout. For best results, aim for 6-15 nodes in architecture diagrams and 10-25 nodes in detailed flows. If your system is larger, split it into multiple focused diagrams rather than cramming everything into one.
Use It
Just ask your AI IDE naturally:
"Create a High Level architecture diagram of this codebase"
"Create an architecture diagram for a microservices system with an API Gateway, Auth Service, User Service, Order Service, PostgreSQL, Redis cache, and Kafka event bus"
"Convert this mermaid diagram to excalidraw diagram"
"Add a Caching layer to the Order Service in the High Level architecture diagram"
The AI calls the MCP tool with the relationship map. The MCP handles layout, styling, and output. Open the resulting .excalidraw file with the Excalidraw VS Code extension or drag it into excalidraw.com.
Features
Auto Layout Engine
Uses the Sugiyama hierarchical layout algorithm with:
- Adaptive layer gaps - spacing adjusts based on edge label length
- Hub node stretching - gateways/load balancers stretch to span connected services
- Obstacle-aware edge routing - arrows curve around intermediate nodes instead of cutting through them
- Disconnected component stacking - separate subgraphs (e.g., monitoring stack) are placed without overlap
Component Library
50+ technology mappings with automatic visual styling:
| Category | Technologies |
|---|---|
| Database | PostgreSQL, MySQL, MongoDB, DynamoDB, Cassandra, ClickHouse, SQLite, CockroachDB |
| Message Queue | Kafka, RabbitMQ, SQS, Redis Streams, NATS |
| Cache | Redis, Memcached, Varnish |
| Load Balancer | Nginx, HAProxy, ALB/ELB, Traefik, Envoy |
| Compute | Docker, Kubernetes, Lambda, ECS, Fargate |
| Storage | S3, GCS, Azure Blob, MinIO |
| API | REST, GraphQL, gRPC, WebSocket |
| CDN | CloudFront, Cloudflare |
| Monitoring | Prometheus, Grafana, Datadog, ELK |
| Client | Browser, Mobile, Desktop, CLI |
Stateful Editing
Diagram metadata is embedded in the .excalidraw file. Ask the AI:
"Add a Redis cache in front of the database in the existing diagram"
The MCP reads the current state, applies the modification, and re-renders with proper layout.
Mermaid Conversion
Already have a Mermaid flowchart? Convert it:
"Convert this Mermaid diagram to Excalidraw" (paste your Mermaid syntax)
MCP Tools
| Tool | Description |
|---|---|
create_diagram | Create a new diagram from structured node/connection data |
mermaid_to_excalidraw | Convert Mermaid flowchart syntax to .excalidraw |
modify_diagram | Add/remove/update nodes and connections on an existing diagram |
get_diagram_info | Read current diagram state (call before modifying) |
Contributing
See CONTRIBUTING.md for details.
License
MIT - see LICENSE.
