Ext Ops Panel
Open dashboard
Comparison

f-mcp-bridge vs Supericons

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). Supericons is an MCP server published by curlymolelabs. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-16. 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-bridgeSupericons
Claude Code: claude-plugins-community Listed
Version: 1.7.28
Forks (GitHub): 1
Stars (GitHub): 10
Not marked · First seen
Listed
Version: 2.0.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 0.4.22
Downloads/month (npm): 2 313
Downloads/week (npm): 951
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 Supericons
Factf-mcp-bridgeSupericons
Marketplaces that list it (differs)1 (worse)2 (better)
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)Remote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)2Not published
Parts of the bundle (differs)412
LicenceMITMIT
Repository (differs)github.com/atezer/fmcpgithub.com/curlymolelabs/supericons
Changes in the last 7 days (differs)04
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 9 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

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.

Supericons

In its own words, on Official MCP Registry:

Multilingual semantic SVG icon search with previews for AI coding agents. 20,000+ icons.

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

Supericons As a remote MCP server

Claude Code
claude mcp add --transport http supericons https://mcp.supericons.dev/mcp

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

Only Supericons 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

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

What it can do: f-mcp-bridge · What it can do: Supericons · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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