DrawArch MCP
Related Servers
Alternatives to DrawArch MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables generating editable draw.io architecture diagrams from system descriptions, with automatic ELK layout, official icons, layered views, and objective quality scoring.11MIT
- AlicenseAqualityDmaintenanceGenerates professional architecture diagrams from natural language descriptions using template-driven prompts and swappable AI image providers.72MIT
- AlicenseNot gradedqualityDmaintenanceGenerates editable Excalidraw diagram files from natural language descriptions of systems and architectures.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables creation of Azure architecture diagrams from natural language descriptions, generating PNG images automatically.MIT
- AlicenseAqualityBmaintenanceGenerates, reviews, and imports cloud architecture diagrams for AWS, Azure, and Google Cloud from editable specs, Terraform, or live Google Cloud inventory, rendering them as PNG, SVG, PDF, or JPG.101Apache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables users to generate and revise 25 types of hand-drawn Excalidraw diagrams—including architecture, flowcharts, sequence, ER, Gantt, and charts—from natural-language specs without managing coordinates. It can also persist architecture as a queryable, version-controlled knowledge graph and export offline to SVG or PNG.-
TDQS
Scored across 11 tools
Each tool has a distinct purpose, but the paired create/validate tools for general drawio vs reference recreations (create_drawio/create_reference_drawio, validate_drawio/validate_reference_drawio) require careful reading of descriptions to avoid confusion. Otherwise, the reference plan lifecycle tools are clearly separated.
All tools follow a consistent verb_noun snake_case pattern (list_themes, resolve_asset, create_drawio, get_reference_plan, compare_reference_recreation). The pattern is uniform and predictable.
11 tools is appropriate for a server covering two related workflows (general diagram generation and reference-based recreation). Each tool has a clear role, and the count is within the ideal range.
The tool surface covers the full lifecycle for both workflows: asset/theme discovery, diagram creation and validation, and reference plan preparation, revision, rendering, and comparison. Minor gaps like no delete/update for general drawio files are acceptable given the server's purpose.