Server definition
- Hash
- sha256:1e7dfc32ade197b9a9845f4276afb54d1785b835cb29b8642908062718602756
- What it is
- What a remote MCP server returned when asked what it offers: 25 tools
The blob, as servednamed by its sha256
{
"instructions": "READ THIS FIRST — it saves you time and produces a visibly better result. This server exposes a live cnvs.app whiteboard shared with human collaborators in real time.\n\n=== The three rules that matter most ===\n\nA. ALWAYS fetch `get_preview(board_id)` (or `GET https://cnvs.app/svg-preview/<id>`) when the board has any strokes or images. The JSON snapshot gives you numbers (point arrays, bboxes); the SVG preview shows you shapes. A \"47-point red stroke at (323,1771)-(585,2066)\" is a *heart* — you will not know that from JSON. Seeing only coordinates is functional blindness. One preview fetch per meaningful edit is cheap.\n\nB. PREFER THE REST API over MCP tools for WRITES. Every MCP tool has a 1:1 REST equivalent (`add_text` ↔ `POST /api/boards/<id>/texts`, `move` ↔ `POST /api/boards/<id>/<kind>/<id>/move`, etc.). REST is universal (any HTTP client), stateless (no session bookkeeping), and doesn't consume your per-turn tool-call budget. Reserve MCP tools for environments where you can't `curl`. Full REST reference: https://cnvs.app/llms.txt and https://cnvs.app/openapi.json.\n\nC. IF YOU WANT TO REACT TO HUMAN EDITS IN REAL TIME (the board is shared — humans are drawing alongside you): install the `cnvs-whiteboard` Agent Skill at https://cnvs.app/cnvs-whiteboard/SKILL.md and its companion `mcp-listen` at https://cnvs.app/mcp-listen/SKILL.md. The pair turns MCP subscription pushes into real in-chat notifications that re-invoke the model. Without them most chat-UI MCP clients consume the SSE push in session cache without ever waking the model — you end up blind to edits until the user types again. Install: `mkdir -p ~/.claude/skills/mcp-listen && cd ~/.claude/skills/mcp-listen && curl -O https://cnvs.app/mcp-listen/SKILL.md -O https://cnvs.app/mcp-listen/package.json --create-dirs -o scripts/listen.mjs https://cnvs.app/mcp-listen/scripts/listen.mjs && npm install`.\n\n=== Access locks ===\n\nBoards can be PIN-locked. Two modes: `write` (anyone reads, only key-holders write) and `all` (key required for read AND write). If a request needs a key, the server responds with JSON-RPC error code -32001 (`board_locked`) carrying `data.lockMode`. Pass the current 8-character lowercase alphanumeric key (legacy 6-character keys remain accepted) by either:\n • setting the `X-Board-Key` HTTP header on the JSON-RPC POST, or\n • adding `access_key: \"<code>\"` to the tool's arguments (or to `params` on `resources/read` / `resources/subscribe`).\nCreate a lock with `POST /api/boards/<id>/lock {mode}` — the key is returned ONCE in the body. There is no recovery: lose the key, lose the board. REST mirror endpoints: `/lock`, `/unlock`, `/verify-key`.\n\n=== Color (named only) ===\n\nPass ink color as a NAME, not hex — think \"click the button\", not \"specify RGB\". Accepted values (case-insensitive): `auto` / `\"\"` / `black` / omitted for theme-aware ink (dark in light mode, light in dark mode), or a named palette color: `red`, `blue`, `green`, `orange`, `yellow`, `pink`, `purple`, `maroon`, `brown`, `gray`, `lightgray`, `teal`, `sage`, `sky`, `lavender`. ANYTHING ELSE including a literal hex like `#ff3b30` silently clamps to auto. This prevents AI writes from being invisible on the opposite theme. Applies to texts, strokes, and move responses.\n\n=== Mechanics ===\n\n1. Start with `open_board(url_or_id)` to resolve the canonical id. This auto-subscribes your session so `notifications/resources/updated` starts flowing immediately. Need a fresh board and no URL was given? Call `create_board` (or `curl -X POST https://cnvs.app/api/boards`) — the server generates the id. `create_board` can also pre-fill the whole board in one atomic call (`content` with texts/lines/images or kanban columns/tasks, `autolayout: true` to place unpositioned items, `lock` to PIN-lock at create time) — prefer it over N per-item calls when building a board from scratch.\n2. Coordinates: infinite canvas, +x right, +y DOWN (standard SVG). Text nodes ~200–400 px wide, ~40–80 px per line; leave 20–40 px gaps between nodes. Re-fetch `get_preview` before placing to find free space — editing blind produces overlapping clutter.\n3. Author tag: prefix `ai:<label>` (defaults to `ai:claude` for MCP writes, `ai:rest` for REST writes). Tag is IMMUTABLE after creation — a human moving your sticker does NOT relabel it.\n4. Prefer updating existing items (pass the same `id` to `add_text`) over creating duplicates. `move` repositions any item kind (text/link/line/image) without re-sending the content.\n5. Notifications debounce ~3 s after activity settles, so a burst of edits produces one wake-up, not dozens.\n6. Limits (live manifest at https://cnvs.app/quotas.json): standard REST/MCP 60 req / 10 s per board; valid server-side X-Import-Token 600 / 10 s. WebSocket stays 60 / 10 s. Also: 5 MiB body cap, 500 texts (100 k chars each), 50 images (~900 kB each, 10 MB total), 2000 strokes. Quota errors return 413 (REST) or -32000 (MCP) with a `kind` field naming the specific limit hit.\n\n=== Tasks (kanban mode) ===\n\nA board is either 'draw' (freeform whiteboard, the default) or 'todo' (kanban). `set_board_mode(board_id, mode)` chooses, switchable WHILE the board is empty of drawings/tasks (empty/seeded columns don't count, so a cleared board can switch again). Setting 'todo' auto-seeds three columns (To do / In progress / Done). Manage the board with `create_column` / `update_column` / `delete_column` and `create_task` / `update_task` / `move_task` / `delete_task`; read the whole board with `list_tasks` (returns `{ mode, columns, tasks }`). REST mirrors live at `/api/boards/<id>/tasks` (and `/columns`, etc.). `cnvs://board/<id>/tasks.json` is subscribable — subscribe for live `notifications/resources/updated` pushes just like state.json.",
"tools": [
{
"description": "Place a raster or SVG image on the board at (x, y) with explicit width/height in board pixels. `data_url` MUST be a `data:image/(png|jpeg|gif|webp|svg+xml);base64,...` string ≤ ~900 kB; hosted URLs are not accepted. Strongly recommended: also pass a tiny `thumb_data_url` (≤8 kB JPEG/PNG/WebP, ~64 px on the long edge) — it is embedded into the SVG preview so OTHER AI viewers (and you, on later `get_preview` calls) can actually see the image instead of a placeholder box.",
"inputSchema": {
"properties": {
"access_key": {
"description": "8-character lowercase alphanumeric board access key when the board is locked (legacy 6-character lowercase alphanumeric keys are also accepted). Equivalent to setting the `X-Board-Key` HTTP header on the JSON-RPC POST. Omit for unlocked boards. Obtain via POST /api/boards/<id>/lock.",
"type": "string"
},
"author": {
"type": "string"
},
"board_id": {
"type": "string"
},
"data_url": {
"type": "string"
},
"height": {
"type": "number"
},
"id": {
"type": "string"
},
"thumb_data_url": {
"type": "string"
},
"width": {
"type": "number"
},
"x": {
"type": "number"
},
"y": {
"type": "number"
}
},
"required": [
"board_id",
"x",
"y",
"width",
"height",
"data_url"
],
"type": "object"
},
"name": "add_image",
"outputSchema": null
},
{
"description": "Drop a URL capsule onto the board — rendered as a clickable pill showing the hostname. Use this instead of `add_text` when the node is just a link; the capsule styling signals clickability to humans. Same coordinate rules as `add_text` (+x right, +y down).",
"inputSchema": {
"properties": {
"access_key": {
"description": "8-character lowercase alphanumeric board access key when the board is locked (legacy 6-character lowercase alphanumeric keys are also accepted). Equivalent to setting the `X-Board-Key` HTTP header on the JSON-RPC POST. Omit for unlocked boards. Obtain via POST /api/boards/<id>/lock.",
"type": "string"
},
"author": {
"type": "string"
},
"board_id": {
"type": "string"
},
"url": {
"type": "string"
},
"x": {
"type": "number"
},
"y": {
"type": "number"
}
},
"required": [
"board_id",
"x",
"y",
"url"
],
"type": "object"
},
"name": "add_link",
"outputSchema": null
},
{
"description": "Create a NEW text node, or update an existing one (pass the same `id` to overwrite content/position in place — preferred over creating a duplicate). Supports cnvs markup (Markdown-ish) and Mermaid diagrams in the content. When using Mermaid, the ENTIRE content of this text node must be a single Mermaid diagram (one ```mermaid fenced block and nothing else — no heading, no prose before or after). If you need prose + a diagram, create two separate text nodes. `postit: true` renders as a yellow sticky; `diagram: true` renders as a framed box (2px border in the text colour, centred text) — the two are mutually exclusive. Coordinates are in board-world pixels, +x right, +y DOWN; pick a spot that does not overlap existing items (check `get_preview` first). Default width auto-fits content up to ~320 px; pass `width` for explicit wrapping (160–4096). Keep content under 100 000 chars.",
"inputSchema": {
"properties": {
"access_key": {
"description": "8-character lowercase alphanumeric board access key when the board is locked (legacy 6-character lowercase alphanumeric keys are also accepted). Equivalent to setting the `X-Board-Key` HTTP header on the JSON-RPC POST. Omit for unlocked boards. Obtain via POST /api/boards/<id>/lock.",
"type": "string"
},
"author": {
"description": "Author tag, defaults to ai:claude.",
"type": "string"
},
"board_id": {
"type": "string"
},
"color": {
"description": "Named ink only (no hex). Accepted (case-insensitive): 'auto'/''/'black'/omitted for theme-aware ink, or 'red', 'blue', 'green', 'orange', 'yellow', 'pink', 'purple', 'maroon', 'brown', 'gray', 'lightgray', 'teal', 'sage', 'sky', 'lavender'. Anything else (including a literal hex) silently clamps to auto.",
"type": "string"
},
"content": {
"type": "string"
},
"diagram": {
"description": "Render as a framed diagram box (2px border in the text colour, centred text). Mutually exclusive with postit.",
"type": "boolean"
},
"id": {
"description": "Optional stable id; generated when omitted.",
"type": "string"
},
"postit": {
"type": "boolean"
},
"width": {
"description": "Explicit width in px (160–4096).",
"type": "number"
},
"x": {
"type": "number"
},
"y": {
"type": "number"
}
},
"required": [
"board_id",
"x",
"y",
"content"
],
"type": "object"
},
"name": "add_text",
"outputSchema": null
},
{
"description": "Create a fresh board in ONE call — optionally pre-filled with content, auto-laid-out, and/or PIN-locked at create time. Mirrors the extended `POST /api/boards` REST body exactly (same server-side implementation). With no arguments it returns a blank draw board; `mode: 'todo'` (+ optional `template`) seeds a kanban board. `content` imports initial items atomically: everything is validated FIRST and the board is created only if every item passes — on any invalid item you get a structured error naming its kind + index and NOTHING is created. `autolayout: true` (draw mode) fills in x/y for texts/images that omit them (deterministic masonry grid; explicit coordinates are never touched). `lock: 'write'|'all'` locks the board atomically with creation and returns the plaintext `access_key` ONCE — there is no recovery. The response's `imported` counts confirm what was created, `ids` returns the server-minted item ids per kind in the order you supplied them (index i of `ids.texts` is the id created for `content.texts[i]`; `ids.columns` is empty when the columns came from the template seed, and lanes have no id — they are keyed by board + lane index), and `embed_url` (the `?embed=1#<id>` iframe view) is returned for any board readable without a key — it is omitted for `lock:'all'` boards, whose embed frame can't read the board anonymously. Prefer this over open_board + N per-item calls when you are building a whole board from scratch.",
"inputSchema": {
"properties": {
"author": {
"description": "Author tag stamped on every created item (e.g. 'ai:plai'). Defaults to 'ai:import'.",
"type": "string"
},
"autolayout": {
"description": "Draw mode only: fill x/y for texts/images that omit them (deterministic masonry). Without it, items missing coordinates are rejected. No-op in todo mode.",
"type": "boolean"
},
"content": {
"description": "Initial board content, applied atomically at create time. Draw mode: `texts` [{x?, y?, content, color?, width?, postit?, diagram?, kind?, author?, sourceId?}], `lines` [{points, color?, anchors?, author?}] (alias `strokes`), `images` [{x?, y?, dataUrl, width, height, author?, sourceId?}]. Todo mode: `columns` [{title, lane?, color?, author?}] (array order = sort order), `tasks` [{columnIndex, name, description?, due_date?, priority?, assignee?, done?, color?, author?}] (columnIndex indexes into content.columns, or into the template-seeded columns when content.columns is empty), `lanes` [{lane, title, author?}], `colWidth`. Every item's optional `author` is its CREATOR tag (same 1-80 char [A-Za-z0-9:_-.] rule as elsewhere) and is never rewritten later — omit it to inherit the top-level `author`, or set it per item to preserve the original authorship when restoring somebody else's board. Item ids are ALWAYS minted server-side and returned in `ids`; you cannot choose them. To keep anchored strokes, give a text/image an optional `sourceId` (unique string, <=128 chars, write-only — never stored, never the row id) and reference it from `lines[].anchors.start.id` / `.end.id`: matching ids are rewritten to the minted id, unmatched ids are left as-is and render as a free stroke end. Kanban structures with a non-todo mode (or draw items with mode 'todo') are rejected with `content_mode_mismatch`. The combined input arrays may contain at most 2550 entries. At most 10 lane-title entries are accepted, every title must reference a lane used by a created column, and each lane index may be named AT MOST ONCE — a second entry for the same lane is rejected (naming that second entry's index) instead of collapsing last-write-wins, which would overwrite the first entry's author. `tasks[].done` must be a real boolean (or omitted/null for not-done): a truthy stand-in such as the string \"false\" is rejected rather than coerced, so a card is never imported as completed by accident. Standard per-board quotas also apply, and the 5 MB request-body cap is the real ceiling for image-heavy imports. A valid X-Import-Token selects higher REST/MCP and board-create rate tiers, but never changes these content limits.",
"type": "object"
},
"lock": {
"description": "PIN-lock the board atomically at create time; the plaintext key is returned ONCE as `access_key`.",
"enum": [
"write",
"all"
],
"type": "string"
},
"mode": {
"description": "Board mode. Defaults to 'draw'.",
"enum": [
"draw",
"todo"
],
"type": "string"
},
"template": {
"description": "Starter column set when mode is 'todo' and content.columns is empty/absent. Defaults to 'kanban'.",
"enum": [
"kanban",
"sprint",
"bugs"
],
"type": "string"
}
},
"type": "object"
},
"name": "create_board",
"outputSchema": null
},
{
"description": "Add a kanban column (swimlane) to a 'todo' board. Generates and returns a stable column id. `sort` is a float ordering key (ascending); omit to default to 0. `lane` is an integer row index for multi-row layouts (defaults to 0). `color` is an optional title color ('red' / 'blue' / 'green', or 'auto' / omit for default). To rename, reorder, recolor or move between lanes later use `update_column`.",
"inputSchema": {
"properties": {
"access_key": {
"description": "8-character lowercase alphanumeric board access key when the board is locked (legacy 6-character lowercase alphanumeric keys are also accepted). Equivalent to setting the `X-Board-Key` HTTP header on the JSON-RPC POST. Omit for unlocked boards. Obtain via POST /api/boards/<id>/lock.",
"type": "string"
},
"author": {
"description": "Author tag, defaults to ai:claude.",
"type": "string"
},
"board_id": {
"type": "string"
},
"color": {
"description": "Title color: 'red', 'blue', 'green', or 'auto' (default).",
"type": "string"
},
"lane": {
"description": "Row index for multi-row layouts. Defaults to 0.",
"type": "integer"
},
"sort": {
"description": "Float ordering key (ascending). Defaults to 0.",
"type": "number"
},
"title": {
"type": "string"
}
},
"required": [
"board_id",
"title"
],
"type": "object"
},
"name": "create_column",
"outputSchema": null
},
{
"description": "Create a task (card) in a column on a 'todo' board. Generates and returns a stable task id. `column_id` must reference an existing column (see `list_tasks`). `description` is free-form prose stored on the card; `priority` is one of 'H' | 'M' | 'L' (omit for none); `due_date` is an ISO 8601 date string; `assignee` is free text (name / initials / email). `sort` is a float ordering key within the column (ascending), defaulting to 0.",
"inputSchema": {
"properties": {
"access_key": {
"description": "8-character lowercase alphanumeric board access key when the board is locked (legacy 6-character lowercase alphanumeric keys are also accepted). Equivalent to setting the `X-Board-Key` HTTP header on the JSON-RPC POST. Omit for unlocked boards. Obtain via POST /api/boards/<id>/lock.",
"type": "string"
},
"assignee": {
"type": "string"
},
"author": {
"description": "Author tag, defaults to ai:claude.",
"type": "string"
},
"board_id": {
"type": "string"
},
"column_id": {
"type": "string"
},
"description": {
"type": "string"
},
"done": {
"description": "Whether the task is completed (checked off). Defaults to false.",
"type": "boolean"
},
"due_date": {
"description": "ISO 8601 date.",
"type": "string"
},
"name": {
"type": "string"
},
"priority": {
"description": "High / Medium / Low. Omit for none.",
"enum": [
"H",
"M",
"L"
],
"type": "string"
},
"sort": {
"description": "Float ordering key within the column. Defaults to 0.",
"type": "number"
}
},
"required": [
"board_id",
"column_id",
"name"
],
"type": "object"
},
"name": "create_task",
"outputSchema": null
},
{
"description": "Bulk-create multiple task cards in one call — far cheaper than calling `create_task` N times. Pass `tasks`: an array of task objects, each with `column_id` (required) + the same fields `create_task` accepts (`name`, `description`, `due_date`, `priority`, `assignee`, `done`, `sort`). Returns the array of created ids in order. Stops at the first invalid item and reports its index; items before it are still created (not transactional).",
"inputSchema": {
"properties": {
"access_key": {
"description": "8-character lowercase alphanumeric board access key when the board is locked (legacy 6-character lowercase alphanumeric keys are also accepted). Equivalent to setting the `X-Board-Key` HTTP header on the JSON-RPC POST. Omit for unlocked boards. Obtain via POST /api/boards/<id>/lock.",
"type": "string"
},
"author": {
"description": "Author tag applied to every task, defaults to ai:claude.",
"type": "string"
},
"board_id": {
"type": "string"
},
"tasks": {
"description": "Array of task objects to create.",
"items": {
"properties": {
"assignee": {
"type": "string"
},
"column_id": {
"type": "string"
},
"description": {
"type": "string"
},
"done": {
"type": "boolean"
},
"due_date": {
"description": "ISO 8601 date.",
"type": "string"
},
"name": {
"type": "string"
},
"priority": {
"enum": [
"H",
"M",
"L"
],
"type": "string"
},
"sort": {
"type": "number"
}
},
"required": [
"column_id",
"name"
],
"type": "object"
},
"type": "array"
}
},
"required": [
"board_id",
"tasks"
],
"type": "object"
},
"name": "create_tasks",
"outputSchema": null
},
{
"description": "Delete a kanban column by id. Tasks in the column are removed with it. Get the id from `list_tasks`.",
"inputSchema": {
"properties": {
"access_key": {
"description": "8-character lowercase alphanumeric board access key when the board is locked (legacy 6-character lowercase alphanumeric keys are also accepted). Equivalent to setting the `X-Board-Key` HTTP header on the JSON-RPC POST. Omit for unlocked boards. Obtain via POST /api/boards/<id>/lock.",
"type": "string"
},
"board_id": {
"type": "string"
},
"id": {
"type": "string"
}
},
"required": [
"board_id",
"id"
],
"type": "object"
},
"name": "delete_column",
"outputSchema": null
},
{
"description": "Delete a task (card) by id. Get the id from `list_tasks`.",
"inputSchema": {
"properties": {
"access_key": {
"description": "8-character lowercase alphanumeric board access key when the board is locked (legacy 6-character lowercase alphanumeric keys are also accepted). Equivalent to setting the `X-Board-Key` HTTP header on the JSON-RPC POST. Omit for unlocked boards. Obtain via POST /api/boards/<id>/lock.",
"type": "string"
},
"board_id": {
"type": "string"
},
"id": {
"type": "string"
}
},
"required": [
"board_id",
"id"
],
"type": "object"
},
"name": "delete_task",
"outputSchema": null
},
{
"description": "Draw a freehand stroke on the board. Use for arrows, underlines, connector lines, annotations, or simple shapes — a straight line needs two points, a rough circle wants ~20. Stroke width is fixed at 3 px; `color` is a NAME, not hex (case-insensitive): 'auto'/''/'black'/omitted for theme-aware ink, or 'red', 'blue', 'green', 'orange', 'yellow', 'pink', 'purple', 'maroon', 'brown', 'gray', 'lightgray', 'teal', 'sage', 'sky', 'lavender' — anything else (including a literal hex like '#ff0000') silently clamps to auto. Accepts three equivalent point formats — pick whichever your MCP client serialises cleanly: nested `[[x,y],[x,y],...]`, flat `[x1,y1,x2,y2,...]`, or a JSON string of either. Some clients (Claude Code as of 2026-04) drop nested arrays during tool-call serialisation, so prefer the flat form or the JSON-string form when in doubt. To delete a stroke later, use `erase` with `kind: 'line'` and the id returned here.",
"inputSchema": {
"properties": {
"access_key": {
"description": "8-character lowercase alphanumeric board access key when the board is locked (legacy 6-character lowercase alphanumeric keys are also accepted). Equivalent to setting the `X-Board-Key` HTTP header on the JSON-RPC POST. Omit for unlocked boards. Obtain via POST /api/boards/<id>/lock.",
"type": "string"
},
"author": {
"type": "string"
},
"board_id": {
"type": "string"
},
"color": {
"type": "string"
},
"id": {
"type": "string"
},
"points": {
"description": "Points as [[x,y],...], flat [x1,y1,x2,y2,...], or a JSON string of either."
}
},
"required": [
"board_id",
"points"
],
"type": "object"
},
"name": "draw_stroke",
"outputSchema": null
},
{
"description": "Delete a single item by id. `kind` MUST match the item type: 'text' for text nodes, 'line' for freehand strokes, 'image' for images — the wrong kind silently targets the wrong table and is a common mistake. Get the id + type from `get_board` (texts[], lines[], images[]). There is no bulk/erase-all tool: loop if you need to delete multiple items.",
"inputSchema": {
"properties": {
"access_key": {
"description": "8-character lowercase alphanumeric board access key when the board is locked (legacy 6-character lowercase alphanumeric keys are also accepted). Equivalent to setting the `X-Board-Key` HTTP header on the JSON-RPC POST. Omit for unlocked boards. Obtain via POST /api/boards/<id>/lock.",
"type": "string"
},
"board_id": {
"type": "string"
},
"id": {
"type": "string"
},
"kind": {
"enum": [
"text",
"line",
"image"
],
"type": "string"
}
},
"required": [
"board_id",
"id",
"kind"
],
"type": "object"
},
"name": "erase",
"outputSchema": null
},
{
"description": "Export a 'todo' board's columns + tasks as a single text document. `format` is 'markdown' (a checklist grouped by column, the default) or 'csv' (one row per task with column/name/priority/assignee/due_date/done). Returns the rendered text. Same data as the GET /api/boards/<id>/tasks.md and tasks.csv REST endpoints.",
"inputSchema": {
"properties": {
"access_key": {
"description": "8-character lowercase alphanumeric board access key when the board is locked (legacy 6-character lowercase alphanumeric keys are also accepted). Equivalent to setting the `X-Board-Key` HTTP header on the JSON-RPC POST. Omit for unlocked boards. Obtain via POST /api/boards/<id>/lock.",
"type": "string"
},
"board_id": {
"type": "string"
},
"format": {
"description": "Output format. Defaults to 'markdown'.",
"enum": [
"markdown",
"csv"
],
"type": "string"
}
},
"required": [
"board_id"
],
"type": "object"
},
"name": "export_tasks",
"outputSchema": null
},
{
"description": "Full structured JSON state of a board: texts (id, x, y, content, color, width, postit, author), strokes (id, points, color, author), images (id, x, y, width, height, dataUrl, thumbDataUrl, author; heavy base64 >8 kB elided to dataUrl:null, tiny images inlined). Use this for EXACT ids/coordinates/content (needed for `move`, `erase`, editing a text by id). For visual layout (where is empty space? what overlaps?) call `get_preview` instead — it's much cheaper for spatial reasoning than a huge JSON dump.",
"inputSchema": {
"properties": {
"access_key": {
"description": "8-character lowercase alphanumeric board access key when the board is locked (legacy 6-character lowercase alphanumeric keys are also accepted). Equivalent to setting the `X-Board-Key` HTTP header on the JSON-RPC POST. Omit for unlocked boards. Obtain via POST /api/boards/<id>/lock.",
"type": "string"
},
"board_id": {
"type": "string"
}
},
"required": [
"board_id"
],
"type": "object"
},
"name": "get_board",
"outputSchema": null
},
{
"description": "Compact schematic SVG render of the board (typically a few kB even for dense boards). Returns both an image/svg+xml content block (you can SEE it) and the raw SVG text. CALL THIS any time you need to understand where things are — before placing new items, before deciding whether the canvas is crowded, before picking a free region. AI-authored items get a purple border so you can tell which contributions were yours. For precise text content prefer `get_board`.",
"inputSchema": {
"properties": {
"access_key": {
"description": "8-character lowercase alphanumeric board access key when the board is locked (legacy 6-character lowercase alphanumeric keys are also accepted). Equivalent to setting the `X-Board-Key` HTTP header on the JSON-RPC POST. Omit for unlocked boards. Obtain via POST /api/boards/<id>/lock.",
"type": "string"
},
"board_id": {
"type": "string"
}
},
"required": [
"board_id"
],
"type": "object"
},
"name": "get_preview",
"outputSchema": null
},
{
"description": "Read the full kanban state of a 'todo' board: `{ mode, columns, tasks }`, both ordered by their `sort` key (ascending). Each task carries its hot fields (name, due_date, priority, assignee, done, column_id, sort) plus an opaque `content` JSON string (holds the description). Use this to get exact column/task ids before updating, moving or deleting.",
"inputSchema": {
"properties": {
"access_key": {
"description": "8-character lowercase alphanumeric board access key when the board is locked (legacy 6-character lowercase alphanumeric keys are also accepted). Equivalent to setting the `X-Board-Key` HTTP header on the JSON-RPC POST. Omit for unlocked boards. Obtain via POST /api/boards/<id>/lock.",
"type": "string"
},
"board_id": {
"type": "string"
}
},
"required": [
"board_id"
],
"type": "object"
},
"name": "list_tasks",
"outputSchema": null
},
{
"description": "Reposition an existing item to a new (x, y) without retyping its content. Works for every item kind: `text` and `link` set the top-left to (x, y); `line` translates every point so the stroke's bounding box top-left lands at (x, y); `image` sets the top-left like text. `kind` defaults to `text` for backward compat with older callers. Find the id + kind via `get_board`. Prefer `move` over re-creating an item when only the location changes — it preserves the id, content, author and avoids a round-trip of base64 bytes for images.",
"inputSchema": {
"properties": {
"access_key": {
"description": "8-character lowercase alphanumeric board access key when the board is locked (legacy 6-character lowercase alphanumeric keys are also accepted). Equivalent to setting the `X-Board-Key` HTTP header on the JSON-RPC POST. Omit for unlocked boards. Obtain via POST /api/boards/<id>/lock.",
"type": "string"
},
"board_id": {
"type": "string"
},
"id": {
"type": "string"
},
"kind": {
"description": "Item kind. Defaults to `text`.",
"enum": [
"text",
"link",
"line",
"image"
],
"type": "string"
},
"x": {
"type": "number"
},
"y": {
"type": "number"
}
},
"required": [
"board_id",
"id",
"x",
"y"
],
"type": "object"
},
"name": "move",
"outputSchema": null
},
{
"description": "Move a task to a column at a given sort position — the kanban drag-and-drop primitive. `column_id` is the destination column and `sort` its float order key (ascending) within that column.",
"inputSchema": {
"properties": {
"access_key": {
"description": "8-character lowercase alphanumeric board access key when the board is locked (legacy 6-character lowercase alphanumeric keys are also accepted). Equivalent to setting the `X-Board-Key` HTTP header on the JSON-RPC POST. Omit for unlocked boards. Obtain via POST /api/boards/<id>/lock.",
"type": "string"
},
"board_id": {
"type": "string"
},
"column_id": {
"type": "string"
},
"id": {
"type": "string"
},
"sort": {
"type": "number"
}
},
"required": [
"board_id",
"id",
"column_id",
"sort"
],
"type": "object"
},
"name": "move_task",
"outputSchema": null
},
{
"description": "ALWAYS call this first when given a board URL or ID. Resolves the canonical board id and auto-creates the board row if it does not exist yet. Returns a summary (item counts, authors). After this, call BOTH `get_preview` and `get_board` before editing so you can see the layout visually AND know the exact ids/coordinates — do not skip `get_preview`, otherwise you will place new items blindly on top of existing ones.",
"inputSchema": {
"properties": {
"access_key": {
"description": "8-character lowercase alphanumeric board access key when the board is locked (legacy 6-character lowercase alphanumeric keys are also accepted). Equivalent to setting the `X-Board-Key` HTTP header on the JSON-RPC POST. Omit for unlocked boards. Obtain via POST /api/boards/<id>/lock.",
"type": "string"
},
"url_or_id": {
"description": "Full board URL (https://cnvs.app/#<id>) or bare UUID.",
"type": "string"
}
},
"required": [
"url_or_id"
],
"type": "object"
},
"name": "open_board",
"outputSchema": null
},
{
"description": "Read tasks from a 'todo' board with server-side filtering — handy for 'what's overdue?' / 'what's assigned to X?' without pulling the whole board. All filters are optional and AND together: `assignee` (exact match), `priority` ('H'|'M'|'L'), `done` (boolean), `overdue` (true → due_date strictly before today, not done), `due_before` / `due_after` (ISO date window on due_date). Returns `{ boardId, mode, tasks }` — tasks ordered by sort, each with the same fields as `list_tasks`.",
"inputSchema": {
"properties": {
"access_key": {
"description": "8-character lowercase alphanumeric board access key when the board is locked (legacy 6-character lowercase alphanumeric keys are also accepted). Equivalent to setting the `X-Board-Key` HTTP header on the JSON-RPC POST. Omit for unlocked boards. Obtain via POST /api/boards/<id>/lock.",
"type": "string"
},
"assignee": {
"description": "Exact-match assignee filter.",
"type": "string"
},
"board_id": {
"type": "string"
},
"done": {
"type": "boolean"
},
"due_after": {
"description": "ISO date; due_date > this.",
"type": "string"
},
"due_before": {
"description": "ISO date; due_date < this.",
"type": "string"
},
"overdue": {
"description": "Only tasks past due and not done.",
"type": "boolean"
},
"priority": {
"enum": [
"H",
"M",
"L"
],
"type": "string"
}
},
"required": [
"board_id"
],
"type": "object"
},
"name": "query_tasks",
"outputSchema": null
},
{
"description": "Choose whether this board is a freeform whiteboard ('draw', the default) or a kanban task board ('todo'). Mode is switchable WHENEVER the board is empty of real content: drawings (text/strokes/images) and tasks. Empty or seeded columns DON'T count (switching to 'draw' clears them), so a cleared board can be switched again, and you can flip draw<->todo freely until the first stroke/text/image or task lands. Setting 'todo' auto-seeds three starter columns (To do / In progress / Done). Returns `{ mode, columns }`. Use the task/column tools (`create_task`, `create_column`, …) once the board is in 'todo' mode.",
"inputSchema": {
"properties": {
"access_key": {
"description": "8-character lowercase alphanumeric board access key when the board is locked (legacy 6-character lowercase alphanumeric keys are also accepted). Equivalent to setting the `X-Board-Key` HTTP header on the JSON-RPC POST. Omit for unlocked boards. Obtain via POST /api/boards/<id>/lock.",
"type": "string"
},
"board_id": {
"type": "string"
},
"mode": {
"description": "Board mode.",
"enum": [
"draw",
"todo"
],
"type": "string"
},
"template": {
"description": "Optional starter column template when mode is 'todo': 'kanban' (To do / In progress / Done, the default), 'sprint' (Backlog / Sprint / Review / Done), or 'bugs' (Triage / Confirmed / In progress / Fixed). Unknown/omitted falls back to 'kanban'.",
"type": "string"
}
},
"required": [
"board_id",
"mode"
],
"type": "object"
},
"name": "set_board_mode",
"outputSchema": null
},
{
"description": "Set the shared kanban column width in pixels for a 'todo' board (all columns share one width). Clamped to [200, 480]. Read the current value as `colWidth` from `list_tasks`.",
"inputSchema": {
"properties": {
"access_key": {
"description": "8-character lowercase alphanumeric board access key when the board is locked (legacy 6-character lowercase alphanumeric keys are also accepted). Equivalent to setting the `X-Board-Key` HTTP header on the JSON-RPC POST. Omit for unlocked boards. Obtain via POST /api/boards/<id>/lock.",
"type": "string"
},
"board_id": {
"type": "string"
},
"width": {
"description": "Column width in px, clamped to [200, 480].",
"type": "number"
}
},
"required": [
"board_id",
"width"
],
"type": "object"
},
"name": "set_column_width",
"outputSchema": null
},
{
"description": "Set (or clear) the title of a kanban row (lane). Lanes group columns into horizontal swimlanes; a lane is identified by its integer `lane` index (the same index columns carry). Pass a `title` to name the row, or an empty string to clear it. Read current lane titles + the shared column width via `list_tasks`.",
"inputSchema": {
"properties": {
"access_key": {
"description": "8-character lowercase alphanumeric board access key when the board is locked (legacy 6-character lowercase alphanumeric keys are also accepted). Equivalent to setting the `X-Board-Key` HTTP header on the JSON-RPC POST. Omit for unlocked boards. Obtain via POST /api/boards/<id>/lock.",
"type": "string"
},
"author": {
"description": "Author tag, defaults to ai:claude.",
"type": "string"
},
"board_id": {
"type": "string"
},
"lane": {
"description": "Row index (>= 0).",
"type": "integer"
},
"title": {
"description": "Row title; empty string clears it.",
"type": "string"
}
},
"required": [
"board_id",
"lane"
],
"type": "object"
},
"name": "set_lane",
"outputSchema": null
},
{
"description": "Rename, reorder, recolor or move an existing kanban column. Requires the column `id` (from `list_tasks`). Pass `title`, `sort`, `lane` and/or `color` to change them.",
"inputSchema": {
"properties": {
"access_key": {
"description": "8-character lowercase alphanumeric board access key when the board is locked (legacy 6-character lowercase alphanumeric keys are also accepted). Equivalent to setting the `X-Board-Key` HTTP header on the JSON-RPC POST. Omit for unlocked boards. Obtain via POST /api/boards/<id>/lock.",
"type": "string"
},
"author": {
"description": "Author tag, defaults to ai:claude.",
"type": "string"
},
"board_id": {
"type": "string"
},
"color": {
"description": "Title color: 'red', 'blue', 'green', or 'auto' (default).",
"type": "string"
},
"id": {
"type": "string"
},
"lane": {
"description": "Row index for multi-row layouts.",
"type": "integer"
},
"sort": {
"description": "Float ordering key (ascending).",
"type": "number"
},
"title": {
"type": "string"
}
},
"required": [
"board_id",
"id"
],
"type": "object"
},
"name": "update_column",
"outputSchema": null
},
{
"description": "Update an existing task by `id` (from `list_tasks`). Pass only the fields you want to change: `name`, `description`, `due_date`, `priority` ('H'|'M'|'L'), `assignee`, `done` (true once completed), `column_id` (to reassign), `sort`. To move a card between columns while setting its order, `move_task` is the dedicated tool.",
"inputSchema": {
"properties": {
"access_key": {
"description": "8-character lowercase alphanumeric board access key when the board is locked (legacy 6-character lowercase alphanumeric keys are also accepted). Equivalent to setting the `X-Board-Key` HTTP header on the JSON-RPC POST. Omit for unlocked boards. Obtain via POST /api/boards/<id>/lock.",
"type": "string"
},
"assignee": {
"type": "string"
},
"author": {
"description": "Author tag, defaults to ai:claude.",
"type": "string"
},
"board_id": {
"type": "string"
},
"column_id": {
"type": "string"
},
"description": {
"type": "string"
},
"done": {
"description": "Whether the task is completed (checked off).",
"type": "boolean"
},
"due_date": {
"description": "ISO 8601 date.",
"type": "string"
},
"id": {
"type": "string"
},
"name": {
"type": "string"
},
"priority": {
"enum": [
"H",
"M",
"L"
],
"type": "string"
},
"sort": {
"type": "number"
}
},
"required": [
"board_id",
"id"
],
"type": "object"
},
"name": "update_task",
"outputSchema": null
},
{
"description": "Long-poll: blocks until the next edit lands on this board, then returns. \n\nWHEN TO CALL THIS: if your MCP client does NOT surface `notifications/resources/updated` events from `resources/subscribe` back to the model (most chat clients do not — they receive the SSE event but don't inject it into your context), this tool is how you 'wait for the human' inside a single turn. Typical flow: you draw / write what you were asked to, then instead of ending your turn you call `wait_for_update(board_id)`. When the human adds, moves, or erases something, the call returns and you refresh with `get_preview` / `get_board` and continue the collaboration. Great for turn-based interactions (games like tic-tac-toe, brainstorming where you respond to each sticky the user drops, sketch-and-feedback loops, etc.). If your client DOES deliver resource notifications natively, prefer `resources/subscribe` — it's cheaper and has no timeout ceiling.\n\nBEHAVIOUR: resolves ~3 s after the edit burst settles (same debounce as the push notifications — this is intentional so drags and long strokes collapse into one wake-up). Returns `{ updated: true, timedOut: false }` on a real edit, or `{ updated: false, timedOut: true }` if nothing happened within `timeout_ms`. On timeout, just call it again to keep waiting; chaining calls is cheap. `timeout_ms` is clamped to [1000, 55000]; default 25000 (leaves headroom under typical 60 s proxy timeouts).",
"inputSchema": {
"properties": {
"access_key": {
"description": "8-character lowercase alphanumeric board access key when the board is locked (legacy 6-character lowercase alphanumeric keys are also accepted). Equivalent to setting the `X-Board-Key` HTTP header on the JSON-RPC POST. Omit for unlocked boards. Obtain via POST /api/boards/<id>/lock.",
"type": "string"
},
"board_id": {
"type": "string"
},
"timeout_ms": {
"type": "number"
}
},
"required": [
"board_id"
],
"type": "object"
},
"name": "wait_for_update",
"outputSchema": null
}
]
}Verify it yourself
curl -s https://api.teppi.xyz/v1/evidence/sha256:1e7dfc32ade197b9a9845f4276afb54d1785b835cb29b8642908062718602756 | sha256sum