Enables generation of Kubernetes architecture diagrams including ingress, services, pods, and other Kubernetes infrastructure components as part of the diagrams library's 15+ supported providers.
Uses the Python diagrams library to generate infrastructure and architecture diagrams as code, supporting 500+ node types across multiple cloud and infrastructure providers.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Diagrams MCP Server Create an AWS 3-tier web app diagram with load balancer, EC2 instances, and RDS database"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server for generating infrastructure and architecture diagrams as code using the Python diagrams library.
5 Diagram Tools for infrastructure, architecture, and flowcharts:
Infrastructure Diagrams - 15+ providers (AWS, Azure, GCP, K8s, On-Prem, SaaS)
500+ Node Types - Compute, database, network, storage, security
Custom Icons - Web URLs (HTTPS) and local files
Flowcharts - 24 shapes for process diagrams
Validation - Dry-run before generation
Advanced Capabilities:
Multiple output formats (PNG, PDF, JPG, DOT)
Cluster grouping with unlimited nesting
Edge styling (colours, labels, line styles)
Graphviz attribute customisation
Related MCP server: diagrams-mcp
System Requirements:
Graphviz must be installed:
macOS: brew install graphviz
Ubuntu/Debian: sudo apt-get install graphviz
Windows: Download from https://graphviz.org/download/
Add to your claude_desktop_config.json:
For published package:
{
"mcpServers": {
"diagrams": {
"command": "uvx",
"args": ["diagrams-mcp"]
}
}
}For local development:
{
"mcpServers": {
"diagrams:local": {
"command": "uv",
"args": [
"--directory",
"/ABSOLUTE/PATH/TO/diagrams-mcp",
"run",
"diagrams-mcp"
]
}
}
}Quick setup (CLI):
Published package:
claude mcp add --transport stdio math -- uvx diagrams-mcpLocal development:
claude mcp add --transport stdio math -- uvx --from /absolute/path/to/diagrams-mcp diagrams-mcpTeam setup (project-level):
Add .mcp.json to your project root:
{
"mcpServers": {
"diagrams": {
"command": "uvx",
"args": ["diagrams-mcp"]
}
}
}Verify installation:
claude mcp listOr check in IDE: View → MCP Servers, or use /mcp command.
Once installed, try these prompts:
"Create an AWS 3-tier web application diagram with Route53, ELB, EC2 instances, and RDS"
"Generate a Kubernetes microservices architecture with ingress, services, and pods"
"Build a flowchart for a CI/CD pipeline with decision points"
"Create a diagram using a custom icon from my company logo URL"
"Show me all available AWS compute nodes"
Map to tools: create_diagram, create_diagram_with_custom_icons, create_flowchart, list_available_nodes, validate_diagram_spec
All tool parameters and descriptions are available in your IDE's autocomplete.
Tool | Description |
| Full infrastructure/architecture diagrams with all providers |
| Diagrams with custom node icons from URLs or local files |
| Simplified flowchart creation with 24 process shapes |
Tool | Description |
| Search 500+ available nodes by provider, category, or keyword |
| Dry-run validation before generation |
HTTPS-only (HTTP rejected)
5MB file size limit
5-second download timeout
Image format validation (PNG, JPG)
Automatic caching (~/.diagrams_mcp/icon_cache)
Path validation (file must exist)
Format validation
Sandboxed execution
# Run all tests
uv run poe testSTDIO mode (for Claude Desktop integration):
uv run diagrams-mcpHTTP mode (for containerised deployments):
uv run diagrams-mcp-http --port 8000MIT License. See LICENSE file for details.
Contributions welcome via PRs! Please ensure:
Tests pass, and new ones are added if applicable
Code is linted & formatted
Type hints are included
Clear, actionable error messages are provided
For issues and questions, please open an issue on GitHub.
Generate infrastructure diagrams with 15+ providers (AWS, Azure, GCP, K8s, etc.).
Examples: AWS: nodes=[{"id":"r53","provider":"aws","category":"network","type":"Route53",...}] K8s: nodes=[{"id":"ing","provider":"k8s","category":"network","type":"Ingress",...}] Clusters: clusters=[{"name":"VPC","node_ids":["elb","ec2"],"graph_attr":{"bgcolor":"#E5F5FD"}}]
⚠️ CRITICAL: Node types must exist in diagrams library or diagram fails silently (no arrows). ALWAYS verify first: list_available_nodes(provider="aws", category="compute") For brands (Stripe, Vercel), use create_diagram_with_custom_icons instead.
Inputs: name (required), nodes (required), connections (required), clusters, +9 more. Returns: result
Create diagrams with custom icons from web URLs or local files.
USE WHEN: Brand logos (Stripe, Vercel, Supabase, Fly.io) not in diagrams library. GitHub avatars work well: https://avatars.githubusercontent.com/u/{org_id}
Examples: URL: custom_nodes=[{"id":"stripe","icon_source":"url","icon_path":"https://avatars.githubusercontent.com/u/856813"}] Mixed: nodes=[{...AWS nodes...}], custom_nodes=[{...}], connections=[...]
HTTPS-only for URLs, 5MB limit, PNG/JPG supported. Automatic caching.
Inputs: name (required), custom_nodes (required), connections (required), nodes, +7 more. Returns: result
Create process flowcharts with 24 shapes (StartEnd, Process, Decision, etc.).
Example: steps=[{"id":"start","shape":"StartEnd","label":"Start"},...] flows=[{"from_step":"start","to_step":"check"},...]
Inputs: name (required), steps (required), flows (required), direction, +4 more. Returns: result
Discover 500+ node types across providers.
⚠️ USE THIS FIRST before create_diagram to avoid invalid node errors.
Filters: provider, category, search_term
Examples: AWS compute: provider="aws", category="compute" → EC2, Lambda, ECS, EKS... Search DBs: search_term="db" → RDS, DynamoDB, SQL across providers
Inputs: provider, category, search_term, limit. Returns: result
Validate diagram before generation (dry-run).
Checks: node validity, connection references, cluster memberships. Returns: {"valid": true/false, "errors": [...], "warnings": [...]}
Inputs: nodes (required), connections (required), clusters. Returns: result
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 5 tools
Each tool has a clearly distinct purpose: create_diagram for standard infrastructure diagrams, create_diagram_with_custom_icons for diagrams with custom icons, create_flowchart for process flowcharts, list_available_nodes for discovery, and validate_diagram_spec for validation. The descriptions explicitly differentiate when to use each tool, with clear boundaries between them.
All tool names follow a consistent verb_noun pattern with snake_case: create_diagram, create_diagram_with_custom_icons, create_flowchart, list_available_nodes, validate_diagram_spec. The naming is predictable and readable throughout the set.
With 5 tools, this server is well-scoped for diagram creation and management. Each tool earns its place by covering distinct aspects: diagram generation (2 tools), flowchart creation, node discovery, and validation. This count is appropriate for the domain without being too sparse or bloated.
The tool set covers the core diagram creation workflow comprehensively: discovery (list_available_nodes), validation (validate_diagram_spec), and generation for both infrastructure diagrams and flowcharts. A minor gap exists in lacking update or delete operations for existing diagrams, but agents can work around this by regenerating diagrams as needed.
Generate cloud architecture diagrams, flowcharts, and sequence diagrams.
Discover cloud shapes and create, inspect, validate, patch, and review architecture diagrams.
Create workflow, sequence, architecture, and mind map diagrams via AI assistants.
Create, read and edit architecture, flow and ER diagrams on a live canvas shared with your team.
