by BV-Venky
Turn your architecture into a living, queryable knowledge graph - and render it as beautiful auto-laid-out Excalidraw diagrams. An MCP server for Cursor, Claude Code & Windsurf. Offline, no API keys.
# Add to your Claude Code skills
git clone https://github.com/BV-Venky/excalidraw-architect-mcpGuides for using mcp servers skills like excalidraw-architect-mcp.
Last scanned: 6/9/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-06-09T07:48:54.355Z",
"npmAuditRan": true,
"pipAuditRan": true
}See how excalidraw-architect-mcp compares with popular alternatives.
excalidraw-architect-mcp is an open-source mcp servers skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by BV-Venky. Turn your architecture into a living, queryable knowledge graph - and render it as beautiful auto-laid-out Excalidraw diagrams. An MCP server for Cursor, Claude Code & Windsurf. Offline, no API keys. It has 150 GitHub stars.
Yes. excalidraw-architect-mcp passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/BV-Venky/excalidraw-architect-mcp" and add it to your Claude Code skills directory (see the Installation section above).
excalidraw-architect-mcp is primarily written in Python. It is open-source under BV-Venky on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other MCP Servers skills you can browse and compare side by side. Open the MCP Servers category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh excalidraw-architect-mcp against similar tools.
No comments yet. Be the first to share your thoughts!
Top skills in this category by stars
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
See comparison
Every diagram your engineering docs need — as hand-drawn Excalidraw, generated by your AI.
Twenty-five diagram types. Architecture and flowcharts, but also sequence diagrams, state machines, ER models, swimlanes, timelines, Gantt charts, quadrants, funnels, and hand-sketched bar/line/scatter charts. No coordinates to hallucinate, no Figma, no stale PNGs.
When you're onboarding onto a codebase, designing a new system, or documenting how something works, a diagram communicates in seconds what pages of text can't. But the options aren't great.
Mermaid is quick to generate and locked down — you can't drag a node, group things visually, or annotate it afterwards. Figma means thirty minutes of manual work per picture. And when an LLM writes Excalidraw JSON directly it hallucinates coordinates: boxes overlap, arrows tangle, and you fix it by hand.
Worse, most tools only cover one diagram type well. The moment your doc needs a sequence diagram next to the architecture sketch, you're switching tools and the two look nothing alike.
excalidraw-architect-mcp separates the what from the where — the AI describes structure, the engine does the pixel math.
Your LLM says what the components, actors, tiers, or data points are. The MCP picks the layout algorithm for that diagram type, styles it, and writes a real .excalidraw file you can open and keep editing. 50+ technologies (Kafka, PostgreSQL, Redis…) get auto-styled, every diagram can be revised in natural language, and it runs fully offline in Cursor/Claude Code/Windsurf — no API keys.
Every image below is a real
.excalidrawfile generated by this MCP — zero manual positioning. Click any one to see it full size.
The gallery above is ordered by how often you'll reach for each type. Internally they fall into five families, which is what decides the layout engine:
| Family | Types |
|---|---|
| Graph | architecture · flowchart |
| Structural | tree · org_chart · state · nested · layers · medallion · er · high_level · it_state |
| Flow | swimlane · process · data_flow · dp_integration · sequence |
| Geometric | timeline · quadrant · pyramid (+ funnel) · venn · loop · gantt |
| Charts | bar · line · scatter |
architecture and flowchart are graphs and take nodes + connections. Every other type takes a diagram_type and a spec shaped for it:
create_diagram(
output_path="./checkout.excalidraw",
diagram_type="sequence",
spec={
"title": "Checkout authorization",
"actors": [{"id": "web", "label": "Web app"}, {"id": "psp", "label": "Payment PSP"}],
"messages": [
{"from_id": "web", "to_id": "psp", "label": "authorize"},
{"from_id": "psp", "to_id": "web", "label": "approved",
"kind": "return", "focal": True},
],
},
)
Call list_diagram_types() for when-to-use guidance on each, and get_diagram_schema("<type>") for the exact spec shape. Or just ask: "draw the PR review flow as a swimlane".
Two conventions worth knowing. Mark one or two elements "focal": true — that earns the accent color,