Ext Ops Panel
Open dashboard
Comparison

io.github.ronmiz/infernoflow vs io.github.shinpr/sub-agents-mcp

io.github.ronmiz/infernoflow is an MCP server published by ronmiz. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.shinpr/sub-agents-mcp is an MCP server published by shinpr. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-24. 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
Marketplaceio.github.ronmiz/infernoflowio.github.shinpr/sub-agents-mcp
Official MCP Registry Listed
Version: 0.46.5
Forks (GitHub): 0
Stars (GitHub): 8
Not marked · First seen
Listed
Version: 0.15.1
Downloads/month (npm): 1 059
Downloads/week (npm): 294
Forks (GitHub): 17
Stars (GitHub): 99
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.15.1
Downloads/month (npm): 1 059
Downloads/week (npm): 294
Forks (GitHub): 17
Stars (GitHub): 99
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

io.github.ronmiz/infernoflow vs io.github.shinpr/sub-agents-mcp
Factio.github.ronmiz/infernoflowio.github.shinpr/sub-agents-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)8 (worse)99 (better)
Forks (GitHub) (differs)0 (worse)17 (better)
Last release (differs)2026-10-23 (better)2026-10-22 (worse)
Where it runs (differs)On your machine (infernoflow)On your machine (sub-agents-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 012, secrets among them: 2
Licence (differs)Not statedMIT
Repository (differs)github.com/ronmiz/infernoflowgithub.com/shinpr/sub-agents-mcp
Changes in the last 7 days (differs)35
First seen (differs)2026-10-232026-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

io.github.ronmiz/infernoflow

In its own words, on Official MCP Registry:

Git-native memory for coding agents: gotchas, decisions and bookmarks as plain text in your repo.

io.github.shinpr/sub-agents-mcp

In its own words, on Official MCP Registry:

MCP server for delegating tasks to specialized AI sub-agents across coding tools

How to run each

io.github.ronmiz/infernoflow As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio infernoflow -- npx -y infernoflow mcp

io.github.shinpr/sub-agents-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "AGENTS_DIR=<YOUR_AGENTS_DIR>" --env "AGENT_TYPE=<YOUR_AGENT_TYPE>" --env "CLI_API_KEY=<YOUR_CLI_API_KEY>" --env "CURSOR_API_KEY=<YOUR_CURSOR_API_KEY>" --transport stdio sub-agents-mcp -- npx -y sub-agents-mcp

Requires: AGENTS_DIR, AGENT_TYPE, CLI_API_KEY (secret), CURSOR_API_KEY (secret)

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 io.github.ronmiz/infernoflow asks for

  • INFERNOFLOW_PROJECT_DIR

Only io.github.shinpr/sub-agents-mcp asks for

  • AGENTS_DIR
  • AGENTS_SETTINGS_PATH
  • AGENT_EFFORT
  • AGENT_MODEL
  • AGENT_PERMISSION
  • AGENT_TYPE
  • CLI_API_KEY (secret)
  • CURSOR_API_KEY (secret)
  • EXECUTION_TIMEOUT_MS
  • SESSION_DIR
  • SESSION_ENABLED
  • SESSION_RETENTION_DAYS

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

What it can do: io.github.ronmiz/infernoflow · What it can do: io.github.shinpr/sub-agents-mcp · Compare two other plugins

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