Ext Ops Panel
Open dashboard
Comparison

io.github.TranHoaiHung/figma-ui-mcp vs MintPage

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)). MintPage is an MCP server published by hlsitechio. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. 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
Marketplaceio.github.TranHoaiHung/figma-ui-mcpMintPage
Official MCP Registry Listed
Version: 2.5.30
Downloads/month (npm): 2 509
Downloads/week (npm): 1 141
Forks (GitHub): 52
Stars (GitHub): 265
Not marked · First seen
Listed
Version: 0.3.0
Forks (GitHub): 0 (last published figure)
Stars (GitHub): 0 (last published figure)
Not marked · First seen
npm registry (MCP servers) Listed
Version: 2.5.30
Downloads/month (npm): 2 509
Downloads/week (npm): 1 141
Forks (GitHub): 52
Stars (GitHub): 265
Not marked · First seen
Not listed

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

io.github.TranHoaiHung/figma-ui-mcp vs MintPage
Factio.github.TranHoaiHung/figma-ui-mcpMintPage
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)2650 (last published figure)
Forks (GitHub) (differs)520 (last published figure)
Last release (differs)2026-10-26 (better)2026-10-20 (worse)
Where it runs (differs)On your machine (figma-ui-mcp)Remote server (mintpage.ai/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/tranhoaihung/figma-ui-mcpgithub.com/hlsitechio/mintpage
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-19
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 34 h ago returned HTTP 200

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

io.github.TranHoaiHung/figma-ui-mcp

In its own words, on Official MCP Registry:

Bidirectional Figma MCP — AI draws UI on Figma canvas, reads designs back

MintPage

In its own words, on Official MCP Registry:

Publish Markdown or HTML as a live, shareable web page in one tool call. Guest mode needs no key.

How to run each

io.github.TranHoaiHung/figma-ui-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio figma-ui-mcp -- npx -y figma-ui-mcp

MintPage As a remote MCP server

Claude Code
claude mcp add --transport http mintpage https://mintpage.ai/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only MintPage 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: io.github.TranHoaiHung/figma-ui-mcp · What it can do: MintPage · Compare two other plugins

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