diagrams-mcp-server
Related Servers
Alternatives to diagrams-mcp-server
No user-submitted related servers found.
Related Servers
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.320 npmMIT- FlicenseNot gradedqualityAmaintenanceEnables AI coding assistants to generate, revise, and export auto-laid-out hand-drawn diagrams from architecture descriptions across many diagram types, and optionally maintain a queryable, version-controlled architecture knowledge graph.-
- FlicenseNot gradedqualityAmaintenanceEnables AI coding assistants to turn architecture descriptions into auto-laid-out, hand-drawn diagrams across 25 types, then revise them in natural language and export SVG/PNG. It can also persist and query a version-controlled architecture knowledge graph, fully offline without API keys.-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to create, read, update, and delete Draw.io diagrams, allowing automated generation of architectural diagrams, flowcharts, and visual documentation.100 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to draw interactive diagrams (architecture, sequence, class) inside the editor, with clickable nodes that jump to source code.9MIT
- AlicenseNot gradedqualityCmaintenanceEnables generating cloud architecture diagrams, flowcharts, sequence diagrams, and more using three rendering engines: mingrammer/diagrams, Mermaid, and PlantUML.44 PyPI3MIT
TDQS
Scored across 15 tools
Most tools target clearly distinct actions and resources, with strong 'use when/don't use when' guidance. The only mild overlap is among the four source-producing tools (generate, generate_sequence, scaffold, template) and the export/save_export pair, which require reading descriptions to distinguish reliably.
Every tool uses the same diagrams_ prefix and snake_case naming with predictable verb-leading names such as list, get, create, update, delete, render, diff, and generate. Even the compound names like generate_sequence and list_templates follow the same convention consistently.
Fifteen tools is well within the ideal range and each tool appears to earn its place across file CRUD, rendering, export, generation, templates, diffing, and consistency checking. There are no obviously redundant tools or missing major operations that would justify a different count.
The surface provides full lifecycle coverage for diagram files: list, get, create, update, delete, render, diff, export, save export, generate from code, generate sequence diagrams, scaffold code, and template discovery/instantiation. Minor extras like rename/move can be worked around through create/delete, and the domain is otherwise very thoroughly covered.