From a sentence to a diagram.
Arketo connects to the assistant you already build with over MCP. You describe the system, it draws and audits it. Here is the whole loop.
Five steps, start to report
From an empty canvas to a finished report, this is the whole loop the assistant runs with you.
1 · Get your private canvas
Subscribe and you get an isolated workspace and a unique MCP URL, just for you. Nothing is shared with other accounts, and the canvas persists between sessions.
2 · Connect your assistant
Arketo is a standard MCP server, so it drops into any MCP-capable client: Claude, Cursor, Windsurf, VS Code, Codex, and more. In Claude Code it's one command.
claude mcp add architecture --transport http <your-mcp-url>3 · Describe your system
Tell it in plain language: a React frontend, an API gateway, a Go backend, Postgres, a Redis cache. Components appear as you talk and the connections route themselves.
4 · Ask it to analyze
Say "find the risks." It walks the graph and marks bottlenecks, security gaps, and scaling limits by severity, right on the components they affect.
5 · Download the report
Ask for a write-up and it produces a full Markdown report with a phased scaling plan. Drop it into your repo, paste it into a ticket, or hand it to a teammate.
It draws while you talk.
This is a faithful miniature of the real canvas. Components pop in as they are named, edges route between tiers, and a flagged connection carries its severity badge. What you describe is what appears, live.
You talk to it the way you already do.
No diagram syntax, no schema to learn. These are the kinds of sentences that drive the canvas.
We have a Next.js app talking to a Node API, Postgres, and S3 for uploads. Draw it.
Add a Redis cache in front of the database and a worker queue for the email jobs.
Now find anything that will break at 50x the traffic and write it up.
Wire it up in one command.
Get your canvas and MCP URL, paste it into your assistant, and start describing. The first diagram takes minutes.