excalidraw-mcp
Related Servers
Alternatives to excalidraw-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceGenerates editable Excalidraw diagram files from natural language descriptions of systems and architectures.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to build, edit, organize, and export Excalidraw diagrams (architecture, flowcharts, etc.) entirely headless, producing .excalidraw files, SVG, and PNG renders.2,955 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables generating Excalidraw architecture diagrams from a topology spec, with automatic layout, styling, and export to .excalidraw, SVG, and PNG files.159 npmMIT
- AlicenseAqualityDmaintenanceGenerates Excalidraw architecture diagrams with support for 60+ components including GCP, Kafka, and AI/Agentic shapes. Provides MCP tools for creating, modifying, and converting diagrams from structured input or Mermaid syntax.41MIT
- AlicenseNot gradedqualityAmaintenanceThe diagram-quality layer for AI agents — an opinionated Excalidraw methodology (isomorphism test, evidence artifacts, multi-zoom, container discipline) plus a render-view-fix loop. Accepts skeleton and Mermaid input, 5 publishable themes, dual Node/Python renderer. Proven on a 77-diagram published book.4MIT
- FlicenseAqualityBmaintenanceGenerates beautiful Excalidraw diagrams from natural language descriptions using a local llama.cpp LLM, entirely offline.3-
TDQS
Scored across 28 tools
Most tools are clearly separated by diagram type (flowchart, sequence, ER, etc.), but there is meaningful overlap: import_mermaid subsumes import_mermaid_flowchart, create_diagram duplicates every create_* tool, and several tree-like diagram tools (flowchart, org chart, mindmap, decision tree) could be confused for generic hierarchy requests. Descriptions help, but the boundaries are not always crisp.
The create_<diagram_type> convention is consistent and predictable across the majority of tools, making the set easy to scan. Minor deviations include import_mermaid vs. import_mermaid_flowchart, the generic create_diagram, and a few names like create_swot_analysis that break the diagram suffix pattern.
28 tools is on the heavy side, though the breadth of diagram types partially justifies it. The count is inflated by redundancy: import_mermaid_flowchart is largely subsumed by import_mermaid, create_diagram duplicates all specialized creators, and list_diagram_types is a metadata helper rather than a core operation.
The server covers a wide range of diagram creation plus modify, read, export, and Mermaid import, so most user workflows have a path to completion. Minor gaps exist around full edit fidelity—modify_diagram only supports adding/removing nodes and connections, not arbitrary repositioning or restyling—and there is no support for importing other diagram formats.