excalidraw-editor-mcp

by creativedswork

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Open Excalidraw canvas

open_canvas

Opens a specific canvas file inside a designated project directory for viewing and editing.

Instructions

Opens one canvas inside its project.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectPath": "<projectPath>",
      "canvasPath": "<canvasPath>"
    },
    "name": "open_canvas"
  }
}

Input Schema

Name	Required	Description	Default
`canvasPath`	Yes	Full workspace-relative canvas path under projectPath, for example designs/m3/main.excalidraw. Never pass only main.excalidraw.
`projectPath`	Yes	Full workspace-relative project path, for example designs/m3.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Sep 7, 2026

TDQS

C2.1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations are absent, so the description must carry the behavioral burden. It gives no information about side effects, whether the operation is read-only or mutating, permission requirements, or what happens if the canvas or project does not exist. 'Open' is ambiguous regarding state changes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single vague sentence that essentially restates the title without adding meaningful detail. It is under-specified rather than appropriately concise, lacking the substance needed for an agent to understand the tool's behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description is the sole source of behavioral context. It provides no information on expected results, error conditions, or use cases, making it inadequate for a tool with two required parameters in a rich sibling landscape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema descriptions are thorough (100% coverage) with examples and explicit constraints like 'Never pass only main.excalidraw' and clarify the projectPath/canvasPath relationship. The tool description adds nothing beyond the schema, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Opens one canvas inside its project', which names a verb and a resource and distinguishes from open_project. However, it does not clarify what 'open' means operationally (load, select, display, set active), leaving ambiguity. It also does not differentiate from other canvas tools like check_canvas, capture_canvas, or inspect_canvas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus siblings such as open_project, list_canvases, or check_canvas. There are no prerequisites, exclusions, or context about when this tool is the right choice among the many canvas-related tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.