diagram-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 |
|---|---|
| render_mermaidA | Render a Mermaid diagram to SVG, PNG, JPG, or PDF format with comprehensive styling and output options. Output options:
Examples:
|
| render_plotlyA | Render a Plotly chart to SVG, PNG, JPG, or PDF format with comprehensive styling and output options. Output options:
Examples:
Plotly Code Example: Plotly.newPlot('plotly-chart', [{ x: [1, 2, 3, 4, 5], y: [1, 2, 4, 8, 16], type: 'scatter' }], { margin: { t: 0 } }); |
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 2 tools
The two tools serve clearly distinct purposes: one renders Mermaid diagrams, the other renders Plotly charts. There is no overlap in functionality, so an agent can easily select the correct tool based on the desired output type.
Both tools follow a consistent 'render_' prefix naming pattern, clearly indicating their action and distinguishing them by the library they support (mermaid vs plotly). This makes the naming predictable and easy to understand.
With only two tools, the count is on the lower side but appropriate for a server focused on rendering two distinct visualization libraries. Each tool is justified by the different input formats and rendering engines, so the count feels reasonable for the scope.
The server covers the core functionality for rendering diagrams from two popular libraries. While it could include additional libraries or a generic render tool, the current set is sufficient for its stated purpose and has no obvious gaps in the rendering workflows.