F
licenseNot graded
qualityF
maintenanceEnables AI assistants to create, read, and manage Draw.io diagrams programmatically through natural language interactions.
1
-
drawio-mcp
by abossard
Related Servers
Alternatives to drawio-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to create and edit draw.io diagrams programmatically, supporting a wide range of diagram types and styles.5MIT
- AlicenseAqualityDmaintenanceEnables AI agents to generate and edit draw.io diagrams with real-time browser preview.521 npmApache 2.0
- AlicenseAqualityCmaintenanceEnables AI agents to edit diagram/graph structures on a live draw.io canvas and manage local versions via snapshots, restore, and export without embedding a separate LLM or polluting the workspace.7MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to generate professional UML diagrams (class, use case, activity, sequence) from natural language descriptions, producing editable .drawio files compatible with diagrams.net.753 npmISC
diag2md-mcpofficial
AlicenseAqualityBmaintenanceEnables AI coding agents to discover, convert, and synchronize Draw.io C4 and UML diagrams into Mermaid Markdown, providing architectural context and guardrails during chat sessions.315 npmMIT
TDQS
A3.8/5.0
Scored across 21 tools
Disambiguation4/5
Most tools have distinct purposes, but some overlap exists among visual feedback tools (highlight_element, show_ai_selection, show_ai_cursor) and between add_node/add_edge vs batch_add_elements. Description text clarifies these, but an agent might initially confuse them.
Naming Consistency5/5
Nearly all tools follow a clear verb_noun snake_case pattern (e.g., create_diagram, read_diagram, add_node, update_element, check_layout, undo_last_operation). Verbs are descriptive and consistent across the set.
Tool Count4/5
21 tools is on the higher end but justified for a full-featured diagram editor covering file management, element CRUD, layout, UI feedback, and history. The count feels purposeful rather than bloated.
Completeness4/5
The tool surface covers core diagram lifecycle (create, read, update, delete, batch) plus layout, history, and visual feedback. Minor gaps like missing delete_page or get_single_element exist, but read_diagram and update_element work around them.
Maintenance
ActivityInactive
ResponsivenessNo issues