Ext Ops Panel
Open dashboard
Comparison

agent-work-layer-mcp vs Subagent MCP

agent-work-layer-mcp is an MCP server published by probita-ai. Marketplaces we read that list it: 1 (npm registry (MCP servers)). 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-11-09. 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
Marketplaceagent-work-layer-mcpSubagent MCP
npm registry (MCP servers) Listed
Version: 0.9.1
Downloads/month (npm): 2 005
Downloads/week (npm): 995
Forks (GitHub): 2
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.31
Downloads/month (PyPI): 1 246
Downloads/week (PyPI): 54
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): 54
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

agent-work-layer-mcp vs Subagent MCP
Factagent-work-layer-mcpSubagent MCP
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last release (differs)2026-11-03Not published
Where it runs (differs)On your machine (agent-work-layer-mcp)On your machine (subagent-harness-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/probita-ai/agent-work-layergithub.com/thang1710/subagent-mcp
Changes in the last 7 days (differs)10
First seen (differs)2026-10-122026-10-11

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

agent-work-layer-mcp

In its own words, on npm registry (MCP servers):

MCP server for Agent Work Layer: hand Work Orders between agent sessions and get checked Work Reports back.

Subagent MCP

In its own words, on Official MCP Registry:

Let Codex orchestrate external coding agents through their native harnesses.

How to run each

agent-work-layer-mcp

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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.

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

Package data comes from the public npm registry (registry.npmjs.org). 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