Skip to main content
Glama
sketchboard-excalidraw-mcp

sketchboard-excalidraw-mcp

# sketchboard-excalidraw-mcp

Excalidraw canvas authorship + headless-render MCP server. Slots next to inkscape-mcp and gimp-mcp as the vector/raster/diagram trio in the fleet.

Status: day 2. Server shell, package layout, and fleet standardization are in place. Headless rendering (render_svg/render_png) is real and tested. Canvas bridging, Mermaid conversion, and batch rendering are registered as MCP tools but return not_implemented - see docs/DESIGN.md for what's real vs planned.

What this is

A merge of two upstream approaches into one fleet-standard server:

  • Canvas workbench (planned base: fork of lesleslie/excalidraw-mcp, itself built on yctimlin/mcp_excalidraw): Python FastMCP server + TypeScript canvas server + React frontend for live, interactive diagram authorship. Not merged in yet - both upstreams are cloned for reference/cherry-picking under D:\Dev\repos\external\, but no canvas-bridge code has been ported into this repo. See the fork-drift open question in docs/DESIGN.md before that lands.

  • Headless rendering (real, implemented): ported from bassimeledath/excalidraw-render-mcp's TypeScript/agent-browser renderer into Python/Playwright, rather than vendoring a second Node stack. A warm Chromium instance renders Excalidraw element JSON to SVG/PNG via exportToSvg, reused across calls in the same process. Known gap: still loads @excalidraw/excalidraw from esm.sh at runtime rather than a locally vendored bundle, so it needs network access on first render and isn't version-pinned yet.

The two modes are deliberately decoupled: headless render tools work without the canvas server running (agent batch mode), while the canvas/Tauri app is for interactive human use. Both talk to the same backend; the desktop app is not a sidecar wrapping the Python server.

Related MCP server: excalidraw-export-mcp

Fork sources on this machine

Both upstream forks were cloned for reference/cherry-picking, not vendored wholesale:

  • D:\Dev\repos\external\excalidraw-mcp-lesleslie\

  • D:\Dev\repos\external\excalidraw-render-bassimeledath\

Planned extras

  • Mermaid-to-Excalidraw conversion, wrapping the official @excalidraw/mermaid-to-excalidraw npm package rather than reimplementing Mermaid parsing.

  • .excalidrawlib support for reusable fleet-diagram components (server boxes, transport arrows).

  • Batch-render command for the repo-README diagram pipeline across the fleet (~200 repos).

Ports

Port

Service

11107

Backend (FastMCP HTTP /mcp + REST)

11108

Frontend (Vite React canvas)

Registered in mcp-central-docs/operations/WEBAPP_PORTS.md.

License and attribution

MIT, same as both upstream sources. Credit chain: this project builds on lesleslie/excalidraw-mcp (which credits yctimlin/mcp_excalidraw) and borrows the headless-render architecture from bassimeledath/excalidraw-render-mcp. Font licensing (Excalidraw's default hand-drawn fonts ship under SIL OFL, not MIT) is tracked separately in NOTICE.md once the JS bundle is vendored.

Development

uv sync
uv run pytest
just release-dry

See docs/DESIGN.md for the day 1/2/3 build plan and the concrete technical decisions behind this scaffold.

Available Tools

4 tools
batch_renderA

Batch-render README diagrams across a list of fleet repos.

NOT IMPLEMENTED YET. Day 2/3 work: browser-context pool over the one warm Chromium instance (not one page reused sequentially), so a 200-repo run doesn't serialize behind a single tab.

Return Format

{"success": False, "error": str, "error_type": "not_implemented", "suggestions": list[str]}

Inputs: output_dir (required), repo_list_path (required). Returns: object

mermaid_to_excalidrawA

Convert a Mermaid diagram to Excalidraw elements and optionally render it.

NOT IMPLEMENTED YET. Planned to wrap the official @excalidraw/mermaid-to-excalidraw npm package via a small Node/Bun shim rather than reimplementing Mermaid parsing.

Return Format

{"success": False, "error": str, "error_type": "not_implemented", "suggestions": list[str]}

Inputs: output_path (required), mermaid_source (required). Returns: object

render_svgA

Render Excalidraw element JSON to SVG via headless Chromium (Playwright).

NOT IMPLEMENTED YET. Day 2 work: port bassimeledath's warm-Chromium exportToSvg approach into sketchboard_excalidraw_mcp/render.py using a locally vendored excalidraw JS bundle (no CDN dependency at runtime).

Return Format

{"success": False, "error": str, "error_type": "not_implemented", "suggestions": list[str]}

Inputs: output_path (required), elements_json (required). Returns: object

statusA

Report server identity and which capability groups are wired up yet.

This is the one real tool in the day-1 scaffold - everything else is registered but returns an explicit not_implemented result.

Return Format

{"server": str, "version": str, "capabilities": dict[str, str]}

Examples

status()

Inputs: no named parameters. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    The four tools have clearly distinct purposes: status for server info, render_svg for single-file rendering, mermaid_to_excalidraw for format conversion, and batch_render for multi-repo processing. Even though three are unimplemented, their intended roles are unambiguous and non-overlapping.

    Naming Consistency4/5

    All names use snake_case and mostly follow a verb_noun pattern (render_svg, batch_render), with mermaid_to_excalidraw being a noun_to_noun exception and status being a simple noun. The pattern is mostly consistent and readable, only minor deviations.

    Tool Count5/5

    Four tools is a well-scoped number for this server's purpose, covering status, single render, conversion, and batch processing. The count is neither too thin nor too heavy, and each tool has a clear intended role.

    Completeness1/5

    Three of four tools are marked NOT IMPLEMENTED YET and return explicit not_implemented errors. This creates severe dead ends for any agent attempting real diagram conversion or rendering; the only functional tool is status, leaving the server's stated purpose almost entirely unfulfilled.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers