diagram-studio-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KROKI_URL | No | Optional: KROKI_URL (default https://kroki.io) | https://kroki.io |
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_diagramA | Renderiza source con Kroki. Engines: mermaid, graphviz (DOT), plantuml, d2, erd. Devuelve path del archivo y base64 (recortado en text si es grande). |
| list_enginesB | Engines soportados y URL de Kroki. |
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 have entirely distinct roles: rendering diagrams versus listing supported engines. No overlap in purpose.
Both tools follow a clear verb_noun pattern (render_diagram, list_engines), making the API predictable.
With only two tools, the server feels minimal but appropriate for a narrow scope; however, it borders on thin for a typical server.
The core rendering capability is present alongside engine information, but additional conveniences like validation or format conversion are absent.