Labsco
ByteOverDev logo

diagrams-mcp-server

β˜… 3

from ByteOverDev

MCP server for generating cloud architecture diagrams, flowcharts, sequence diagrams, and more β€” powered by mingrammer/diagrams, Mermaid, and PlantUML.

πŸ”₯πŸ”₯πŸ”₯πŸ”₯βœ“ VerifiedFreeQuick setup

diagrams-mcp-server

PyPI CI Railway

MCP server for generating cloud architecture diagrams, flowcharts, sequence diagrams, and more β€” powered by three rendering engines: mingrammer/diagrams, Mermaid, and PlantUML.

Example diagram

Available Tools

Discovery

  • list_providers() β†’ list[str] β€” List all diagram providers (aws, gcp, k8s, azure, onprem, etc.)
  • list_services(provider) β†’ list[str] β€” List service categories within a provider (e.g. aws β†’ compute, database, network)
  • list_nodes(provider, service) β†’ list[dict] β€” List node classes for a provider.service pair with import paths
  • search_nodes(query) β†’ list[dict] β€” Search for nodes by keyword across all providers (e.g. "postgres", "lambda")

Rendering

  • render_diagram(code) β†’ Image (PNG) β€” Execute a Python script using mingrammer/diagrams in a sandboxed subprocess. Returns a rendered cloud architecture diagram.
  • render_mermaid(definition) β†’ Image (PNG/SVG) β€” Render a Mermaid diagram definition (flowcharts, sequence, class, ER, state, Gantt, and more).
  • render_plantuml(definition) β†’ Image (PNG) β€” Render a PlantUML diagram definition (sequence, class, component, activity, state, deployment).

Cross-Provider Equivalence

  • find_equivalent(node, target_provider?) β†’ dict β€” Find equivalent services across cloud providers (e.g. EC2 β†’ ComputeEngine on GCP).
  • list_categories() β†’ list[dict] β€” List all 30 infrastructure role categories with mapped nodes across providers.

Resources

The server provides reference documentation accessible via MCP resource URIs:

URIDescription
diagrams://reference/diagramDiagram constructor parameters, defaults, and usage
diagrams://reference/edgeEdge operators, labels, styling, and chaining
diagrams://reference/clusterCluster nesting, styling, and graph attributes
diagrams://reference/mermaidMermaid syntax examples for 6 diagram types
diagrams://reference/plantumlPlantUML syntax examples for 6 diagram types

Examples

Cloud Architecture (mingrammer/diagrams)

"Draw an AWS architecture with an ALB routing to two ECS services, backed by RDS and ElastiCache"

from diagrams import Diagram, Cluster
from diagrams.aws.network import ALB
from diagrams.aws.compute import ECS
from diagrams.aws.database import RDS, ElastiCache

with Diagram("ECS Service", direction="LR"):
    lb = ALB("ALB")

    with Cluster("ECS Cluster"):
        services = [ECS("Web"), ECS("API")]

    lb >> services
    services[0] >> ElastiCache("Cache")
    services[1] >> RDS("Database")

Flowchart (Mermaid)

"Create a flowchart showing a CI/CD pipeline"

Mermaid flowchart

Sequence Diagram (PlantUML)

"Show the authentication flow between a client, API gateway, and auth service"

PlantUML sequence diagram

@startuml
Client -> "API Gateway": POST /login
"API Gateway" -> "Auth Service": Validate credentials
"Auth Service" --> "API Gateway": JWT token
"API Gateway" --> Client: 200 OK + token
Client -> "API Gateway": GET /data (Bearer token)
"API Gateway" -> "Auth Service": Verify token
"Auth Service" --> "API Gateway": Valid
"API Gateway" --> Client: 200 OK + data
@enduml

Development

# Clone and install
git clone https://github.com/ByteOverDev/diagrams-mcp.git
cd diagrams-mcp
pip install -e ".[dev]"

# Run tests
pytest

# Lint and format
ruff check .
ruff format .

# Run the MCP server locally (stdio mode)
diagrams-mcp-server

Split Facade/Renderer Mode

For hosted deployments, the MCP server can run as a lightweight facade that delegates render work to a separate renderer service. This keeps the always-on MCP process small while Graphviz, Chromium, Mermaid CLI, Java, and PlantUML live only in the renderer image.

# Terminal 1: renderer service
RENDERER_HOST=0.0.0.0 RENDERER_PORT=8001 diagrams-renderer-server

# Terminal 2: HTTP MCP facade delegating to the renderer
FASTMCP_TRANSPORT=http \
FASTMCP_HOST=0.0.0.0 \
FASTMCP_PORT=8000 \
DIAGRAMS_RENDERER_MODE=remote \
DIAGRAMS_RENDERER_URL=http://127.0.0.1:8001 \
diagrams-mcp-server

Docker/Railway examples are included:

FilePurpose
Dockerfile.facadeSlim MCP facade image without renderer-only binaries
Dockerfile.rendererRenderer image with Graphviz, Chromium, Mermaid CLI, Java, and PlantUML
railway.facade.tomlExample Railway facade service config
railway.renderer.tomlExample Railway renderer service config

Key environment variables:

VariablePurpose
DIAGRAMS_RENDERER_MODE=remoteMakes the facade use the HTTP renderer service
DIAGRAMS_RENDERER_URLRenderer base URL, for example http://diagrams-renderer.railway.internal:8080
DIAGRAMS_IMAGE_STORE_DIROptional file-backed temporary image store directory
BASE_URLOptional public base URL used when returning absolute download links

Supported Providers

The render_diagram tool supports all providers from the mingrammer/diagrams library, including:

AWS, GCP, Azure, Kubernetes, On-Premise, AlibabaCloud, OCI, OpenStack, DigitalOcean, Elastic, Outscale, Generic, and Custom nodes.

Use list_providers() and search_nodes(query) to discover available nodes.

License

MIT

<!-- mcp-name: io.github.mskry/diagrams-mcp-server -->