Agents
MCP
Let Claude Code, or any other agent that speaks MCP, write walkthroughs and draw canvases into your account. What it makes is a private draft, and publishing stays with you.
Connect an agent
Create an API key on your account page. It is shown once, beside the exact setup for the client you picked: Claude Code, Codex, Gemini CLI, GitHub Copilot in VS Code or Cursor. For Claude Code it is one command.
claude mcp add --transport http walkthrough \ https://walkthrough.page/mcp \ --header "Authorization: Bearer <key>"
Any other client connects over Streamable HTTP to this address, sending the key as a header.
https://walkthrough.page/mcp Authorization: Bearer <key>
Tools
Ten tools, and none of them deletes, publishes or shares anything. Those stay on the site, with the owner.
get_authoring_guide- How to write a walkthrough and draw a canvas, with a finished example. An agent should read it first.
list_walkthroughs- Every walkthrough the account owns, with its id, name, title, status and edit link.
get_walkthrough- One walkthrough as its index.mdx, diagrams.yml and seed, with the version to send back.
create_walkthrough- Saves a new private draft from an index.mdx and its diagrams.yml.
update_walkthrough- Replaces a walkthrough with new files, given the version it was read at.
list_canvases- Every canvas the account owns, with what it opens on and its edit link.
get_canvas- One canvas: its title, its items and the version to send back.
create_canvas- Draws a new canvas of boxes, arrows and text, optionally opening on a walkthrough.
update_canvas- Replaces a canvas's items, and its title if one is sent, given the version it was read at.
link_canvas- Opens a canvas on one of the account's walkthroughs, or detaches it.
Changing what is there
An update replaces the whole walkthrough or canvas, and it is checked against what the agent read. get_walkthrough and get_canvas answer with a version; the update sends it back. If anybody changed it in between, yourself in the editor included, nothing is saved, and the agent is told to read it again and redo the change.
A published walkthrough changes for its readers as soon as an update lands.
What a walkthrough contains
The authoring guide is the one description of the files, every block and diagram kind, and the limits the server enforces, and it is tested against the importer that reads them. An agent reads it with get_authoring_guide; a script reads the same text at GET /api/v1/guide. When the server refuses something, its message names the line or field to fix.