Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Build, run, inspect, and verify finite-element simulations with AgentFEM.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
AGENTFEM_MCP_ROOTS, AGENTFEM_COMMANDYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"agentfem": {
"command": "uvx",
"args": [
"agentfem-mcp"
],
"env": {
"AGENTFEM_MCP_ROOTS": "your-value",
"AGENTFEM_COMMAND": "your-value"
}
}
}
}Run this in your terminal
claude mcp add agentfem --env AGENTFEM_MCP_ROOTS=your-value --env AGENTFEM_COMMAND=your-value -- uvx agentfem-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"agentfem": {
"command": "uvx",
"args": [
"agentfem-mcp"
],
"env": {
"AGENTFEM_MCP_ROOTS": "your-value",
"AGENTFEM_COMMAND": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"agentfem": {
"type": "stdio",
"command": "uvx",
"args": [
"agentfem-mcp"
],
"env": {
"AGENTFEM_MCP_ROOTS": "your-value",
"AGENTFEM_COMMAND": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
AGENTFEM_MCP_ROOTS envAGENTFEM_COMMAND envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account haoming-luo, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Happo
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Review Happo's visual and accessibility diffs: inspect comparisons, accept or reject, report flakes.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
One finite-element platform. Any compatible agent. Evidence intact.
AgentFEM MCP gives Codex, Claude, and other MCP-compatible agents a small, stable tool surface for building and running inspectable finite-element projects. AgentFEM remains the deterministic scientific engine; the agent interprets intent and explains evidence.
Install from PyPI · Discover in the official MCP Registry · Read the AgentFEM agent guide
Already using an AI assistant in the terminal? You can use AgentFEM directly through its CLI. Choose between CLI, MCP, and skills →
For a supported desktop client on macOS or Linux, download the tiny AgentFEM-0.1.0.mcpb connection bundle from the 0.1.0 release. It installs only the interface; the AgentFEM scientific runtime remains the single source of solver capabilities, upgrades, and results.
It exposes seven tools—not hundreds of solver internals:
| Tool | Purpose |
|---|---|
describe_system | Inspect the installed runtime and a compact capability map |
create_project | Start from a version-matched AgentFEM template |
validate_project | Report process success and scientific acceptance separately |
inspect_project | Read project and recent-run identity |
submit_run | Launch an isolated serial or MPI process |
get_run_status | Observe a durable background job |
get_result_summary | Read a compact result and trust state; request full evidence only when needed |
Want to see the underlying workflow before installing?
AgentFEM must already be installed. With uvx, Codex needs one command and the adapter remains isolated from the numerical environment:
codex mcp add agentfem \
--env AGENTFEM_MCP_ROOTS=/absolute/path/to/AgentFEMProjects \ -- uvx --from agentfem-mcp agentfem-mcp
Or install the lightweight adapter in the active environment:
python -m pip install agentfem-mcp
The 0.1.0 lifecycle is acceptance-tested with the public AgentFEM 0.3.3 CLI contracts and the current 0.3.7 development line.
Give your agent a project root, not your whole home directory.
Codex officially supports local stdio MCP servers. Confirm the connection with codex mcp list, then begin with:
Use AgentFEM to create, validate, run, verify, and briefly explain a 2D
cantilever. Keep the project and result paths visible.
On macOS or Linux, open the release's .mcpb file in a supporting desktop client and choose the one project folder the connection may access. AgentFEM must already be installed. Windows support currently uses the explicit WSL2 configuration from the AgentFEM guide rather than claiming a native bridge.
Claude Code:
claude mcp add agentfem --scope user \
--env AGENTFEM_MCP_ROOTS=/absolute/path/to/AgentFEMProjects \ -- uvx --from agentfem-mcp agentfem-mcp
Claude Desktop configuration:
{
"mcpServers": { "agentfem": { "command": "agentfem-mcp", "env": { "AGENTFEM_MCP_ROOTS": "/absolute/path/to/AgentFEMProjects" } } } }
If a desktop app cannot see the activated conda environment, set AGENTFEM_COMMAND to the absolute agentfem executable. The official macOS runtime, AgentFEM WSL2 runtime, and common agentfem-env/fenicsx-env layouts are also detected automatically.
VS Code can place the same local server in .vscode/mcp.json:
{
"servers": { "agentfem": { "type": "stdio", "command": "uvx", "args": ["--from", "agentfem-mcp", "agentfem-mcp"], "env": { "AGENTFEM_MCP_ROOTS": "${workspaceFolder}" } } } }
The server is model-neutral. A DeepSeek or other model can use it through any host that implements local MCP tools. ChatGPT connectors require a public HTTPS server; AgentFEM will add that route only with a real authenticated compute and artifact boundary, rather than silently uploading local models through this adapter.
The repository's minimal, unprivileged Dockerfile exists for MCP directory startup and tool-introspection checks. It intentionally contains the public MCP adapter, not a second AgentFEM solver distribution. Real simulations should use the installed AgentFEM runtime and an explicit local project root.
This repository contains a portable AgentFEM workflow skill and a local Codex marketplace under .agents/plugins/. It combines scientific operating guidance with the same MCP server; it does not create a second solver interface.
AI agent
│ seven typed MCP tools ▼ AgentFEM MCP ── process + path boundary │ versioned JSON contracts ▼ AgentFEM CLI → Study → Model → Step → SimulationResult ▼ FEniCSx / PETSc / MPI
completed, verified, and validated remain different scientific states.| Variable | Meaning |
|---|---|
AGENTFEM_MCP_ROOTS | Approved project roots separated by the platform path separator |
AGENTFEM_COMMAND | Absolute path to a specific agentfem executable |
With no root configured, the server restricts access to its working directory. The default maximum is 16 MPI ranks and can only be changed by the server operator, not by an agent tool call.
python -m pip install -e '.[test]'
ruff check . pytest python -m build
See SECURITY.md for the trust boundary and CONTRIBUTING.md for contribution expectations. The first release evidence records protocol, package, and real-solver acceptance separately.
AgentFEM MCP is Apache-2.0 licensed and maintained as an official companion to AgentFEM.