MetaForge (local) vs io.github.TranHoaiHung/figma-ui-mcp
MetaForge (local) is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.
MetaForge (local) is a plugin bundle for AI coding tools published by MetaForge. No marketplace we read lists it any more. io.github.TranHoaiHung/figma-ui-mcp is an MCP server published by TranHoaiHung. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-25. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.TranHoaiHung/figma-ui-mcp | |
|---|---|---|
| Community marketplace fidelodok/metaforge | Removed on 2026-10-23 Version: 0.2.5 Forks (GitHub): 0 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.5.29 Downloads/month (npm): 1 649 Downloads/week (npm): 329 Forks (GitHub): 50 Stars (GitHub): 264 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 2.5.29 Downloads/month (npm): 1 649 Downloads/week (npm): 329 Forks (GitHub): 50 Stars (GitHub): 264 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 | MetaForge (local)no longer listed · | io.github.TranHoaiHung/figma-ui-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 8 | 264 |
| Forks (GitHub) (differs) | 0 | 50 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (figma-ui-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | Not published |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 59 | Not a bundle |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/fidelodok/metaforge | github.com/tranhoaihung/figma-ui-mcp |
| Changes in the last 7 days (differs) | 5 | 0 |
| First seen (differs) | 2026-10-18 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of MetaForge (local)
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Bitbybit 3D parametric CAD API, version-exact, for coding agents: search, describe, examples, guide
-
AI plugin for working with CADBuildr, a CAD-as-code platform. Skills for project setup, API reference, broker/viewer iteration, and render/export workflows.
-
Build and verify CAD parts and assemblies with the ClassCAD engine, locally, no server needed.
-
Parametric 3D CAD for AI agents: build print-ready parts, check them, export STL, 3MF or STEP.
-
Build, verify and export 3D CAD parts and assemblies with the ClassCAD engine, running locally.
-
Define hardware project BOMs with ESP32-first focus — onboarding captures location/vendors/on-hand gear, then skills for spec creation, live web research of parts…
What each says it does
MetaForge (local)
Runs MetaForge as a local process over stdio. No gateway, no account, no network. Needs the `metaforge-mcp` command on your PATH; the package README gives the one line that installs it.
io.github.TranHoaiHung/figma-ui-mcp
Bidirectional Figma MCP — AI draws UI on Figma canvas, reads designs back
How to run each
MetaForge (local)
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.TranHoaiHung/figma-ui-mcp As a local MCP server: npm package
claude mcp add --transport stdio figma-ui-mcp -- npx -y figma-ui-mcpCommands 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 io.github.TranHoaiHung/figma-ui-mcp publish no settings it asks for, so we do not compare settings.
What it can do: MetaForge (local) · What it can do: io.github.TranHoaiHung/figma-ui-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. 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.