io.github.tldraw/tldraw
REMOTE · TLDRAW-MCP-APP.TLDRAW.WORKERS.DEV · 2 COMPONENTS · SCANNED SEP 24
Draw and visually collaborate with your agents on tldraw's canvas.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 980 tokens (~140/item across 7 items; 6 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage74
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 21% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
How do I install the io.github.tldraw/tldraw MCP server?
io.github.tldraw/tldraw is a hosted endpoint at https://tldraw-mcp-app.tldraw.workers.dev/sse, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · tldraw-mcp-app.tldraw.workers.dev
claude mcp add --transport http tldraw-tldraw 'https://tldraw-mcp-app.tldraw.workers.dev/sse'
{
"mcpServers": {
"tldraw-tldraw": {
"url": "https://tldraw-mcp-app.tldraw.workers.dev/sse"
}
}
} {
"servers": {
"tldraw-tldraw": {
"type": "http",
"url": "https://tldraw-mcp-app.tldraw.workers.dev/sse"
}
}
} [mcp_servers.tldraw-tldraw] url = "https://tldraw-mcp-app.tldraw.workers.dev/sse"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tldraw-tldraw": {
"type": "remote",
"url": "https://tldraw-mcp-app.tldraw.workers.dev/sse",
"enabled": true
}
}
} openclaw mcp add tldraw-tldraw --url 'https://tldraw-mcp-app.tldraw.workers.dev/sse' --transport streamable-http
mcp_servers:
tldraw-tldraw:
url: "https://tldraw-mcp-app.tldraw.workers.dev/sse" {
"McpServers": {
"tldraw-tldraw": {
"Transport": "http",
"Url": "https://tldraw-mcp-app.tldraw.workers.dev/sse"
}
}
} assistant mcp add tldraw-tldraw -t streamable-http -u 'https://tldraw-mcp-app.tldraw.workers.dev/sse'
{
"mcpServers": {
"tldraw-tldraw": {
"type": "http",
"url": "https://tldraw-mcp-app.tldraw.workers.dev/sse"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 72
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://tldraw-mcp-app.tldraw.workers.dev/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tldraw.workers.dev | CN=WE1,O=Google Trust Services,C=US | 20 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a99e6099120aa31c13b7d68f468c6d1a |
| SANs: tldraw.workers.dev, *.tldraw.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tldraw-mcp-app.tldraw.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 404 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://tldraw-mcp-app.tldraw.workers.dev/sse | Verified | 200 | |
| http (plaintext) | http://tldraw-mcp-app.tldraw.workers.dev/sse | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
_exec_callback Exec Callback ~51
App-only: widget calls this to resolve a pending exec request.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | – |
| error | string | – | – |
| execKey | string | – | – |
| result | object | – | – |
No output schema declared.
No examples provided.
_get_canvas_state Get Canvas State ~33
App-only: get the latest checkpoint for a canvas by its canvasId.
| Name | Type | Req | Description |
|---|---|---|---|
| canvasId | string | yes | – |
No output schema declared.
No examples provided.
exec Execute Code ~484
Execute JavaScript code on a tldraw canvas. The code runs in the widget with access to the live `editor` instance, helper functions, and normal js. Use the `search` tool first to discover available Editor methods and shape types. Each canvas has a unique `canvasId`. Omit `canvasId` to create a new blank canvas. To edit an existing canvas, pass the `canvasId` that was returned by a previous exec call. Shapes and text grow depending on the amount of text they have. Use clever scripting to ensure there are no unintended overlaps. Examples: - Create a rectangle: editor.createShape({ _type: 'rectangle', shapeId: 'box1', x: 200, y: 120, w: 320, h: 180, text: 'Hello' }) - Connect shapes with an arrow: editor.createShape({ _type: 'arrow', shapeId: 'a1', fromId: 'box1', toId: 'box2', x1: 0, y1: 0, x2: 100, y2: 0 }) - Select and zoom: editor.select('box1'); editor.zoomToSelection() - Read shapes: return editor.getCurrentPageShapes() - Distribute evenly: editor.distributeShapes(editor.getSelectedShapeIds(), 'horizontal') - Box around shapes: boxShapes(['box1', 'box2'], { text: 'Group label', color: 'blue' }) - Stack shapes dynamically: editor.createShape({ _type: 'rectangle', shapeId: 'a', x: 0, y: 0, w: 300, h: 200, text: 'First box\nwith wrapping text' }); const bounds = editor.getShapePageBounds('a'); editor.createShape({ _type: 'rectangle', shapeId: 'b', x: 0, y: bounds.maxY + 20, w: 300, h: 200, text: 'Below first' })
| Name | Type | Req | Description |
|---|---|---|---|
| canvasId | string | – | Canvas ID to edit. Omit to create a new blank canvas. Pass a canvasId from a previous exec result to continue editing that canvas. |
| code | string | yes | JavaScript code to execute. Has access to `editor` (tldraw Editor instance) and helper functions. |
No output schema declared.
No examples provided.
read_checkpoint Read Checkpoint ~27
App-only: read shapes from a checkpoint by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| checkpointId | string | yes | – |
No output schema declared.
No examples provided.
save_checkpoint Save Checkpoint ~72
App-only: save shapes to a checkpoint (from user edits). shapesJson and assetsJson must be JSON array strings.
| Name | Type | Req | Description |
|---|---|---|---|
| assetsJson | string | – | – |
| bindingsJson | string | – | – |
| canvasId | string | – | – |
| checkpointId | string | yes | – |
| shapesJson | string | yes | – |
No output schema declared.
No examples provided.
search Search Editor API ~209
Search the tldraw Editor API spec by writing JavaScript that receives a `spec` object and returns a result. The spec contains: spec.members (all Editor methods/properties with name, kind, signature, description, category), spec.categories (category names), spec.types.shapes (focused shape type definitions with props), spec.types.shapeTypes (list of all shape type strings), spec.helpers (exec helper functions with descriptions, params, examples). Examples: - Find shape methods: return spec.members.filter(m => m.category === "shapes").map(m => ({ name: m.name, signature: m.signature })) - Get arrow shape props: return spec.types.shapes.find(s => s.shapeType === "arrow") - List all categories: return spec.categories - Find a helper: return spec.helpers.find(h => h.name === "createArrowBetweenShapes")
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | JavaScript code that receives `spec` and returns a result. Must use `return` to produce output. |
No output schema declared.
No examples provided.
What is the io.github.tldraw/tldraw MCP server?
io.github.tldraw/tldraw is an MCP server listed in the public MCP registry as io.github.tldraw/tldraw. Draw and visually collaborate with your agents on tldraw's canvas. This page covers its hosted endpoint (https://tldraw-mcp-app.tldraw.workers.dev/sse).
Is the io.github.tldraw/tldraw MCP server safe to use?
io.github.tldraw/tldraw scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.tldraw/tldraw MCP server expose?
io.github.tldraw/tldraw exposes 6 tools: search, exec, _exec_callback, _get_canvas_state, read_checkpoint, save_checkpoint. Their descriptions and schemas cost roughly 876 tokens of context every time the server is loaded.
Does the io.github.tldraw/tldraw MCP server require authentication?
No. We connected to io.github.tldraw/tldraw without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.tldraw/tldraw MCP server still maintained?
io.github.tldraw/tldraw is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.