f-mcp-bridge vs io.github.GLips/Figma-Context-MCP
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). io.github.GLips/Figma-Context-MCP is an MCP server published by GLips. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
| Marketplace | ||
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.7.28 Forks (GitHub): 1 Stars (GitHub): 10 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.13.2 Forks (GitHub): 1 263 Stars (GitHub): 15 970 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
| Fact | f-mcp-bridge | io.github.GLips/Figma-Context-MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 10 (worse) | 15 970 (better) |
| Forks (GitHub) (differs) | 1 (worse) | 1 263 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@atezer/figma-mcp-bridge) | On your machine (figma-developer-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 41 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/atezer/fmcp | github.com/glips/figma-context-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
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.
io.github.GLips/Figma-Context-MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
How to run each
f-mcp-bridge
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.GLips/Figma-Context-MCP As a local MCP server: npm package
claude mcp add --env "FIGMA_API_KEY=<YOUR_FIGMA_API_KEY>" --transport stdio figma-context-mcp -- npx -y figma-developer-mcpRequires: FIGMA_API_KEY (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
The marketplaces of f-mcp-bridge publish no settings it asks for, so we do not compare settings.
What it can do: f-mcp-bridge · What it can do: io.github.GLips/Figma-Context-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.