Skip to main content

MCP Overview

Ideagram exposes diagrams and model links through an MCP server. Compatible AI tools can inspect architecture, create or update diagram elements, validate diagrams, export Mermaid, and link visual nodes to canonical project entities.

Transport Choices​

The public alpha uses Remote HTTP. Hosted clients, CLI tools, and editors connect to:

https://ideagram.dev/mcp

Configure the client with a personal access token from Settings > MCP Access. The token identifies your account; you do not need a user ID, repository checkout, or Supabase credentials.

What Is Final?​

Remote HTTP is the supported alpha path for hosted integrations. The current auth path is:

  • Today: personal access tokens from Settings > MCP Access, plus an ops-managed env-var allowlist for service identities.
  • Later: OAuth + PKCE is the intended long-term remote authorization flow.

Token Scopes​

read permits inspection. write permits edits within the user's permissions. propose queues decision/spec upserts for review, while other permitted writes still apply directly. Only a write scope can resolve pending changes. A token does not grant access to another user's organization.

Tool Surface​

The MCP server supports discovery, creation, and documentation workflows. Its tool surface is not identical to every action in the editor:

  • Discover and create the workspace hierarchy — list organizations, workspaces, and projects the token can see, and create a new workspace, project, or diagram from scratch (no need to already have an id to hand).
  • List, fetch, add, and update diagrams — components, connections, versions, validation, and Mermaid export.
  • Create and edit Pages and Notes — documents, folders, decision records (ADRs), and specs, cross-linked to diagrams and model entities.
  • Read and update the project model — entities, relationships, and their links to diagram instances.
  • Propose and review changes — queue decision/spec proposals for human approval, and ask/answer clarifying questions against a project.
  • Run packaged skills — a named prompt + tool subset for a repeatable workflow.

See MCP tool reference for the full list.

Next Steps​

  • Use Remote HTTP MCP to access your account from Cursor, Claude Code, or another client that supports bearer headers.
  • Use MCP clients when configuring Cursor, Claude Code, or ChatGPT-compatible clients.
  • Use MCP tool reference to see the available operations.