fusion-svg-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_style_tokensA | Return the color palette, glyphs, font stack, and structural rules extracted from the original Disler fusion-harness SVGs. |
| list_diagramsA | List diagram ids the generator can produce (svg-07..svg-12), with reference originals and descriptions. |
| preview_diagramA | Generate a diagram in memory and return the SVG markup (does not write to disk). |
| generate_diagramC | Generate one Disler-style diagram and write it under the images/ directory (or --outDir). |
| generate_all_fork_diagramsB | Generate svg-07 through svg-12 into images/ (or outDir). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
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.
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.
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.
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.