# cnvs.app (remote · cnvs.app)

Real-time collaborative whiteboard — AI agents and humans edit the same board live over MCP.

- Trust score: 59/100 (low)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `cnvs.app`: 59/100 (this document), [markdown](https://verifymcp.io/servers/app-cnvs-whiteboard/cnvs.md), [page](https://verifymcp.io/servers/app-cnvs-whiteboard/cnvs)

## Channel facts

- Endpoint: `https://cnvs.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 25 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 8314 tokens (~296/item across 28 items; 25 tools + 3 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 49% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http app-cnvs-whiteboard https://cnvs.app/mcp
```

### Codex

```toml
[mcp_servers.app-cnvs-whiteboard]
url = "https://cnvs.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-cnvs-whiteboard": {
      "type": "remote",
      "url": "https://cnvs.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-cnvs-whiteboard --url https://cnvs.app/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-cnvs-whiteboard:
    url: "https://cnvs.app/mcp"
```

### Other

```json
{
  "mcpServers": {
    "app-cnvs-whiteboard": {
      "type": "http",
      "url": "https://cnvs.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 59, +5)

- [security] Tool “create_board” rewrote its description, which is the text the model reads
- [functional] Schema quality: poor → excellent
- [cosmetic] “create_board” reworded the description of “content”

### 2026-08-02 (score 54, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 53, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 53, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 54, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 53, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 52)

First indexed and scored.

## MCP tools (25)

### `open_board` (~190 tokens)

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.

Input parameters:

- `access_key` (string): 6-char board access key (a-z, 0-9) when the board is locked. 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.
- `url_or_id` (string, required): Full board URL (https://cnvs.app/#<id>) or bare UUID.

### `create_board` (~1027 tokens)

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.

Input parameters:

- `author` (string): Author tag stamped on every created item (e.g. 'ai:plai'). Defaults to 'ai:import'.
- `autolayout` (boolean): 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.
- `content` (object): 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?, aut…
- `lock` (string): PIN-lock the board atomically at create time; the plaintext key is returned ONCE as `access_key`.
- `mode` (string): Board mode. Defaults to 'draw'.
- `template` (string): Starter column set when mode is 'todo' and content.columns is empty/absent. Defaults to 'kanban'.

### `get_board` (~212 tokens)

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.

Input parameters:

- `access_key` (string): 6-char board access key (a-z, 0-9) when the board is locked. 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.
- `board_id` (string, required)

### `get_preview` (~176 tokens)

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`.

Input parameters:

- `access_key` (string): 6-char board access key (a-z, 0-9) when the board is locked. 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.
- `board_id` (string, required)

### `add_text` (~489 tokens)

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.

Input parameters:

- `access_key` (string): 6-char board access key (a-z, 0-9) when the board is locked. 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.
- `author` (string): Author tag, defaults to ai:claude.
- `board_id` (string, required)
- `color` (string): 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', 'light…
- `content` (string, required)
- `diagram` (boolean): Render as a framed diagram box (2px border in the text colour, centred text). Mutually exclusive with postit.
- `id` (string): Optional stable id; generated when omitted.
- `postit` (boolean)
- `width` (number): Explicit width in px (160–4096).
- `x` (number, required)
- `y` (number, required)

### `add_link` (~167 tokens)

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).

Input parameters:

- `access_key` (string): 6-char board access key (a-z, 0-9) when the board is locked. 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.
- `author` (string)
- `board_id` (string, required)
- `url` (string, required)
- `x` (number, required)
- `y` (number, required)

### `add_image` (~271 tokens)

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.

Input parameters:

- `access_key` (string): 6-char board access key (a-z, 0-9) when the board is locked. 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.
- `author` (string)
- `board_id` (string, required)
- `data_url` (string, required)
- `height` (number, required)
- `id` (string)
- `thumb_data_url` (string)
- `width` (number, required)
- `x` (number, required)
- `y` (number, required)

### `draw_stroke` (~387 tokens)

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.

Input parameters:

- `access_key` (string): 6-char board access key (a-z, 0-9) when the board is locked. 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.
- `author` (string)
- `board_id` (string, required)
- `color` (string)
- `id` (string)
- `points` (required): Points as [[x,y],...], flat [x1,y1,x2,y2,...], or a JSON string of either.

### `move` (~249 tokens)

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.

Input parameters:

- `access_key` (string): 6-char board access key (a-z, 0-9) when the board is locked. 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.
- `board_id` (string, required)
- `id` (string, required)
- `kind` (string): Item kind. Defaults to `text`.
- `x` (number, required)
- `y` (number, required)

### `erase` (~181 tokens)

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.

Input parameters:

- `access_key` (string): 6-char board access key (a-z, 0-9) when the board is locked. 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.
- `board_id` (string, required)
- `id` (string, required)
- `kind` (string, required)

### `wait_for_update` (~416 tokens)

Long-poll: blocks until the next edit lands on this board, then returns. 

WHEN 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.

BEHAVIOUR: 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).

Input parameters:

- `access_key` (string): 6-char board access key (a-z, 0-9) when the board is locked. 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.
- `board_id` (string, required)
- `timeout_ms` (number)

### `set_board_mode` (~309 tokens)

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.

Input parameters:

- `access_key` (string): 6-char board access key (a-z, 0-9) when the board is locked. 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.
- `board_id` (string, required)
- `mode` (string, required): Board mode.
- `template` (string): 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 / Fi…

### `create_column` (~270 tokens)

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`.

Input parameters:

- `access_key` (string): 6-char board access key (a-z, 0-9) when the board is locked. 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.
- `author` (string): Author tag, defaults to ai:claude.
- `board_id` (string, required)
- `color` (string): Title color: 'red', 'blue', 'green', or 'auto' (default).
- `lane` (integer): Row index for multi-row layouts. Defaults to 0.
- `sort` (number): Float ordering key (ascending). Defaults to 0.
- `title` (string, required)

### `update_column` (~206 tokens)

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.

Input parameters:

- `access_key` (string): 6-char board access key (a-z, 0-9) when the board is locked. 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.
- `author` (string): Author tag, defaults to ai:claude.
- `board_id` (string, required)
- `color` (string): Title color: 'red', 'blue', 'green', or 'auto' (default).
- `id` (string, required)
- `lane` (integer): Row index for multi-row layouts.
- `sort` (number): Float ordering key (ascending).
- `title` (string)

### `delete_column` (~113 tokens)

Delete a kanban column by id. Tasks in the column are removed with it. Get the id from `list_tasks`.

Input parameters:

- `access_key` (string): 6-char board access key (a-z, 0-9) when the board is locked. 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.
- `board_id` (string, required)
- `id` (string, required)

### `create_task` (~314 tokens)

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.

Input parameters:

- `access_key` (string): 6-char board access key (a-z, 0-9) when the board is locked. 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.
- `assignee` (string)
- `author` (string): Author tag, defaults to ai:claude.
- `board_id` (string, required)
- `column_id` (string, required)
- `description` (string)
- `done` (boolean): Whether the task is completed (checked off). Defaults to false.
- `due_date` (string): ISO 8601 date.
- `name` (string, required)
- `priority` (string): High / Medium / Low. Omit for none.
- `sort` (number): Float ordering key within the column. Defaults to 0.

### `update_task` (~265 tokens)

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.

Input parameters:

- `access_key` (string): 6-char board access key (a-z, 0-9) when the board is locked. 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.
- `assignee` (string)
- `author` (string): Author tag, defaults to ai:claude.
- `board_id` (string, required)
- `column_id` (string)
- `description` (string)
- `done` (boolean): Whether the task is completed (checked off).
- `due_date` (string): ISO 8601 date.
- `id` (string, required)
- `name` (string)
- `priority` (string)
- `sort` (number)

### `move_task` (~146 tokens)

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.

Input parameters:

- `access_key` (string): 6-char board access key (a-z, 0-9) when the board is locked. 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.
- `board_id` (string, required)
- `column_id` (string, required)
- `id` (string, required)
- `sort` (number, required)

### `delete_task` (~105 tokens)

Delete a task (card) by id. Get the id from `list_tasks`.

Input parameters:

- `access_key` (string): 6-char board access key (a-z, 0-9) when the board is locked. 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.
- `board_id` (string, required)
- `id` (string, required)

### `list_tasks` (~165 tokens)

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.

Input parameters:

- `access_key` (string): 6-char board access key (a-z, 0-9) when the board is locked. 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.
- `board_id` (string, required)

### `set_lane` (~199 tokens)

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`.

Input parameters:

- `access_key` (string): 6-char board access key (a-z, 0-9) when the board is locked. 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.
- `author` (string): Author tag, defaults to ai:claude.
- `board_id` (string, required)
- `lane` (integer, required): Row index (>= 0).
- `title` (string): Row title; empty string clears it.

### `set_column_width` (~147 tokens)

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`.

Input parameters:

- `access_key` (string): 6-char board access key (a-z, 0-9) when the board is locked. 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.
- `board_id` (string, required)
- `width` (number, required): Column width in px, clamped to [200, 480].

### `create_tasks` (~215 tokens)

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).

Input parameters:

- `access_key` (string): 6-char board access key (a-z, 0-9) when the board is locked. 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.
- `author` (string): Author tag applied to every task, defaults to ai:claude.
- `board_id` (string, required)
- `tasks` (array, required): Array of task objects to create.

### `query_tasks` (~279 tokens)

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`.

Input parameters:

- `access_key` (string): 6-char board access key (a-z, 0-9) when the board is locked. 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.
- `assignee` (string): Exact-match assignee filter.
- `board_id` (string, required)
- `done` (boolean)
- `due_after` (string): ISO date; due_date > this.
- `due_before` (string): ISO date; due_date < this.
- `overdue` (boolean): Only tasks past due and not done.
- `priority` (string)

### `export_tasks` (~176 tokens)

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.

Input parameters:

- `access_key` (string): 6-char board access key (a-z, 0-9) when the board is locked. 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.
- `board_id` (string, required)
- `format` (string): Output format. Defaults to 'markdown'.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-cnvs-whiteboard/cnvs#diagnostics

## Score history

- 2026-08-03: 59
- 2026-08-02: 54
- 2026-08-01: 53
- 2026-07-31: 53
- 2026-07-30: 53
- 2026-07-29: 54
- 2026-07-28: 53
- 2026-07-27: 53
- 2026-07-26: 52

## Links

- Remote endpoint: https://cnvs.app/mcp
- Repository: https://github.com/lksrz/cnvs-whiteboard-skills
- Website: https://cnvs.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-cnvs-whiteboard/cnvs/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-cnvs-whiteboard/cnvs/changelog.json
- HTML version of this page: https://verifymcp.io/servers/app-cnvs-whiteboard/cnvs