Ext Ops Panel
Open dashboard
Comparison

CanvasKeep vs Canvs

CanvasKeep is an MCP server published by CanvasKeep. Marketplaces we read that list it: 1 (Official MCP Registry). Canvs is an MCP server published by voronkovm. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceCanvasKeepCanvs
Official MCP Registry Listed
Version: 0.6.2
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.0
No figure published
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

CanvasKeep vs Canvs
FactCanvasKeepCanvs
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (canvaskeep-mcp)Remote server (app.canvs.io/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 2Not published
LicenceNot statedNot stated
Repository (differs)github.com/canvaskeep/canvaskeep-mcpNot stated
Changes in the last 7 days (differs)20
First seen (differs)2026-10-182026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 301 (16 h ago)

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

CanvasKeep

In its own words, on Official MCP Registry:

Create and edit Excalidraw diagrams in your CanvasKeep workspace, with auto-layout and folders.

Canvs

In its own words, on Official MCP Registry:

AI-powered diagrams, mind maps, flowcharts on a free unlimited collaborative whiteboard

How to run each

CanvasKeep As a local MCP server: npm package

Claude Code
claude mcp add --env "CANVASKEEP_API_KEY=<YOUR_CANVASKEEP_API_KEY>" --env "CANVASKEEP_MASTER_KEY=<YOUR_CANVASKEEP_MASTER_KEY>" --transport stdio canvaskeep-mcp -- npx -y canvaskeep-mcp

Requires: CANVASKEEP_API_KEY (secret), CANVASKEEP_MASTER_KEY (secret)

Canvs As a remote MCP server

Claude Code
claude mcp add --transport http canvs https://app.canvs.io/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Canvs has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of Canvs publish no settings it asks for, so we do not compare settings.

What it can do: CanvasKeep · What it can do: Canvs · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built