Now in beta · Works with Claude Code, Codex, Cursor and local models through MCP →

Your agent doesn't know your architecture.
Now it does.

Ideagram keeps your diagrams, ADRs and specs linked in one workspace and serves them to your agent through one MCP server. It reads your decisions before it writes code, keeps the architecture up to date, and you approve every change.

Local models · Real-time collaboration · No-signup playground

>_ Claude Code · connected to Ideagram via MCP
Why do we use Stripe? Update the ADR with the SCA requirement.
ideagram (MCP)
✓get_project_contextpayments
✓get_diagram"Checkout · Containers"
✓get_documentADR-014
◷upsert_decisionADR-014 · proposed
Stripe was chosen because it's the only provider reached from the Payment Service. I proposed an update to ADR-014; it's waiting for your approval in Ideagram.
MCP inbox · 1 pending

Claude proposed changes to ADR-014+ 2 lines in Context · linked to Payment Service

ApproveReview diffReject
  1. Live diagrams in your docs. ADRs and pages embed the real diagram, not a screenshot.
  2. Agents read it through MCP. Claude Code loads the project before it answers.
  3. You approve what changes. Proposed edits wait in the inbox for a person.
One MCP server forClaude CodeCodexCursorChatGPTlocal models and any client that speaks MCP
Why Ideagram

Architecture knowledge is scattered. Your agents can’t see it.

  1. 01

    Diagrams drift

    The diagram in the wiki shows last year’s system. Nobody knows which boxes are still true.

  2. 02

    Decisions get lost

    Why you chose Postgres lives in a chat thread from two years ago. New people ask again.

  3. 03

    Agents guess

    Coding agents read the files you open, not the architecture. They fill the gaps with plausible guesses.

Ideagram keeps diagrams, decisions and the system model in one workspace and hands it to your agents through MCP.

One workspace

Diagrams, pages and decisions that point to each other.

Five parts of one workspace, all linked to the same model. Pick one to see it.

Customer[Person]Buys products inthe web storeCheckout SPA[Container: React]Cart, address andpayment stepsOrder API[Container: Node.js]Creates and tracksordersPayment Service[Container: Go]Authorizes andcaptures paymentsOrders DB[PostgreSQL]Stripe[External system]Card processingand SCAHTTPSRESTRESTSQLHTTPS
  • 12 diagram types with auto-layout
  • Mermaid and PlantUML in, Mermaid out
  • Version history and live cursors
Ideagram MCP

Agents propose.
You approve.

Your agents get the full architecture as context and write back through the same path the editor uses. Scoped tokens and an approval inbox keep people in charge.

  1. 1Your agentClaude Code, Cursor, ChatGPT or any MCP client
  2. 2Ideagram MCPOne URL and a scoped personal token
  3. 3Your workspaceDiagrams, pages, ADRs and the model
  4. 4Your reviewProposed changes wait for your approval

Three token scopes

  • readLoads diagrams, pages, ADRs and the model before writing a line of code.
  • proposeNever changes anything on its own: every change waits in your inbox for approval.
  • writeChanges diagrams and pages directly. For agents and automations you trust.

50+ MCP tools · every tool call audited · tokens act as you, never more

Connect in one command

claude mcp add --transport http --scope user \
  --header "Authorization: Bearer idg_pat_…" \
  ideagram https://ideagram.dev/mcp

# then just ask
› draft an ADR from the checkout diagram
› reconcile this diagram with the code in src/
› export the payment flow as Mermaid
Who it’s for

Built for the people who design the system.

Software architects

Keep the C4 views, decisions and the system model in one place that stays current.

  • C4 from context to deployment
  • ADRs linked to the views they change
  • Versions you can compare

Platform and staff engineers

Document how services talk to each other and walk new people through real flows.

  • Sequence and flow walkthroughs
  • Runbooks next to the diagrams
  • Mermaid in, Mermaid out

Teams shipping with AI agents

Give Claude Code, Cursor or ChatGPT the architecture before they touch the code.

  • One MCP server for every client
  • Read, propose or write tokens
  • An inbox for agent proposals
Playground

Paste Mermaid. See the system.

Try it without an account. Save it to Ideagram when it's worth keeping.

C4Container
  Person(customer, "Customer")
  Container(spa, "Checkout SPA", "React")
  Container(order, "Order API", "Node.js")
  Container(pay, "Payment Service", "Go")
  ContainerDb(db, "Orders DB", "PostgreSQL")
  System_Ext(stripe, "Stripe")

  Rel(customer, spa, "Uses")
  Rel(spa, order, "Create order")
  Rel(spa, pay, "Pay")
  Rel(order, db, "Reads/writes")
  Rel(pay, stripe, "Charges")
Customer[Person]Buys products inthe web storeCheckout SPA[Container: React]Cart, address andpayment stepsOrder API[Container: Node.js]Creates and tracksordersPayment Service[Container: Go]Authorizes andcaptures paymentsOrders DB[PostgreSQL]Stripe[External system]Card processingand SCAHTTPSRESTRESTSQLHTTPS
Open the playgroundMermaid and PlantUML · runs in your browser
FAQ

Questions, answered.

More in the documentation, or ask us directly.

What does the beta include?

The whole product: diagrams, pages and notes, ADRs and specs, the system model, flows, versions, real-time collaboration and the MCP server. Some workflows may still change based on feedback.

How do I get access?

Create an account with your email, Google or GitHub: you are in right away, free during the beta. The playground works without an account.

Which agents work with Ideagram?

Any MCP client that supports remote HTTP with a bearer token: Claude Code, Codex, Cursor and ChatGPT-compatible clients among them. You connect once with a URL and a personal token.

Can an agent change things without me?

Only if you give it a write token. Read tokens only load context; propose tokens queue every change for your approval. A token acts as you and never reaches more than you can.

Can I bring my existing diagrams?

Yes. Paste Mermaid or PlantUML and Ideagram builds the diagram; you can export to Mermaid at any time.

Do I need to install anything?

No. Ideagram runs in the browser, and agents connect over HTTPS to a single MCP URL with a personal token.

Contact

Let's talk about your architecture.

Book a walkthrough for your team, ask about access, or tell us what your agents need. A human from the team replies, usually within one business day.

  • Team walkthroughs30 minutes with your own diagrams and MCP setup.
  • Beta accessGet a workspace and an MCP token for your team.
  • Feedback & partnershipsIntegrations, contributing, press.
What can we help with?
We never share your email.
Ideagram beta

Let your agents read the architecture, not guess it.

The playground needs no account. Beta teams get a workspace and an MCP token.