excalidraw-room-mcp

create_room

Create an empty live Excalidraw room, join it, and receive a shareable link with the encryption key for inviting collaborators. Returns the handle taken in the room.

Instructions

Create a new empty live-collaboration room, join it, and return the excalidraw.com link for a person to open. The link contains the encryption key; share it only with people who should see the drawing. The result states the handle this server took in the room.

Input Schema

TableJSON Schema

Name	Required	Description
`handle`	No	Name to appear as in the room: lowercase letters, digits and hyphens, 1 to 32 characters. Made unique against the agents already in the room by appending -2, -3, and the result text states the handle taken. Defaults to root-claude.
`nearbyRadius`	No	How far a neighbourhood query reaches around a mention, in canvas px, and the distance placement keeps between clusters. 250 by default; room_status reports it, and list_mentions, wait_for_mention, show_room, read_scene near and snapshot_scene near use it when they are given no radius of their own.
`agentReplyDepth`	No	How many agent replies deep a chain an agent started may run before this agent stops hearing it, 0 to 5. 1 by default, so an agent may answer another agent once and the conversation goes on only if a person writes again; 0 means agent-started chains are never answered, even with answerAgentMentions on. A chain a person started is never bounded. This agent takes the bound at its own join and applies it to what it hears; it is not synchronised across the room, so two agents in one room may hold different bounds. room_status reports it as "agentReplyDepth: <n>".

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.8.0Sep 11, 2026

addedInput schema / properties / agentReplyDepth

Added value: +{
+  "description": "How many agent replies deep a chain an agent started may run before this agent stops hearing it, 0 to 5. 1 by default, so an agent may answer another agent once and the conversation goes on only if a person writes again; 0 means agent-started chains are never answered, even with answerAgentMentions on. A chain a person started is never bounded. This agent takes the bound at its own join and applies it to what it hears; it is not synchronised across the room, so two agents in one room may hold different bounds. room_status reports it as \"agentReplyDepth: <n>\".",
+  "maximum": 5,
+  "minimum": 0,
+  "type": "integer"
+}

Changed3 schema fields changedv0.7.1Sep 10, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / handle

Added value: +{
+  "description": "Name to appear as in the room: lowercase letters, digits and hyphens, 1 to 32 characters. Made unique against the agents already in the room by appending -2, -3, and the result text states the handle taken. Defaults to root-claude.",
+  "type": "string"
+}

addedInput schema / properties / nearbyRadius

Added value: +{
+  "description": "How far a neighbourhood query reaches around a mention, in canvas px, and the distance placement keeps between clusters. 250 by default; room_status reports it, and list_mentions, wait_for_mention, show_room, read_scene near and snapshot_scene near use it when they are given no radius of their own.",
+  "minimum": 0,
+  "type": "number"
+}

First observedv0.1.0Sep 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries behavioral disclosure on its own. It discloses that the creator joins the room, the returned link includes an encryption key, the link should only go to trusted people, and the result states the server's handle. It does not cover all possible lifecycle effects, but this is sufficient for a simple creation tool.

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?

Three short sentences, front-loaded with the core action. Each sentence earns its place: creating/joining/returning, the encryption-key security note, and the result-handle disclosure. No redundancy with the schema.

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

Completeness4/5

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

No output schema exists, so the description must explain what is returned, and it does: the excalidraw.com link and the resulting handle. It does not specify the exact return type or edge cases, but for a tool with three fully documented optional parameters, this is complete enough.

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 description coverage is 100%, so the input schema fully documents handle, nearbyRadius, and agentReplyDepth. The description adds no extra meaning to these parameters, which is fine at the baseline of 3, but it also does nothing to enrich them.

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 names a specific verb and resource: 'Create a new empty live-collaboration room, join it, and return the excalidraw.com link.' It clearly contrasts with sibling tools like open_room and join_room by emphasizing 'new empty' and the creation/join side effect.

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

Usage Guidelines4/5

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

The context for when to use this tool is clear: a new collaboration room is needed, and it must be created, joined, and shared. It does not explicitly list alternatives or exclusion criteria, but the 'new empty' wording makes the difference from open_room/join_room evident.

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

Deploy Server

create_room

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools