Diagramy MCP

Diagramy hosts a remote Streamable HTTP MCP server. After you authorize a client, tools can list workspaces and architectures, search the model, inspect connections and ownership, and — when write is enabled — apply structured architecture operations.

Set-up time is about five minutes. Open Workspace settings → Developer in app.diagramy.io to mint an API key or connect via OAuth.

MCP server URL:

https://api.diagramy.io/mcp

Skip the manual steps below — copy this prompt into any agentic assistant and it can add the server itself.

Add the Diagramy MCP server to this environment.

Server: https://api.diagramy.io/mcp
Transport: Streamable HTTP
Auth: OAuth 2.1 with PKCE (preferred), or a workspace API key as a Bearer token

If your MCP config is JSON-based, add:
{
  "mcpServers": {
    "diagramy": {
      "type": "streamable-http",
      "url": "https://api.diagramy.io/mcp"
    }
  }
}

Once connected, authenticate, then list my Diagramy workspaces and architectures to confirm it worked.

Read

• Architectures, model objects, groups, connections, tags, technology kinds, ownership, DSL
• Version history, architecture pull requests, review comments, persisted ADRs

Write

• Create empty architectures, update metadata and lifecycle status (draft, active, …)
• Create/update/delete objects and connections, batch apply_ops on main
• Proposal workflow: create/open/merge branches, apply_proposal_ops, comments
• Persist ADRs and other docs via save_adr / save_document

Workspace MCP write must be enabled for all write tools.

1. Open Cursor Settings → Tools & MCP
2. Add a custom MCP server with Streamable HTTP
3. Use URL https://api.diagramy.io/mcp and an API key header, or Authenticate via OAuth

{
  "mcpServers": {
    "diagramy": {
      "type": "streamable-http",
      "url": "https://api.diagramy.io/mcp",
      "headers": {
        "Authorization": "Bearer dgm_live_YOUR_KEY"
      }
    }
  }
}

claude mcp add --transport http diagramy https://api.diagramy.io/mcp

Then run claude, open /mcp, and Authenticate.

Add a custom MCP connector with name Diagramy and URL https://api.diagramy.io/mcp. Complete the browser consent flow: sign in, pick a workspace, choose read or read+write, Allow.

• What architectures are in my Diagramy workspace?
• What is the API service connected to?
• What does the payments team own?
• Add a Redis cache next to the API and connect them.

• OAuth 2.1 with PKCE (S256) for remote clients
• Workspace API keys hashed at rest (dgm_live_…)
• MCP write disabled by default per workspace
• Tool-level scopes: mcp:read / mcp:write

More docs: Documentation · Security