mcp_excalidraw
MCP server and Claude Code skill for Excalidraw, programmatic canvas toolkit to create, edit, and export diagrams via AI agents with real-time canvas sync.
Runssource: GitHubhomepageTypeScriptMITcommit 713706e967ed
TypeScript, MIT licensed.
mcp_excalidraw runs. An Argusic agent installed it in 6.2 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Full build succeeds (TypeScript + Vite), canvas server starts and responds to health checks, all 5 MCP stdio wire checks pass, local bind regression passes, all 15 Playwright browser tests pass, and the CLI correctly creates, queries, describes, and exports Excalidraw elements.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
- Install time
- 6 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- npm test exited 0 (5 stdio wire checks passed, 1 local bind check passed); npm run test:canvas exited 0 (15/15 passed); canvas server health endpoint returned 200; CLI add/describe/export commands all returned valid JSON with correct element data
- Model tokens used
- 72,955
- Exact commit tested
- 713706e967ed
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- `npm ci` took ~10s real wall time - First build took ~39s for Vite + ~7s for tsc - Second full build took ~33s for Vite + ~7s for tsc - MCP tests: ~10s - Bind tests: ~10s - Playwright test: 33.5s test execution + 43s build = ~77s - Chromium download: ~16s - npm reinstall: ~10s - NVM/node download/install: ~20s - Various CLI tests and server starts: ~15s Total wall clock was probably around 4-5 minutes. But actually from the environment_context `curren… Let me just report honestly:
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 6.2 minutes to install, slower than the median of the 35 comparable projects Argusic has measured.
Of the 36 TypeScript projects Argusic has installed and timed, mcp_excalidraw was the 27th fastest to reach a running state, and 30 of 36 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 6.2 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mcp-excalidraw)Questions
- Does mcp_excalidraw run?
- Yes. mcp_excalidraw runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test mcp_excalidraw?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 713706e967ed. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test mcp_excalidraw?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does mcp_excalidraw take to install?
- 6.2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does mcp_excalidraw need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mcp_excalidraw?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does mcp_excalidraw compare with the alternatives?
- Of the 36 TypeScript projects Argusic has installed and timed, mcp_excalidraw was the 27th fastest to reach a running state, and 30 of 36 reached one at all.
- Where is the evidence for mcp_excalidraw?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.