Generate and edit AWS, Azure, GCP and Kubernetes architecture diagrams as editable draw.io files.
MCPpedia last refreshed this data
io.github.RedHold/diagrams-so-mcp is an MCP server that generate and edit AWS, Azure, GCP and Kubernetes architecture diagrams as editable draw.io files. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 87/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-redhold-diagrams-so-mcp": {
"args": [
"-y",
"@diagrams-so/mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
The Diagrams.so MCP server — generate, edit, and manage cloud architecture diagrams from any MCP client (Claude Desktop, Claude Code, Cursor). It's a thin stdio client over the public Diagrams.so API (/api/v2); every tool is one REST call.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@diagrams-so/mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @diagrams-so/mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in cloud
MCP Server for GCP environment for interacting with various Observability APIs.
Evidence-grounded agent memory with mandatory provenance, on local SQLite or Cloudflare D1
MCP Server for kubernetes management commands
Upload, organize, search, and transform images, videos, and files with AI-powered tools.
MCP Security Weekly
Get CVE alerts and security updates for io.github.RedHold/diagrams-so-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
The Diagrams.so MCP server — generate, edit, and manage cloud architecture diagrams from any MCP client (Claude Desktop, Claude Code, Cursor). It's a thin stdio client over the public Diagrams.so API (/api/v2); every tool is one REST call.
Needs Node ≥ 18. No API key to copy: you connect by approving in a browser.
# 1. add the server to Claude Code
claude mcp add diagrams-so -- npx -y @diagrams-so/mcp
# 2. connect this machine (a browser opens, press Approve)
npx @diagrams-so/mcp login
Restart your client, then ask: "Generate an AWS 3-tier web app diagram and show me the warnings."
Run /mcp if you want to confirm all 23 tools registered first.
Using it a lot? Install once and the command gets shorter:
npm i -g @diagrams-so/mcp
diagrams-so login
The server talks to production (
https://api.diagrams.so/api/v2) by default. Point it at a local or self-hosted API withDIAGRAMS_API_BASE.
Using Claude Desktop or Cursor instead of the CLI? See Add it to your MCP client. Prefer a one-click, no-terminal install? See One-click install (MCPB).
Add the server to your client config (below) with DIAGRAMS_LOGIN_EMAIL set to your email,
then just ask for a diagram. Because the machine isn't connected yet, the first tool call
emails you a one-time sign-in code and replies with a link. Open it, enter the code, press
Approve, and ask again. Nothing to install or type.
login only connects the machine. It never generates anything itself, so there is no
generate command to type in a terminal. You write the prompt in your assistant's normal
chat box and it calls the tools for you.
| Client | Where you type the prompt |
|---|---|
| Claude Code | the terminal chat, same place you ask anything else |
| Claude Desktop | the normal message box |
| Cursor | the chat or composer panel |
MCP servers load at startup, so restart your client after adding it. Then run /mcp and
confirm diagrams-so shows 23 tools.
Now just ask, in plain English:
Generate an AWS three-tier web app with an ALB, EC2 Auto Scaling and RDS Multi-AZ. Show me the design warnings, then export it as draw.io.
Behind that one sentence the assistant calls generate_diagram, then get_warnings, then
export_diagram. You never name a tool or write JSON.
More things worth asking, once you have a diagram:
The warnings mention no encryption in transit. Fix that one and show me the new score.
Add a CloudFront distribution in front of the ALB.
Re-export it as SVG so I can drop it in the README.
Each reply carries the credit cost and your remaining balance. Generating, editing, fixing and re-laying-out spend credits; reading, warnings and every export are free.
The .drawio file the assistant saves opens at app.diagrams.net or
in the desktop app, fully editable — it is real draw.io XML, not a picture.
Prefer not to use an assistant at all? diagrams.so/create has
the same thing as a web page: type the prompt in the box. No install, no login, no MCP.
Create & change (mutating)
| Tool | What it does | Cost |
|---|---|---|
generate_diagram | Create a diagram from a prompt → id + draw.io XML + warnings + score | credits |
edit_diagram | Apply a natural-language change (new version) | credits |
fix_warning | Resolve one Well-Architected warning | credits |
relayout_diagram | AI re-arrange the layout (async; first |