figma-to-react vs Figma CodeKit MCP
figma-to-react is a plugin bundle for AI coding tools published by Gary Basin. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Figma CodeKit MCP is an MCP server published by Mehmoodqureshi. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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 |  figma-to-react |  Figma CodeKit MCP |
|---|---|---|
| Community marketplace gbasin/figma-to-react | Listed Version: 0.9.27 Forks (GitHub): 2 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.4 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
| Fact | figma-to-react | Figma CodeKit MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 8 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 2 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.figma.com/mcp) | On your machine (figma-codekit-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Hooks it runs (differs) | 9 | Not published |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/gbasin/figma-to-react | github.com/mehmoodqureshi/figma-codekit-mcp |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-19 | 2026-10-15 |
| Endpoint at the last check (differs) | Responded 3 days ago | no remote endpoint we check |
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-to-react
Convert Figma designs to pixel-perfect React components with Tailwind CSS
Figma CodeKit MCP
Figma to pixel-perfect code: deterministic HTML/React, then a render + pixel-diff verify loop.
How to run each
figma-to-react As a Claude Code plugin
/plugin marketplace add gbasin/figma-to-react
/plugin install figma-to-react@figma-to-reactFigma CodeKit MCP As a local MCP server: npm package
claude mcp add --env "FIGMA_TOKEN=<YOUR_FIGMA_TOKEN>" --transport stdio figma-codekit-mcp -- npx -y figma-codekit-mcpRequires: FIGMA_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only figma-to-react 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
The marketplaces of figma-to-react publish no settings it asks for, so we do not compare settings.
What it can do: figma-to-react · What it can do: Figma CodeKit MCP · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.