Draw it from an agent: Rovo and Claude
Calibro Sketch now ships its own Rovo agent and the tools behind it. Open Ask Rovo in Confluence, switch to Calibro Sketch Agent, and say what you want: draw the payments platform — browser clients behind a load balancer, a Node API, Postgres, Redis, and two workers consuming from Kafka. The agent writes the diagram itself, as real Excalidraw elements with every label bound to its shape and every arrow bound at both ends, and saves it as a Sketch in the space you name. Then keep talking: add a CDN in front of the clients, what does the diagram in this space show?, put it on the Payments architecture page. Ten tools, every one the same thing the app does and run as you: list spaces, list Sketches, read one in full or as a plain list of components and relationships, create, update, delete, find a page and embed on it, and a guide to the drawing format the agent reads before its first scene. Rovo shows what it is about to write and waits for you to confirm, and an update is refused if someone saved in between rather than overwriting them.
Two things make this more than a chat window. The AI is whoever is talking — Rovo, a Rovo Studio agent your team built with these tools under Connected apps, or Claude — so a diagram drawn from the repository the agent just read costs you nothing on the in-app AI, which stays for the editor’s own describe it, draw it. And the result arrives where you are looking: a page embedding the Sketch redraws the moment the agent saves, the space’s list gains the new diagram without a refresh, and an editor you have open takes the new version in place when you have nothing unsaved, or tells you and leaves your work alone when you do. No polling — the socket is Atlassian’s. The same wiring means a colleague’s save reaches your open page too.
Claude, Claude Code and Claude Desktop have the same ten tools: since 11 October, Calibro Sketch is listed in Claude’s connector directory. A site admin turns on Allow external MCP access for the app once, in Atlassian Administration, and each person adds the connector and signs in — Drawing from an agent has the steps. On upgrade, Confluence asks a site admin to approve one new permission — writing to pages, which only the embed tool uses, and only on a page the agent was pointed at. Nothing else changed: no external egress, the app still runs entirely on Forge, and your diagrams stay inside your site.