Ext Ops Panel
Open dashboard
Comparison

flexcompute vs FEA (finite element analysis)

flexcompute is a plugin bundle for AI coding tools published by flexcompute. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). FEA (finite element analysis) is an MCP server published by TheRoboMaster123. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
MarketplaceflexcomputeFEA (finite element analysis)
Claude Code: claude-plugins-community Listed
Version: 7e5f0a5
Forks (GitHub): 1
Stars (GitHub): 9
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
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

flexcompute vs FEA (finite element analysis)
FactflexcomputeFEA (finite element analysis)
Marketplaces that list it11
Stars (GitHub) (differs)9 (better)1 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (therobomaster123--mcp-fea-mcp-endpoint.modal.run/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/flexcompute/plugin-marketplacegithub.com/therobomaster123/mcp-fea
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 20 h ago

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

flexcompute

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

Flexcompute plugins bring Tidy3D and PhotonForge into your AI coding assistant. Adds the tidy3d-mcp server (live Flexcompute documentation search/fetch) plus skills that guide agents through Tidy3D simulation authoring (geometry, physics guardrails, cost checks, result analysis) and PhotonForge layout work (PCells, ports, routing, LVS-style and overlap checks). Works with Claude Code, Codex, and GitHub Copilot CLI.

FEA (finite element analysis)

In its own words, on Official MCP Registry:

Real FEA on CAD parts: validated setups, stress, safety factor, natural frequencies

How to run each

flexcompute As a Claude Code plugin

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

FEA (finite element analysis) As a remote MCP server

Claude Code
claude mcp add --transport http mcp-fea https://therobomaster123--mcp-fea-mcp-endpoint.modal.run/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 FEA (finite element analysis) 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: flexcompute · What it can do: FEA (finite element analysis) · 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. 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