Excalidraw
Codex skill for Excalidraw MCP App and Excalidraw+ workflows
npx -y skills add fuller-stack-dev/excalidraw-mcp-skill --skill excalidrawAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 29 days oldThe repository was created 29 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Excalidraw MCP workflows for creating, editing, presenting, exporting, and persisting diagrams, wireframes, sequence diagrams, architecture maps, state machines, and slide decks. Use when working with the Excalidraw MCP App, Excalidraw+ workspace scenes, MCP installation or repair, live tool discovery, API-key permissions, or inline interactive canvas rendering.
SKILL.md
3.9 KB, as published. Nobody here has run it
Excalidraw MCP
Route before drawing. Excalidraw has two complementary MCP surfaces:
- Excalidraw MCP App: render an interactive canvas inline in an MCP Apps host.
- Excalidraw+ MCP: persist and administer scenes, collections, and workspace data.
Use both when the user wants an inline canvas and a durable Excalidraw+ scene.
Workflow
- Classify the request:
- Inline or interactive in chat: use the MCP App.
- Durable workspace scene, collection, or administration: use Excalidraw+.
- Both: persist with Excalidraw+, then pass the scene elements to the MCP App.
- Installation, missing tools, or authentication: read references/install.md and references/tools.md.
- Discover the live tools. Both integrations are evolving; do not assume a remembered inventory is current.
- Load the server's format contract before the first content write:
- MCP App: call
read_mebeforecreate_view. - Excalidraw+: call
read_excalidraw_formatbeforeedit_scene_content.
- MCP App: call
- Choose the visual structure before writing elements: wireframe, workflow, swimlane, sequence, architecture, state machine, timeline, hierarchy, or presentation.
- Create or edit with valid Excalidraw elements. Bind shape-to-shape arrows explicitly and use shape labels for shape-owned text.
- Verify the result visually:
- MCP App: inspect the embedded canvas.
- Excalidraw+: use
take_screenshotfor agent QA, then report the scene URL.
- Finish only when the requested surface exists, is readable, and is accessible in the requested location.
For artifact-specific patterns and the bridge workflow, read references/workflows.md.
Hard Rules
- Do not substitute a browser screenshot when the user requested an inline MCP
App. Invoke
create_view. - Treat screenshots as QA evidence, not as the interactive deliverable.
- Do not confuse the Plus API endpoint with the MCP App endpoint.
- Name configured servers by role, such as
excalidraw-appandexcalidraw-plus; avoid an ambiguous singleexcalidrawentry. - Never claim every Plus tool is installed until live discovery confirms it. Key route permissions and workspace role filter the tool list.
- Keep personal and workspace keys separate. Do not print, commit, or embed API keys when an environment-backed header is supported.
- Reconnect or restart the MCP host after configuration changes before judging the installation.
- Prefer
search_scene_contentoverget_scene_contentfor targeted reads. Load the full scene only when a bridge, export, or ID-sensitive edit requires it. - Do not delete scenes, collections, users, invites, or existing elements unless the user explicitly requested that destructive action.
Installation Gate
For installation or repair:
- Select the surface or combination in references/install.md.
- Configure credentials without exposing them.
- Restart or reconnect the client.
- Run
scripts/verify-excalidraw-mcp.sh. - Compare the live inventory with references/tools.md.
Installation is complete only when the required endpoint responds, the
expected tools are discoverable, and the MCP App exposes a valid
ui://excalidraw/mcp-app.html resource when inline rendering is required.
Sources
Read references/sources.md when installing, debugging, or making claims about current tool names, permissions, transports, or client support.