Ext Ops Panel
Open dashboard
Comparison

Figma vs CanvasKeep

Figma is a plugin bundle for AI coding tools published by Figma. Marketplaces we read that list it: 1 (Codex: openai-curated (openai/plugins)). CanvasKeep is an MCP server published by CanvasKeep. 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
MarketplaceFigmaCanvasKeep
Codex: openai-curated (openai/plugins) Listed
Version: 2.0.20
Forks (GitHub): 964
Stars (GitHub): 7 535
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.6.2
Forks (GitHub): 0
Stars (GitHub): 0
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

Figma vs CanvasKeep
FactFigmaCanvasKeep
Marketplaces that list it11
Stars (GitHub) (differs)7 535 (better)0 (worse)
Forks (GitHub) (differs)964 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.figma.com/mcp)On your machine (canvaskeep-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 2
Parts of the bundle (differs)22Not a bundle
Licence (differs)LicenseRef-Figma-Developer-TermsNot stated
Repository (differs)github.com/openai/pluginsgithub.com/canvaskeep/canvaskeep-mcp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-18
Endpoint at the last check (differs)Responded 3 days agono remote endpoint we check

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

Figma

In its own words, on Codex: openai-curated (openai/plugins):

Figma workflows for design implementation, Code Connect templates, and design system rule generation.

CanvasKeep

In its own words, on Official MCP Registry:

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

How to run each

Figma As a Codex plugin

Codex
codex plugin marketplace add openai/plugins

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)

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

Only Figma 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 Figma publish no settings it asks for, so we do not compare settings.

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

Data comes from the public marketplace file https://github.com/openai/plugins/blob/HEAD/.agents/plugins/marketplace.json. 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