Ext Ops Panel
Open dashboard
Comparison

FERS — structural FEM vs AgentFEM

FERS — structural FEM is an MCP server published by ferscloud.com. Marketplaces we read that list it: 1 (Official MCP Registry). AgentFEM is an MCP server published by haoming-luo. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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
MarketplaceFERS — structural FEMAgentFEM
Official MCP Registry Listed
Version: 2.76.0
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Listed
Version: 0.1.0
Downloads/month (PyPI): 199
Downloads/week (PyPI): 38
Forks (GitHub): 1
Stars (GitHub): 0
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

FERS — structural FEM vs AgentFEM
FactFERS — structural FEMAgentFEM
Marketplaces that list it11
Stars (GitHub) (differs)3 (better)0 (worse)
Forks (GitHub) (differs)0 (worse)1 (better)
Last release (differs)2026-10-27Not published
Where it runs (differs)Remote server (ferscloud.com/api/mcp)On your machine (agentfem-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/jeroen124/fers_coregithub.com/haoming-luo/agentfem-mcp
Changes in the last 7 days (differs)30
First seen (differs)2026-10-212026-10-11
Endpoint at the last check (differs)not checked yetno 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

FERS — structural FEM

In its own words, on Official MCP Registry:

Structural FEM for AI agents: frames, plates, buckling, seismic and Eurocode checks, solved locally.

AgentFEM

In its own words, on Official MCP Registry:

Build, run, inspect, and verify finite-element simulations with AgentFEM.

How to run each

FERS — structural FEM As a remote MCP server

Claude Code
claude mcp add --transport http fers https://ferscloud.com/api/mcp

Requires: FERS_API_KEY (secret)

AgentFEM As a local MCP server: PyPI package

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

Commands 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

Only FERS — structural FEM asks for

  • FERS_API_KEY (secret)

Only AgentFEM asks for

  • AGENTFEM_COMMAND
  • AGENTFEM_MCP_ROOTS

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: FERS — structural FEM · What it can do: AgentFEM · Compare two other plugins

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