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
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
The Payment Service must support cards, wallets and SCA in the EU. See [[Refunds v2]] and the PCI notes in [[PCI scope review]].
Integrate Stripe through the Payment Service only; no other container talks to the provider.
Claude proposed changes to ADR-014+ 2 lines in Context · linked to Payment Service
The diagram in the wiki shows last year’s system. Nobody knows which boxes are still true.
Why you chose Postgres lives in a chat thread from two years ago. New people ask again.
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.
Five parts of one workspace, all linked to the same model. Pick one to see it.
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.
50+ MCP tools · every tool call audited · tokens act as you, never more
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
Keep the C4 views, decisions and the system model in one place that stays current.
Document how services talk to each other and walk new people through real flows.
Give Claude Code, Cursor or ChatGPT the architecture before they touch the code.
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")
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.
Create an account with your email, Google or GitHub: you are in right away, free during the beta. The playground works without an account.
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.
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.
Yes. Paste Mermaid or PlantUML and Ideagram builds the diagram; you can export to Mermaid at any time.
No. Ideagram runs in the browser, and agents connect over HTTPS to a single MCP URL with a personal token.
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.
The playground needs no account. Beta teams get a workspace and an MCP token.