excalidashapi-mcp
Related Servers
Alternatives to excalidashapi-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to create, modify, and share diagrams on a live Excalidraw canvas through MCP tools, supporting shapes, text, arrows, batch operations, and export to shareable links with images.2,213 npm8MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to create and manipulate live visual diagrams on an Excalidraw canvas in real-time via MCP tools.4,430 npm14BSD 3-Clause
- AlicenseAqualityCmaintenanceEnables MCP clients to list, select, create, summarize, and edit ExcaliDash (Excalidraw) drawings through the Drawing Agent API, supporting both stdio and Streamable HTTP transport.714 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to create, modify, and analyze diagrams using Draw.io (Diagrams.net) through MCP commands.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to collaboratively draw and annotate Excalidraw diagrams in real-time via MCP tools, synced to a browser canvas.9Apache 2.0
- FlicenseNot gradedqualityCmaintenanceMCP server that lets Claude (and other MCP clients) create, list, read, update, and delete drawings in ExcaliDash via its REST API. It allows users to create diagrams directly from natural language commands like 'draw a flowchart'.-
TDQS
Scored across 17 tools
Most tools target distinct actions and resources (drawings, collections, elements, images), and selection behavior is documented. However, get_drawing, get_drawing_summary, and get_selected_drawing require careful reading to distinguish, and find_elements versus inspect_drawing_element could overlap for some queries.
All names are snake_case and follow a predictable verb_noun pattern such as list_drawings, create_drawing, rename_collection, and delete_collection. Minor naming variation like add_image is still readable and does not break the convention.
At 17 tools, the set is slightly above the ideal 3-15 range but justified by drawing lifecycle, selection state, collection management, structural inspection, and image support. It is not excessive for the apparent domain.
The surface covers drawing CRUD, selection, summary/inspection, atomic operations, element search, collection CRUD/move, and image addition. Minor gaps remain around explicit duplication/export or detailed collection inspection, but core lifecycle coverage is solid.