AI-maintained architecture diagrams
Your AI agent keeps it in sync as it codes — reflects reality, not last month's assumptions. Incremental, not one-shot regeneration that dies on the next edit.
Built for developers whose AI writes the code — Claude Code, Cursor, and Copilot users.
Bring your own API keys · works with Claude Code
| Incremental editing (Frametrue) | One-shot regeneration tools |
|---|---|
| Diagram reflects each edit in place | Regenerate from scratch — lose manual refinements |
| Every element addressable by ID | IDs reset on each regeneration |
| Persists reliably | Re-generates full graph; no guarantees |
| Survive the next agent edit | Wiped on next regeneration |
| Always live — polls the real diagram | Snapshot at generation time |
New to this?How to keep an architecture diagram in sync with your code →
Pretty much — statically auto-extracting an accurate diagram from a real codebase is a near-impossible hairball, and Frametrue doesn't attempt it. Instead, your AI agent incrementally maintains the diagram through targeted MCP edits on a stable-ID model, guided by your intent and steering. The live self-diagram above is the proof: it's the current C4 System Context view of Frametrue itself, kept in sync by the agent as the product evolves.
Point your AI coding agent at Frametrue's local MCP server. Each change your agent makes is a targeted edit, not a full regeneration — stable IDs land updates on the exact node, so the view stays current after hundreds of commits instead of drifting out of date.
Yes, when the diagram is maintained rather than one-shot. Frametrue produces a C4 System Context diagram (Level 1) that the agent keeps current through incremental MCP edits. A one-shot generation dies on the next code change; the stable-ID model updates only what changed, so the C4 view stays accurate.
Frametrue runs a local stdio MCP server, so it works with any MCP-compatible client — Claude Code, Cursor, and other stdio MCP clients. Bring your own API keys; the agent reads and edits diagrams directly from your editor session.
No. Frametrue is bring-your-own-tokens: supply your own API key and self-host the MCP server. No subscription is required — the always-current view lives in your own instance.