F
licenseA
qualityB
maintenanceAn MCP server that generates standalone SVG architecture diagrams from text descriptions, running entirely on your machine with no dependencies or network access.
8
-
fusion-svg-mcp
by aintoniodev
Related Servers
Alternatives to fusion-svg-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceAn MCP server that generates beautiful Excalidraw architecture diagrams with perfect auto-layout, stateful editing, and architecture-aware component styling.26313 PyPI151MIT
- FlicenseAqualityCmaintenanceMCP server for generating and editing architecture diagrams from natural language or code, supporting formats like Terraform, docker-compose, Kubernetes, SQL, Mermaid, and PlantUML.2-
- AlicenseBqualityBmaintenanceMCP server that enables LLMs to create and edit draw.io diagrams using high-level intent commands, with automatic layout and styling.45 npm4MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for rendering Mermaid diagrams to SVG and converting Markdown with callout blocks into styled PDF reports.MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that generates Mermaid diagrams with live browser preview, supports real-time rendering and SVG/PNG export.12-
TDQS
A3.5/5.0
Scored across 5 tools
Disambiguation4/5
Most tools are clearly distinct: list vs generate vs preview operations. However, generate_diagram and generate_all_fork_diagrams overlap somewhat in purpose (both generate diagrams to disk), distinguished mainly by count. preview_diagram, list_diagrams, and list_style_tokens are clearly distinct.
Naming Consistency4/5
Names follow a consistent verb_noun pattern (list_, generate_, preview_). The pattern is consistent throughout; generate_all_fork_diagrams is slightly longer/more specific but still fits the pattern. All snake_case, consistent verb-first style.
Tool Count5/5
Five tools is a well-scoped count for an SVG diagram generator MCP server. Each tool serves a clear role: discovery (list_diagrams), style reference (list_style_tokens), single generation, bulk generation, and in-memory preview. No redundancy or bloat.
Completeness3/5
The surface covers the core lifecycle: list available diagrams, inspect style tokens, generate (single and all), and preview without writing. Minor gaps include no delete/cleanup tool and no way to configure output beyond outDir, but the main generate workflow is complete.
Maintenance
ActivitySlowing
ResponsivenessNo issues