visio-mcp
Related Servers
Alternatives to visio-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI clients to create, edit, read, and export Microsoft Visio diagrams via COM automation on Windows.262MIT
- AlicenseNot gradedqualityFmaintenanceEnables to create and edit Microsoft Visio diagrams programmatically via a standardized API.305 PyPI86MIT
- AlicenseNot gradedqualityBmaintenanceA local-first toolkit that rebuilds reference images as editable Microsoft Visio shapes via two MCP servers for image QA and Visio COM rendering.5Apache 2.0
- FlicenseNot gradedqualityDmaintenanceConnects Claude to Microsoft Visio to generate enterprise architecture diagrams from natural language or structured inventory data, supporting multiple diagram types and export formats.4-
- FlicenseNot gradedqualityDmaintenanceEnables creating and managing UML diagrams in Sparx Systems Enterprise Architect via COM interface, supporting sequence, class, use case, and activity diagrams.4-
- AlicenseNot gradedqualityDmaintenanceEnables creation of Azure architecture diagrams from natural language descriptions, generating PNG images automatically.MIT
TDQS
Scored across 23 tools
Each tool targets a distinct resource/action: document lifecycle, stencil discovery, shape placement, container management, styling, layout, and export. Even related pairs like drop_shape/drop_shapes or add_container/badge_container are cleanly separated by singular-vs-multiple or create-vs-badge semantics. An agent should be able to select the right tool reliably.
Most tools follow a clear verb_noun pattern (create_document, save_document, open_stencil, connect_shapes, set_page_size). A few noun-style names deviate (visio_status, pages, container_members, auto_layout), but the overall convention is readable and predictable.
23 tools is on the heavy side for a single server, fitting the '16-25 feels heavy' range. The breadth is understandable given the full Visio authoring workflow, but the count is borderline rather than clearly well-scoped.
The tool surface covers the complete diagram-building lifecycle: stencil discovery, document/page setup, shape placement, text/images, containerization, connection, styling, layout, and PNG export. Missing operations like close_document or undo are not essential to the stated purpose. There are no obvious dead ends for creating and editing diagrams.