Ext Ops Panel
Open dashboard
Comparison

f-mcp-bridge vs figma-suite

f-mcp-bridge is a plugin bundle for AI coding tools published by atezer. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). figma-suite is a plugin bundle for AI coding tools published by robukh. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-13. 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
Marketplacef-mcp-bridgefigma-suite
Claude Code: claude-plugins-community Listed
Version: 1.7.28
Forks (GitHub): 1
Stars (GitHub): 10
Not marked · First seen
Listed
Version: 1.4.0
Forks (GitHub): 0
Stars (GitHub): 1
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

f-mcp-bridge vs figma-suite
Factf-mcp-bridgefigma-suite
Marketplaces that list it11
Stars (GitHub) (differs)10 (better)1 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@atezer/figma-mcp-bridge)Installs as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)2Not published
Parts of the bundle (differs)411
Licence (differs)MITMPL-2.0
Repository (differs)github.com/atezer/fmcpgithub.com/robukh/figma-suite
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

f-mcp-bridge

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

Connect Claude Code to Figma with 46 MCP tools, 20 specialized skills, and 8 commands. Read, write, and analyze Figma designs directly — no REST API token required. Privacy-first, plugin-only architecture with Zero Trust design. Supports design system audits, token pipelines, screen generation, accessibility checks, and Figma-to-code workflows.

figma-suite

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

Design production-quality screens in Figma using your design system — every property variable-bound, every element a component instance. Build and edit Figma component libraries from code, sync design tokens bidirectionally (code ↔ Figma), and audit files for design system compliance. Requires the official Figma MCP server.

How to run each

f-mcp-bridge As a Claude Code plugin

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

figma-suite As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install figma-suite@claude-community

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

Neither one's marketplaces publish the settings it asks for.

What it can do: f-mcp-bridge · What it can do: figma-suite · Compare two other plugins

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