excalidraw-editor-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | Lists managed and discovered Excalidraw projects in the current Workspace. |
| create_projectC | Creates a managed project and opens its default canvas. |
| open_projectA | Opens the default canvas of an existing Excalidraw project. |
| inspect_projectC | Returns a bounded project and canvas summary. |
| rename_projectC | Renames a managed project when its project revision is current. |
| duplicate_projectC | Copies a managed project when its project revision is current. |
| delete_projectB | Deletes a managed project after exact path and revision confirmation. |
| list_canvasesA | Lists canvases in one project. |
| create_canvasB | Creates and opens an empty canvas inside one project. |
| open_canvasC | Opens one canvas inside its project. |
| inspect_canvasC | Returns filtered, paginated semantic elements and optionally a small standard document. |
| check_canvasC | Checks that a canvas is a valid bounded standard document. |
| add_canvas_assetC | Imports one bounded local raster image from the current Workspace. |
| remove_unused_assetsB | Atomically removes files not referenced by any live image element. |
| apply_canvas_changesB | Atomically applies semantic element and canvas changes at one base revision. |
| replace_canvasC | Validates, restores, and atomically replaces one complete standard document. |
| rename_canvasC | Renames a canvas inside the same managed project. |
| duplicate_canvasC | Copies a canvas inside the same project. |
| delete_canvasA | Deletes a canvas after exact path and revision confirmation. |
| export_canvasB | Opens the export View and downloads the saved canvas as JSON, SVG, or PNG. |
| capture_canvasA | Returns a standard MCP PNG rendered by the open Browser View plus text clipping diagnostics. Image-capable models can inspect the PNG; other models can still use the diagnostics. The View must already be open on the same saved canvas revision. |
| pull_canvasB | Returns the bound document when the app revision is stale. |
| report_canvas_captureC | Settles one pending Canvas Harness capture from the bound Browser View. |
| push_canvasC | Saves the bound standard document with compare-and-swap. |
| save_canvas_copyC | Saves the bound draft as a new canvas in the same project. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| excalidraw-authoring | Recommended inspect, edit, conflict retry, and View workflow. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| excalidraw-editor-view |
TDQS
Scored across 25 tools
Most tools have clear, distinct purposes, especially the project vs. canvas CRUD operations. Some slight overlap exists among retrieve/render/modify tools like inspect_canvas vs. pull_canvas, export_canvas vs. capture_canvas, and push_canvas vs. replace_canvas, but their descriptions sufficiently differentiate them.
Tool names consistently follow a verb_noun snake_case pattern across the entire set, such as list_projects, create_canvas, delete_canvas, and export_canvas. Pluralization is used logically for collection operations, and no mixed naming conventions are present.
At 25 tools, the set sits at the heavy end of the acceptable range. Each tool appears purpose-driven for Excalidraw editing workflows, but the count feels somewhat large and could be consolidated, especially around canvas mutation and retrieval operations.
The tool surface covers project and canvas CRUD, inspection, import/export, rendering, synchronization, and asset management. Minor gaps exist around more granular asset handling and direct deletion of specific assets, but the core Excalidraw editing lifecycle is well represented.