Skip to main content

Excalidraw MCP · persistent workflow

An Excalidraw MCP workflow that survives the chat

Connect an MCP-capable agent to a persistent Excalidraw workspace. Let the agent create the first system map, refine the same canvas in the browser, then send a targeted update back through the agent.

01

Input

Defined scope

02

Agent

First draft

03

Canvas

Stable URL

04

Human

Review + edit

05

Agent

Same-canvas update

The useful unit is not the generated image. It is one diagram with a stable URL, editable elements, human review, and programmatic follow-up.

Product boundary: Excaliwow is built on the open-source Excalidraw editor and is not affiliated with or endorsed by Excalidraw. The open-source Excalidraw project has a separate MCP server, and Excalidraw+ has its own API and MCP surfaces in public beta. This page documents Excaliwow’s persistent workspace workflow.

Reproduce it

Copy setup

01

Create a scoped token

Create an account, verify the email, then mint a Personal Access Token with read and write capabilities in Settings → Developer. Add delete only if you intentionally want the agent to use reversible trash/restore tools.

02

Add the MCP server

For Claude Code, export the token before adding the local server so the literal token does not land on the command line stored in shell history.

Terminal

export EXCALIWOW_TOKEN=excw_pat_…
claude mcp add excaliwow \
  --scope local \
  --env EXCALIWOW_TOKEN="$EXCALIWOW_TOKEN" \
  -- npx -y @excaliwow/mcp

03

Or configure a JSON-based client

Claude Desktop and other JSON-config clients can launch the same stdio server through npx. Keep the real token in local settings or a secrets manager, never in a repository.

MCP client config

{
  "mcpServers": {
    "excaliwow": {
      "command": "npx",
      "args": ["-y", "@excaliwow/mcp"],
      "env": {
        "EXCALIWOW_TOKEN": "excw_pat_…"
      }
    }
  }
}

Human review

Change what the agent misunderstood

  1. Correct a misplaced system boundary before polishing the layout.
  2. Clarify one ambiguous data-flow label so reviewers do not infer unsupported behavior.

Same-canvas follow-up

Send the correction back

Update the same diagram in place with the reviewed relationship, preserving every human edit and existing element id.

Review the critical path, not the pixels

  • The browser, agent, and teammate enter through the same hosted edge.
  • The first draft remains distinguishable from the human-reviewed model.
  • Ambiguous responsibilities are corrected before the diagram is shared.
  • The follow-up updates the same diagram rather than creating a replacement.

Common questions

Is this the official Excalidraw MCP server?
No. This is @excaliwow/mcp, the MCP server for Excaliwow’s hosted workspace built on the open-source Excalidraw editor. The open-source Excalidraw project and Excalidraw+ offer separate MCP products. Excaliwow is not affiliated with or endorsed by Excalidraw.
Does Excaliwow include AI credits?
Excaliwow adds no separate AI-generation allowance. You bring Claude, Codex, or another MCP-capable agent, and the MCP server gives it scoped access to diagrams in your Excaliwow account. Normal product and API limits still apply.
Can a person edit an agent-created diagram?
Yes. The MCP tools return a persistent editor URL. Open that diagram in the browser, move or restyle elements, add comments, and then ask the agent to make a targeted update to the same canvas rather than generating a disconnected export.
Do I have to give the agent delete access?
No. A read-and-write token can create and edit diagrams but cannot trash them. Delete is a separate PAT capability, and the MCP delete surface is limited to reversible trash and restore operations rather than permanent purge or public-link creation.

Try the complete agent → browser → agent loop

Start free—no credit card. First 10,000 verified accounts keep the core workspace free; 3 diagrams to start and earn more capacity.

Start free