C4, UML and sequence diagrams
12 diagram types with auto-layout, version history and live cursors.
Works with Claude Code, Cursor and ChatGPT through MCP →Your architecture in one place.
Your architecture in one place.
For you and your agents.
Diagrams, pages, ADRs, specs and notes — linked to each other in one workspace. Connect any agent through one MCP server: it reads the whole picture, proposes changes, and you approve.
Nothing to install · Real-time collaboration · No-signup playground
ADR-014 · IdeagramCheckout · Containers+
🔒 ideagram.dev/app/page/adr-014-payment-provider
Acme/Platform/PaymentsAna, Marcos, ClaudeShare
PAGES
▸ Architecture
§ ADR-014 PaymentsADR
§ ADR-013 Event busADR
◇ Refunds v2SPEC
≡ Runbook: chargebacks
✎ PCI scope reviewNOTE
DIAGRAMS
⬚ Checkout · Containers
⬚ Payment · Sequence
⬚ Orders · Class
MODEL
◎ 42 entities · 61 relations
ADR-014 · Stripe for payments
CONTEXT
The Payment Service must support cards, wallets and SCA in the EU. See [[Refunds v2]] and the PCI notes in [[PCI scope review]].
DECISION
Integrate Stripe through the Payment Service only; no other container talks to the provider.
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
One MCP server forClaude CodeCursorChatGPTand any client that speaks MCP
One workspace
Diagrams, pages and decisions that point to each other.
Architecture usually lives in a whiteboard tool, a wiki and Slack. Here every diagram, page and decision links to the same model.
Pages with wiki links
Write in Markdown, embed live diagrams, link to any page, diagram or model entity.
ADRs and specs
Context, decision, consequences and status, in a format agents can read.
One model, many views
Rename a service once and every diagram, page and agent sees it.
Flows
Step through a request across a diagram. Useful for onboarding and reviews.
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 humans in charge.
- readAgents load diagrams, pages, ADRs and the model before writing a single line of code.
- proposeChanges to decisions and specs land in your MCP Inbox for review.
- writeTrusted automations update diagrams, apply Mermaid/PlantUML and save versions.
# 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
50+ MCP tools · 3 token scopes · every tool call audited
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")
Open the playgroundMermaid and PlantUML · runs in your browser
Contact
Let's talk about your architecture.
Request early access, book a walkthrough for your team, 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.
- Early accessGet your workspace and MCP token first.
- Feedback & partnershipsIntegrations, contributing, press.