Diagrams.so

Add the server to your client config (below) withDIAGRAMS_LOGIN_EMAILset 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, pressApprove, and ask again. Nothing to install or type.

loginonly connects the machine. It never generates anything itself, so there is nogeneratecommand to type in a terminal. You write the promptin your assistant's normal chat boxand it calls the tools for you.

MCP servers load at startup, so restart your client after adding it.Then run/mcpand confirmdiagrams-soshows 23 tools.

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 callsgenerate_diagram, thenget_warnings, thenexport_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 andevery exportare free.

Reads and exports are free;generate/edit/fix/relayoutcost credits, anddeleteis destructive.relayoutasks forconfirm=truebefore it charges.

Installing the package putsdiagrams-soon your PATH. The longerdiagrams-so-mcpname still works, andnpx @diagrams-so/mcp <command>works without installing anything.

npm i -g @diagrams-so/mcp diagrams-so login # connect this machine (a browser opens, press Approve) diagrams-so whoami # which account is this machine connected as diagrams-so logout # remove the local credential diagrams-so install # print client config to paste

The published package runs straight from npm, so there is no path to fill in and no key in the config. Runnpx @diagrams-so/mcp installto print these blocks for your client.

claude mcp add diagrams-so -- npx -y @diagrams-so/mcp npx @diagrams-so/mcp login

Claude Desktop / Cursor (claude_desktop_config.json/mcp.json)

Same package, sameloginstep. It's the MCPB bundle Smithery installs, not the npm package, so the version shown there follows releases rather thannpm dist-tags.

DIAGRAMS_API_KEY=dgz_live_your_key node test-smoke.mjs

Runs the full flow (connect → list tools → whoami → generate → warnings → fix → export → error handling).

# bump "version" in package.json + manifest.json to match, commit, then: git tag v1.2.0 && git push origin v1.2.0

The tag must matchpackage.json'sversion(the workflow enforces this). The.mcpbbundle appears on the GitHub Release; manualworkflow_dispatchproduces it as a downloadable artifact without publishing (handy for testing a bundle).

Repo secrets/variables (optional):DIAGRAMS_API_KEY(live smoke),NPM_TOKEN(npm publish),DIAGRAMS_API_BASEvariable (non-prod live-smoke target).

- stdout is the MCP channel— the server logs only to stderr.
- Errors come back as clean MCP tool errors carrying the API'scode, HTTP status, andrequest_id.
- The server never talks to internal services or the database — only the public/api/v2.
- Long-running tools stay alive past client timeouts.generate/edit/fix/relayout/enhance_prompt/clarify_promptemit anotifications/progressevery 10s while running, so MCP clients that reset their request timeout on progress (resetTimeoutOnProgress) won't abort a slow generation at the SDK's 60s default. If your client doesn't reset on progress, raise its per-call timeout for these tools.

git clone https://github.com/RedHold/diagrams-mcp-app-core.git cd diagrams-mcp-app-core npm install # installs deps and builds dist/ via the prepare hook node scripts/ci-smoke.mjs # all 23 tools register; no API calls, no credits # point a client at your working copy claude mcp add diagrams-so-dev -- node "$(pwd)/dist/index.js" # build the MCPB bundle npm run build && npx @anthropic-ai/mcpb pack

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

Create crafted UI components inspired by the best 21st.dev design engineers.

Bring agent evaluations, observability, and synthetic test set generation directly into your IDE for free with Galileo's new MCP server

An MCP server to help AI assistants to answer questions and generate AccelByte Extend SDK code more effectively .

MCP server for AI Diagram Maker — generate beautiful software engineering diagrams directly inside Cursor, Claude Desktop, Claude Code, or any MCP-compatible AI agent

ALAPI MCP Tools,Call hundreds of API interfaces via MCP

AI-powered SVG animation generator that transforms static files into animated SVG components using the Allyson platform

MCP server that gives AI assistants on-demand access to 1,500+ amCharts docs, ~300 code examples, and 1000+ class API references.

APIMatic MCP Server is used to validate OpenAPI specifications using APIMatic. The server processes OpenAPI files and returns validation summaries by leveraging APIMatic’s API.

One shared context layer for AI agents and humans — live API specs, DB schemas, and versioned contracts across repos so every agent and teammate works from the same source of truth.