A
licenseB
qualityB
maintenanceMCP server that enables AI assistants to create, parse, render, and validate Draw.io diagrams programmatically.
14
2
MIT
@archsmith/mcp-server
by ayeshLK
Related Servers
Alternatives to @archsmith/mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceThis MCP server enables AI agents to compose, revise, inspect, repair, and export editable hand-drawn diagrams as SVG, PNG, JPG, WebP, or PDF from JSON.23Elastic 2.0
- FlicenseAqualityBmaintenanceAn MCP server that generates standalone SVG architecture diagrams from text descriptions, running entirely on your machine with no dependencies or network access.8-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to manage STAR-pattern architecture diagrams, creating, updating, listing, and building interactive viewers via tool calls.MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for generating architecture diagrams with official vendor icons from natural language descriptions. Provides tools to validate specs, render diagrams, search icon catalog, and list available services.4MIT
- AlicenseAqualityDmaintenanceAn MCP server that lets agents draw 18 diagram types from JSON (no SVG, no headless browser)220 npm10MIT
TDQS
A4.1/5.0
Scored across 5 tools
Disambiguation5/5
Each tool has a clearly distinct role: get_schema provides the structural contract, list_registries/get_registry provide governed vocabulary, validate checks conformance, and render produces SVG. The descriptions explicitly distinguish schema (structure) from registry (vocabulary) and clarify that render subsumes validation, preventing misselection.
Naming Consistency4/5
Three tools use verb_noun (get_schema, list_registries, get_registry) while two use bare action verbs (validate, render). The split is logical—retrieval uses get/list, actions use bare verbs—but it is not a single uniform pattern, so it falls short of perfect consistency.
Tool Count5/5
Five tools map cleanly onto the core workflow: discover the schema, discover registries, validate, and render. Each tool earns its place with no redundancy, fitting comfortably in the well-scoped 3-15 range.
Completeness4/5
The surface covers the full author-validate-render lifecycle, including registry listing and lookup, so agents can complete the primary task. Minor gaps exist: no example IR or starter template, and no alternative export formats or render-option introspection beyond what render's description mentions.
Maintenance
ActivityActive
ResponsivenessResponsive