Ext Ops Panel
Open dashboard
Comparison

bridge-ds vs Figma MCP

bridge-ds is a plugin bundle for AI coding tools published by noemuch. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Figma MCP is an MCP server published by scalably.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
Marketplacebridge-dsFigma MCP
Claude Code: claude-plugins-community Listed
Version: 6.0.0
Forks (GitHub): 16
Stars (GitHub): 155
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Downloads/month (npm): 262
Downloads/week (npm): 33
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

bridge-ds vs Figma MCP
Factbridge-dsFigma MCP
Marketplaces that list it11
Stars (GitHub) (differs)155 (better)0 (worse)
Forks (GitHub) (differs)16 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (figma-console-mcp)On your machine (@scalably-io/figma-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 17, secrets among them: 1
Hooks it runs (differs)1Not published
Parts of the bundle (differs)7Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/noemuch/bridgegithub.com/scalably-io/figma-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

bridge-ds

In its own words, on Claude Code: claude-plugins-community:

AI-powered design generation in Figma using your real design system. Bridge extracts your DS (components, tokens, styles), writes validated specs, and generates production-ready Figma designs with 100% DS compliance — zero hardcoded values, real component instances, bound variables. Features a unique learning loop that captures your corrections and improves future generations. Supports both figma-console-mcp and the official Figma MCP server.

Figma MCP

In its own words, on Official MCP Registry:

Figma MCP: list frames in a file and fetch one frame's JSON and image safely. 2 tools.

How to run each

bridge-ds As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install bridge-ds@claude-community

Figma MCP As a local MCP server: npm package

Claude Code
claude mcp add --env "FIGMA_TOKEN=<YOUR_FIGMA_TOKEN>" --transport stdio figma-mcp -- npx -y @scalably-io/figma-mcp

Requires: FIGMA_TOKEN (secret)

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

Tools each declares

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

Settings each asks for

Only bridge-ds asks for

  • FIGMA_ACCESS_TOKEN (secret)

Only Figma MCP asks for

  • FIGMA_ALLOW_HTTP_FOR_TESTS
  • FIGMA_API_BASE_URL
  • FIGMA_MAX_FRAME_BYTES
  • FIGMA_MAX_JSON_BYTES
  • FIGMA_OUTPUT_ROOT
  • FIGMA_REQUEST_TIMEOUT_MS
  • FIGMA_TOKEN (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: bridge-ds · What it can do: Figma MCP · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/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