A
licenseNot graded
qualityC
maintenanceEnables creating and editing Draw.io diagrams via natural language, supporting shapes, connectors, and multi-line text.
2
MIT
mcp-drawio-server
Related Servers
Alternatives to mcp-drawio-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables creating and editing draw.io diagrams from structured descriptions, rendering them as interactive inline SVGs, and providing access to the full draw.io editor for further modification and export.757 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read and edit entity-relationship diagrams and SQL database schemas on the liz-whiteboard collaborative whiteboard through natural language, supporting table, column, and relationship management.MIT
- FlicenseAqualityCmaintenanceEnables local creation and maintenance of editable draw.io XML diagram files, with tools for inspecting, validating, and updating diagrams.5-
- AlicenseAqualityDmaintenanceParses Mermaid ER diagrams to create PostgreSQL tables and automatically generates REST and GraphQL CRUD APIs.12MIT
- AlicenseBqualityAmaintenanceEnables generating editable draw.io architecture diagrams from system descriptions, with automatic ELK layout, official icons, layered views, and objective quality scoring.11MIT
TDQS
A3.5/5.0
Scored across 16 tools
Disambiguation5/5
Each tool targets a distinct action and resource: loading schemas from different sources, opening/listing/describing diagrams, and CRUD operations for tables, columns, and relations. Manual positioning and automatic relayout are clearly separated, so there is no ambiguity between tools.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in lowercase snake_case (e.g., load_database_schema, add_table, remove_relation). Minor pluralization in list_diagrams is the only deviation, and it does not affect the predictable pattern.
Tool Count4/5
At 16 tools, the set is slightly above the typical 3-15 range, but each tool serves a distinct and necessary purpose in the schema-diagram workflow. The count feels well-scoped without redundant tools, though it could be tightened slightly.
Completeness4/5
The server covers the full lifecycle: loading/opening diagrams, listing/describing them, adding/removing tables/columns/relations, positioning, saving, and exporting. Minor gaps exist, such as no update/rename operations for tables or columns and no explicit close-diagram tool, but these are workable around.
Maintenance
ActivityStale
ResponsivenessNo issues