Reads and exports are free. Generating, editing, fixing, re-laying-out, and forking a diagram cost credits. Connect a client with npx @diagrams-so/mcp login, or create a key in your account under Settings → AI Provider.

​
Build diagrams into your product

Diagrams.so turns a natural-language prompt, or an agent tool call, into a real, editable cloud-architecture diagram in native draw.io XML and SVG, with a Well-Architected review you can act on. Reach it three ways:

REST API

Call the API from any language to generate, edit, fix, and export diagrams.

MCP server

Let Claude, Cursor, or VS Code create and iterate diagrams in-loop.

SDKs

Typed Python and TypeScript clients over the same REST API.

​
Your first diagram in under 5 minutes

1

Connect, or get an API key

For the MCP server and the SDKs, run npx @diagrams-so/mcp login and press Approve in the browser. For raw HTTP, go to Settings → AI Provider → Create key at diagrams.so. The key is shown once, so copy it somewhere safe. Keys look like dgz_live_... (live) or dgz_test_... (test).
2

Make a call

3

Open the result

The response includes the diagram id, the draw.io XML, any Well-Architected warnings, and your credit usage. Open the XML at app.diagrams.net or export it as SVG.

​
What you can build

Docs that never drift

Regenerate architecture diagrams from your infra description in CI, so docs stay current.

Agent-native diagrams

Let an AI agent draw, review, and fix a diagram as part of a larger task via MCP.

Well-Architected reviews

Surface warnings on a design and apply fixes programmatically.

Import and remix

Bring an existing draw.io file in, edit it with a prompt, export it back out.

​
Next steps

Quickstart

The full first-call walkthrough.

Authentication

Keys, scopes, and test mode.

API reference

Every endpoint.