Ext Ops Panel
Open dashboard
Comparison

figma vs PFC - ITASCA Discrete Element Simulation

figma is a plugin bundle for AI coding tools published by figma. Marketplaces we read that list it: 5 (Claude Code: claude-plugins-official, Official MCP Registry, Claude: knowledge-work-plugins, Copilot CLI: github/awesome-copilot, Community GitHub marketplaces). PFC - ITASCA Discrete Element Simulation is an MCP server published by yusong652. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
MarketplacefigmaPFC - ITASCA Discrete Element Simulation
Claude Code: claude-plugins-official Listed
Version: 2.2.157
Forks (GitHub): 203
Stars (GitHub): 2 072
Not marked · First seen
Not listed
Official MCP Registry Listed
Version: 1.0.3
Forks (GitHub): 203
Stars (GitHub): 2 072
Not marked · First seen
Listed, marked deprecated
Version: 0.2.5
Downloads/month (PyPI): 192
Downloads/week (PyPI): 19
Forks (GitHub): 19
Stars (GitHub): 217
Not marked · First seen
Claude: knowledge-work-plugins Listed
Version: 2.2.157
Forks (GitHub): 203
Stars (GitHub): 2 072
Not marked · First seen
Not listed
Copilot CLI: github/awesome-copilot Listed
Version: 2.2.124
Forks (GitHub): 203
Stars (GitHub): 2 072
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

figma vs PFC - ITASCA Discrete Element Simulation
FactfigmaPFC - ITASCA Discrete Element Simulation
Marketplaces that list it (differs)5 (better)1 (worse)
Stars (GitHub) (differs)2 072 (better)217 (worse)
Forks (GitHub) (differs)203 (better)19 (worse)
Last release (differs)2026-10-15Not published
Where it runs (differs)Remote server (mcp.figma.com/mcp)On your machine (pfc-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)17Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/figma/mcp-server-guidegithub.com/yusong652/pfc-mcp
Changes in the last 7 days (differs)80
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 43 h agono 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

In its own words, on Claude Code: claude-plugins-official:

Figma design platform integration. Access design files, extract component information, read design tokens, and translate designs into code. Bridge the gap between design and development workflows.

PFC - ITASCA Discrete Element Simulation

In its own words, on Official MCP Registry:

Give AI agents full access to ITASCA PFC - documentation, simulation, and plot capture.

How to run each

figma As a Claude Code plugin

Claude Code
/plugin install figma@claude-plugins-official

PFC - ITASCA Discrete Element Simulation As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio pfc -- uvx pfc-mcp

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

Only figma 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: figma · What it can do: PFC - ITASCA Discrete Element Simulation · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. 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