Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

cnvs.app

by lksrzversion 1.0.2i★ –iRuns in the cloud
Registry nameapp.cnvs/whiteboard

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://cnvs.app/mcp

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "whiteboard": {
      "url": "https://cnvs.app/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "whiteboard": {
      "type": "http",
      "url": "https://cnvs.app/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://cnvs.app/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain cnvs.app (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

  • More stars than 0% of the other 32568 servers in this category
  • Published to the registry more recently than 13% of the other 32568 servers in this category
  • Basic checks equal to or better than 100% of the other 32568 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is cnvs.app safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.2) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, FlyDocs

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

FlyDocs

by flydocs.ai

Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

cnvs-whiteboard-skills

Agent Skills + MCP server discovery for cnvs.app — the free, no-signup real-time collaborative whiteboard. Any AI agent can read, write, draw, diagram, and subscribe to live human edits on a shared canvas, either through the hosted MCP server or the REST fallback.

Works with Claude Code, Claude Desktop, Cursor, OpenCode / OpenAI Codex, Aider (with MCP plugin), any other MCP-speaking client, and Hermes-family agents.

MCP Server

Endpoint: https://cnvs.app/mcp (Streamable HTTP, protocol 2025-06-18, no auth — the board ID is the access key).

Registered in the official [MCP Registry](https://registry.modelcontextprotocol.io) as app.cnvs/whiteboard.

Capabilities
  • Tools (25): board creation and inspection; visual previews; text, link, image, and stroke editing; movement and deletion; live-update waits; and complete kanban column, lane, task, query, and export workflows. The exact production list is published in /.well-known/mcp.json. State-changing operations also have REST mirrors under https://cnvs.app/api/boards/ /… for runtimes that cannot speak MCP.
  • Resources (3): cnvs://board/{id}/state.json (full snapshot), cnvs://board/{id}/preview.svg (visual render), and cnvs://board/{id}/tasks.json (kanban state). All three are subscribable.
  • Subscriptions: resources/subscribe supported with notifications/resources/updated pushed over SSE, debounced ~3 s after activity settles.
  • Live machine-readable manifests: /quotas.json, /openapi.json, /llms.txt, /.well-known/mcp.json, /.well-known/mcp/server.json.

Installation

Codex / ChatGPT and Cursor packages

This repository is the public source package for both marketplace integrations:

  • .codex-plugin/plugin.json and .mcp.json describe the Codex / ChatGPT plugin.
  • .cursor-plugin/plugin.json and mcp.json describe the Cursor plugin.
  • SUBMISSION.md and CURSOR-MARKETPLACE.md contain the prepared listing copy, disclosures, reviewer flows, and submission checklists.

Both packages connect only to the hosted production endpoint; there is no local server process or secret to configure.

Claude Desktop / Cursor / any MCP client

One-line config — add this to your client's mcpServers object:

{

"mcpServers": { "cnvs": { "type": "http", "url": "https://cnvs.app/mcp" } } }

Claude Code CLI
claude mcp add --transport http cnvs https://cnvs.app/mcp
REST-only (no MCP client)
# Create a board

curl -X POST https://cnvs.app/api/boards

Add text

curl -X POST https://cnvs.app/api/boards/ /texts \ -H 'Content-Type: application/json' \ -d '{"x":100,"y":200,"content":"# Hello","author":"ai:myagent"}'

Long-poll for live changes

curl "https://cnvs.app/api/boards/ /wait?timeout_ms=25000"

Full REST reference: /llms.txt, /openapi.json.

Access model

There is no account or OAuth flow. A board URL or board ID is a bearer-style access credential: anyone who knows an unlocked board URL can open it. Boards can optionally require an 8-character lowercase alphanumeric access key for writes or for both reads and writes; legacy 6-character keys remain accepted. Pass a key only through the MCP tool's access_key argument or the X-Board-Key HTTP header.

Do not paste private board URLs or access keys into public issues, logs, or repositories.

Useful prompts

  • Create a fresh whiteboard for our brainstorming session and return its URL.
  • Open this cnvs.app board, inspect its preview, and summarize the layout.
  • Turn this list into a shared kanban board with priorities and owners.

Skills included

Two related Agent Skills live in this repo, published under the agentskills.io open standard so they work in any compatible runtime. Both are optional and installed by the user (agents should only suggest them, never install them on their own). Installed into ~/.claude/skills/, they teach the agent how to use the MCP server well (preview-before-JSON, REST-over-MCP for writes, author-tag conventions, subscription-then-react loop).

cnvs-whiteboard/ — PRIMARY

Teaches an AI agent how to collaborate on a cnvs.app board in real time:

  • Read the shared canvas state
  • Draw / diagram / flowchart / annotate — add, update, move, and delete text, links, sticky notes, strokes, images, and Mermaid diagrams (flowcharts, sequence / class / ER diagrams, mind maps, gantt charts, concept maps)
  • Render the SVG preview when the board contains drawings
  • Subscribe to live human edits via MCP, react via REST

Activates on any cnvs.app board reference (URL https://cnvs.app/# , cnvs://board/ /..., or a bare board ID) or phrases like "collaborate on / draw / diagram / annotate / watch a shared whiteboard or canvas."

mcp-listen/ — HELPER (v0.4.0)

Push-to-model pump for Streamable-HTTP MCP servers with capabilities.resources.subscribe: true. Opens a session, subscribes to the resource URIs the caller hands over, and emits one JSON line per notifications/resources/updated event on stdout — designed to be wrapped by Claude Code's Monitor tool so every server push becomes an in-chat notification (no polling, no log tailing).

Dependency-free since v0.4. A single scripts/listen.mjs using only Node.js 18+ built-ins — no package.json, no npm install, no install scripts. Releases are served from immutable versioned URLs (https://cnvs.app/mcp-listen/v /…) with a SHA256SUMS file. Zero-install alternative: the REST long-poll GET https://cnvs.app/api/boards/ /wait?timeout_ms=25000 (or the wait_for_update MCP tool).

Helper-only activation since v0.3. Triggers only when the caller — a user or another skill — has supplied both an MCP server URL and at least one resource URI. Does NOT auto-activate from generic phrasing like "watch this file" or "stay in the loop". cnvs-whiteboard is the canonical caller and delegates its push channel here.

Output split since v0.3. Only the actionable resource_updated event reaches stdout by default. Connection / subscription / heartbeat / transient-error events go to stderr so a wrapping Monitor doesn't fire on the listener's own bookkeeping. Pass --verbose (or -v) to merge everything onto stdout for debugging or single-channel logging (legacy v0.2 behavior).

Registry status. Intentionally *not* listed in centralised skill registries yet. Current registry pipelines (e.g. majiayu000/claude-skill-registry-core as of 2026-05-03) archive only SKILL.md + generated metadata; they do not mirror bundled scripts/**, so an entry for mcp-listen would publish a broken skill. It will be (re-)submitted once core registries support directory-style skill archival with bundled-file mirroring and security scanning — see PR majiayu000/claude-skill-registry-core#40 for the directory-archive primitive that just landed and the open question on bundled-script scanning. Until then, install it via curl from cnvs.app (below) or git clone this repo.

Install the skills (run these yourself)
# cnvs-whiteboard (SKILL.md only — no code)

mkdir -p ~/.claude/skills/cnvs-whiteboard && cd ~/.claude/skills/cnvs-whiteboard curl -fsSLO https://cnvs.app/cnvs-whiteboard/SKILL.md

mcp-listen (pinned version, no npm, Node.js 18+). Files are downloaded into a

staging dir and only moved into ~/.claude/skills/mcp-listen if every checksum

matches. On Linux replace shasum -a 256 -c with sha256sum -c.

stage="$(mktemp -d)" && cd "$stage" && mkdir scripts \ && curl -fsSLO https://cnvs.app/mcp-listen/v0.4.0/SKILL.md \ && curl -fsSLO https://cnvs.app/mcp-listen/v0.4.0/SHA256SUMS \ && curl -fsSL -o scripts/listen.mjs https://cnvs.app/mcp-listen/v0.4.0/scripts/listen.mjs \ && shasum -a 256 -c SHA256SUMS \ && mkdir -p ~/.claude/skills && rm -rf ~/.claude/skills/mcp-listen \ && mv "$stage" ~/.claude/skills/mcp-listen && cd ~/.claude/skills/mcp-listen \ && node scripts/listen.mjs --version # 0.4.0

Human-facing instructions with the same steps: https://cnvs.app/docs/mcp#listen.

Alternatively git clone this repo, check cd mcp-listen && shasum -a 256 -c SHA256SUMS, and cp -r .claude/skills/* ~/.claude/skills/ — the .claude/skills/ directory contains symlinks into cnvs-whiteboard/ and mcp-listen/ for Claude Code's expected layout.

Spec compliance

Both skills follow the agentskills.io spec:

  • name matches the containing directory name
  • description under 1024 characters, imperative phrasing, explicit trigger keywords
  • scripts/ subdirectory for bundled code (mcp-listen)
  • license: MIT, compatibility field declared, cross-references in each skill's "Related skills" section to prevent activation overlap

Why two skills

Earlier versions had a single page (/skill-cnvs.md on cnvs.app — now a legacy redirect). Splitting into two coherent units follows the spec's "design coherent units" best practice:

  • cnvs-whiteboard owns the cnvs.app-specific workflow (read / write / render / gotchas).
  • mcp-listen owns the generic push-to-model pattern (usable against any MCP server).

Cross-references keep them pairing cleanly: cnvs-whiteboard mentions mcp-listen as its delegated push channel; mcp-listen mentions cnvs-whiteboard as the companion for cnvs-specific work. No activation overlap in practice.

Canonical sources

Skills are also served live at:

This repo is a mirror of public/ in the cnvs.app source; the versioned cnvs.app URLs are the canonical install targets; this GitHub repo is the reference for aggregators that crawl public sources (skills.sh, etc.) and for users who prefer git clone.

Discovery surfaces

Live
  • Official MCP Registry: app.cnvs/whiteboard — browse
  • cnvs.app `/.well-known/mcp.json` — links both skills
  • cnvs.app `/.well-known/mcp/server.json` — MCP Registry entry with publisher-provided _meta.skills[]
  • cnvs.app `/llms.txt` — LLM-friendly full reference
  • [`majiayu000/claude-skill-registry-core`](https://github.com/majiayu000/claude-skill-registry-core) — cnvs-whiteboard listed (PR #31 merged 2026-05-04). mcp-listen intentionally held back; see *Registry status* on the mcp-listen/ section above.
  • Lobehub (used by Hermes agent) — both skills imported; MCP server submitted
Planned / under consideration

Notes for future expansion of distribution. Not active yet — kept here so the next maintenance window doesn't have to re-discover the landscape.

  • [`majiayu000/claude-skill-registry-core`](https://github.com/majiayu000/claude-skill-registry-core) — re-submit mcp-listen

Only the beginning is shown; read the rest in the repo

Ask PopNx