Ext Ops Panel
Open dashboard
Comparison

framework-mcp vs Subagent MCP

framework-mcp is an MCP server published by 81labsapps-ops. Marketplaces we read that list it: 1 (Official MCP Registry). Subagent MCP is an MCP server published by Thang1710. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). 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
Marketplaceframework-mcpSubagent MCP
Official MCP Registry Listed
Version: 0.3.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.31
Downloads/month (PyPI): 1 246
Downloads/week (PyPI): 242
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 1.0.31
Downloads/month (PyPI): 1 246
Downloads/week (PyPI): 242
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

framework-mcp vs Subagent MCP
Factframework-mcpSubagent MCP
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (framework-mcp-production.up.railway.app/mcp)On your machine (subagent-harness-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedMIT
Repository (differs)github.com/81labsapps-ops/framework-mcpgithub.com/thang1710/subagent-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Answered with HTTP 404 (6 days 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

framework-mcp

In its own words, on Official MCP Registry:

Verified, version-pinned answers about fast-moving frameworks for coding agents.

Subagent MCP

In its own words, on Official MCP Registry:

Let Codex orchestrate external coding agents through their native harnesses.

How to run each

framework-mcp As a remote MCP server

Claude Code
claude mcp add --transport http framework-mcp https://framework-mcp-production.up.railway.app/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

Subagent MCP As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio subagent-mcp -- uvx subagent-harness-mcp serve

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

Only framework-mcp 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: framework-mcp · What it can do: Subagent MCP · Compare two other plugins

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