Ext Ops Panel
Open dashboard
Comparison

figma-suite vs Figma MCP Server

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). Figma MCP Server is an MCP server published by planetabhi. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). 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
Marketplacefigma-suiteFigma MCP Server
Claude Code: claude-plugins-community Listed
Version: 1.4.0
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.1.1
Downloads/month (npm): 11 842
Downloads/week (npm): 1 627
Forks (GitHub): 4
Stars (GitHub): 10
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 3.1.2
Downloads/month (npm): 11 842
Downloads/week (npm): 1 627
Forks (GitHub): 4
Stars (GitHub): 10
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-suite vs Figma MCP Server
Factfigma-suiteFigma MCP Server
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)2 (worse)10 (better)
Forks (GitHub) (differs)0 (worse)4 (better)
Last release (differs)Not published2026-10-18
Where it runs (differs)Installs as a plugin bundleOn your machine (figma-mcp-server)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
Licence (differs)MPL-2.0MIT
Repository (differs)github.com/robukh/figma-suitegithub.com/planetabhi/figma-mcp-server
Changes in the last 7 days (differs)01
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

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.

Figma MCP Server

In its own words, on Official MCP Registry:

A local MCP server with full Figma REST API coverage.

How to run each

figma-suite As a Claude Code plugin

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

Figma MCP Server As a local MCP server: npm package

Claude Code
claude mcp add --env "FIGMA_API_KEY=<YOUR_FIGMA_API_KEY>" --transport stdio figma-mcp-server -- npx -y figma-mcp-server

Requires: 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 figma-suite publish no settings it asks for, so we do not compare settings.

What it can do: figma-suite · What it can do: Figma MCP Server · 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. Package data comes from the public npm registry (registry.npmjs.org). 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