Ext Ops Panel
Open dashboard
Comparison

Foundry MCP code mode vs GPTaria MCP

Foundry MCP code mode is an MCP server published by foundry-mcp.com. Marketplaces we read that list it: 1 (Official MCP Registry). GPTaria MCP is an MCP server published by gptaria-mcp. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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
MarketplaceFoundry MCP code modeGPTaria MCP
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 0.2.1
Downloads/month (npm): 106
Downloads/week (npm): 35
Forks (GitHub): 0
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

Foundry MCP code mode vs GPTaria MCP
FactFoundry MCP code modeGPTaria MCP
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (foundry-mcp.com/mcp/code)On your machine (gptaria-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/gptaria-mcp/gptaria-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Answered with HTTP 400 (7 h ago)no 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

Foundry MCP code mode

In its own words, on Official MCP Registry:

Code mode (preview): the AI writes a script against a typed foundry.* API and runs it in a sandbox.

GPTaria MCP

In its own words, on Official MCP Registry:

Post a project brief & publish cases on GPTaria from Claude Code, Cursor or Windsurf.

How to run each

Foundry MCP code mode As a remote MCP server

Claude Code
claude mcp add --transport http foundry-code https://foundry-mcp.com/mcp/code

GPTaria MCP As a local MCP server: npm package

Claude Code
claude mcp add --env "GPTARIA_API_KEY=<YOUR_GPTARIA_API_KEY>" --transport stdio gptaria-mcp -- npx -y gptaria-mcp

Requires: GPTARIA_API_KEY (secret)

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

Only Foundry MCP code mode 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

The marketplaces of Foundry MCP code mode publish no settings it asks for, so we do not compare settings.

What it can do: Foundry MCP code mode · What it can do: GPTaria MCP · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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