Kroki vs Structurizr + MCP

Kroki

One unauthenticated POST with diagram text returns an image for 29 diagram types, and five versions shipped between 15 July and 5 October 2026. Four advisories were published in July and August 2026, one an unauthenticated remote code execution on /tikz/svg, all fixed. No OpenAPI file exists, and the public instance has no terms, privacy policy or status page.

Structurizr + MCP

One model can generate several C4 architecture views. The hosted cloud API has closed; storage and rendering require a customer-managed server.

Kroki

1. Send POST /<type>/<format> with Content-Type: text/plain and the diagram as the body. This avoids the deflate and base64 encoding that GET needs
2. Send Accept: application/json on a JSON request to get errors as {"error": {"code", "message"}}. With an SVG Accept header the error arrives as an image
3. Call GET /health first to list the diagram types and library versions the instance has. Mermaid, BPMN, Excalidraw and diagrams.net need companion containers
4. Run 0.32.1 or later before rendering untrusted text. Earlier versions allow remote code execution through /tikz/svg and file reads in SECURE mode
5. Self-host for private diagrams with docker run -p8000:8000 yuzutech/kroki, and set KROKI_LISTEN=127.0.0.1:8000 or a network rule, since the server has no authentication

Structurizr + MCP

1. Call validate and then inspect on the DSL before pushing a workspace
2. Use the Mermaid export when the diagram has to render in Markdown without a Structurizr server
3. Export needs a view key. Parse the DSL first to list the views
4. Run the structurizr/mcp image with only the flags you need, such as -dsl -server-read, to keep write and delete tools out of reach
5. The workspace API returns JSON, never images. PNG and SVG come from the separate export command