Skip to content
External endpointresponds

Diagrams MCP

Generate cloud architecture diagrams, flowcharts, and sequence diagrams.

Endpoint URL
https://diagrams-mcp-production.up.railway.app/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:01 AM UTC
Check
MCP initialize · 8s limit
Latency
535 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.mskry/diagrams-mcp-server

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
diagrams
Version
3.2.3
Capability keys
experimental, logging, prompts, resources, tools, extensions
Tool names
render_diagram, list_providers, list_services, list_nodes, search_nodes, render_mermaid, render_plantuml, find_equivalent, list_categories
Instructions excerpt

Generate diagrams using multiple rendering engines. **mingrammer/diagrams** (cloud architecture): Use search_nodes to find components by keyword (returns import paths), or browse with list_providers -> list_services -> list_nodes. Read the diagrams://reference/diagram, diagrams://reference/edge, and diagrams://reference/cluster resources for constructor options and usage examples. Then render_diagram to produce images. **Mermaid** (flowcharts, sequence, class, ER, state, Gantt): Read diagrams://reference/mermaid for syntax. Then render_mermaid with a definition string. **PlantUML** (sequence, class, component, activity, state, deployment): Read diagrams://reference/plantuml for syntax. Then render_plantuml with a definition string. **Cross-provider equivalence**: Use find_equivalent to find equivalent services across providers (e.g. find_equivalent('EC2', 'gcp')), or list_categories to see all mapped infrastructure roles. **Tool selection**: Use render_diagram for cloud architectu

Reported Aug 17, 2026, 05:01 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 544ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 586ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 484ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 535ms