diagram-studio-mcp
by 0PValencia
README.md
# @0pvalencia/diagram-studio-mcp
MCP para renderizar diagramas (Mermaid, Graphviz, PlantUML, D2) vía Kroki.
## Cursor / Claude / VS Code
### Local (recomendado si clonas el repo)
```json
{
"mcpServers": {
"diagram-studio": {
"command": "node",
"args": ["/ABSOLUTE/PATH/TO/diagram-studio-mcp/dist/cli.js"]
}
}
}
```
Tras clonar: `npm install && npm run build`.
### npx (sin clonar)
```json
{
"mcpServers": {
"diagram-studio": {
"command": "npx",
"args": ["-y", "@0pvalencia/diagram-studio-mcp"]
}
}
}
```
> Si abres este repo en Cursor y usas `npx`, hace falta `npm install && npm run build` para que el bin local exista. Sin eso, `npx` falla con `diagram-studio-mcp: not found` y el MCP se queda cargando.
## Install / run
```bash
npx -y @0pvalencia/diagram-studio-mcp
```
## Local
```bash
npm install
npm run build
npm start
```
## Tools
- `render_diagram` — source + engine → PNG/SVG
- `list_engines`
Opcional: `KROKI_URL` (default `https://kroki.io`).
Opcional: `KROKI_URL` (default `https://kroki.io`).
## License
MIT
TDQS
A3.7/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have entirely distinct roles: rendering diagrams versus listing supported engines. No overlap in purpose.
Naming Consistency5/5
Both tools follow a clear verb_noun pattern (render_diagram, list_engines), making the API predictable.
Tool Count3/5
With only two tools, the server feels minimal but appropriate for a narrow scope; however, it borders on thin for a typical server.
Completeness4/5
The core rendering capability is present alongside engine information, but additional conveniences like validation or format conversion are absent.
Maintenance
ActivitySlowing
ResponsivenessNo issues