excalidraw-editor-mcp

Overview Schema Source Related Servers Discussions Admin

Open Excalidraw project

open_project

Open an existing Excalidraw project's default canvas by specifying its workspace-relative path. Load the diagram for viewing or editing.

Instructions

Opens the default canvas of an existing Excalidraw 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>"
    },
    "name": "open_project"
  }
}

Input Schema

Name	Required	Description	Default
`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

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states what is opened but does not mention whether the action is read-only, whether it creates or modifies any state, or what happens if the project does not exist.

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

Conciseness5/5

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

The description is a single, focused sentence with no filler. The key scoping information, 'default canvas of an existing project', is front-loaded and directly useful for tool selection.

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

Completeness3/5

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

For a one-parameter open operation, the description plus schema are minimally complete. However, with no annotations and no output schema, it lacks explicit side-effect or error behavior and does not mention alternative sibling tools such as open_canvas.

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?

The input schema already documents projectPath with constraints and an example, so the description does not need to add much. It adds the notion that the project must already exist, but this is a mild addition beyond the schema.

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

Purpose5/5

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

The description uses a specific verb ('opens') with a precise target ('default canvas of an existing Excalidraw project'). The phrase 'default canvas' distinguishes it from open_canvas, and 'existing' distinguishes it from create_project.

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

Usage Guidelines3/5

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

The description implies the tool is for existing projects and their default canvas, but it does not explicitly say when to prefer open_canvas for non-default canvases or when not to use this tool. The usage context is implied rather than explicitly guided.

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