Sequa.AI vs io.github.shinpr/sub-agents-mcp
Sequa.AI is an MCP server published by sequa-ai. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.shinpr/sub-agents-mcp is an MCP server published by shinpr. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
| Marketplace |  Sequa.AI |  io.github.shinpr/sub-agents-mcp |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:f4e0e271c5c5 Forks (GitHub): 5 Pulls (Docker Hub): 10 301 Stars (Docker Hub): 1 Stars (GitHub): 22 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.14.3 Downloads/month (npm): 968 Downloads/week (npm): 274 Forks (GitHub): 16 Stars (GitHub): 98 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
| Fact | Sequa.AI | io.github.shinpr/sub-agents-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 22 (worse) | 98 (better) |
| Pulls (Docker Hub) (differs) | 10 301 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 5 (worse) | 16 (better) |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | On your machine (mcp/sequa) | On your machine (sub-agents-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 12, secrets among them: 2 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/sequa-ai/sequa-mcp | github.com/shinpr/sub-agents-mcp |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-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
Sequa.AI
Stop stitching context for Copilot and Cursor. With Sequa MCP, your AI tools know your entire codebase and docs out of the box.
io.github.shinpr/sub-agents-mcp
MCP server for delegating tasks to specialized AI sub-agents across coding tools
How to run each
Sequa.AI As a local MCP server: Docker image
claude mcp add --env "API_KEY=<YOUR_API_KEY>" --transport stdio sequa -- docker run -i --rm -e API_KEY mcp/sequaRequires: API_KEY (secret)
io.github.shinpr/sub-agents-mcp As a local MCP server: npm package
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-mcpRequires: 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
The marketplaces of io.github.shinpr/sub-agents-mcp publish no list of tools, so we do not compare tools.
Settings each asks for
Only Sequa.AI asks for
API_KEY (secret)MCP_SERVER_URL
Only io.github.shinpr/sub-agents-mcp asks for
AGENTS_DIRAGENTS_SETTINGS_PATHAGENT_EFFORTAGENT_MODELAGENT_PERMISSIONAGENT_TYPECLI_API_KEY (secret)CURSOR_API_KEY (secret)EXECUTION_TIMEOUT_MSSESSION_DIRSESSION_ENABLEDSESSION_RETENTION_DAYS
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Sequa.AI · What it can do: io.github.shinpr/sub-agents-mcp · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.