Draw and verify Excalidraw diagrams through an agent canvas
Use mcp_excalidraw to let coding agents create, inspect, revise, export, and commit editable Excalidraw diagrams from a local canvas.
npx skills add agentskillexchange/skills --skill draw-and-verify-excalidraw-diagrams-through-an-agent-canvas
Use mcp_excalidraw when an agent needs to turn architecture notes, PRDs, Mermaid diagrams, or codebase context into an editable Excalidraw artifact and verify the result visually before handoff. The workflow starts a local canvas server, drives it through the CLI, MCP tools, REST API, or installed agent skill, creates and updates canvas elements, queries scene state, captures screenshots, fixes layout and label problems, saves snapshots, imports or exports .excalidraw files, and can commit diagrams alongside code. Invoke this instead of using Excalidraw normally when the diagram should be generated or maintained by an agent as part of a repo workflow, especially when the agent must see the canvas, iterate, and produce a deterministic file artifact. The scope boundary is an agent-operated Excalidraw workbench for diagram creation and maintenance; it is not the Excalidraw product itself, a generic canvas SDK, a one-shot image generator, or a generic MCP server listing.
What this skill actually does
Inputs and prerequisites: Node.js 20+, mcp-excalidraw-server via npx or npm, a local canvas server on 127.0.0.1:3000, and an MCP-capable or skill-capable coding agent such as Claude Code, Codex CLI, Cursor, OpenCode, or Claude Desktop.
Setup notes: Run npx -y mcp-excalidraw-server install-skill –dir for a portable agent skill, or configure the MCP server with npx -y mcp-excalidraw-server. Start the local canvas with npx -y mcp-excalidraw-server start, open http://127.0.0.1:3000 for screenshot feedback, then ask the agent to draw, inspect, revise, and export a diagram.
Source and verification boundary: use https://mcp-excalidraw-landing.vercel.app/ as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a MCP workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.