Ext Ops Panel
Open dashboard
Comparison

io.github.Mediaeater/swarm-at vs MCP Task Orchestrator

io.github.Mediaeater/swarm-at is an MCP server published by Mediaeater. Marketplaces we read that list it: 1 (Official MCP Registry). MCP Task Orchestrator is an MCP server published by jpicklyk. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-26. 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.Mediaeater/swarm-atMCP Task Orchestrator
Official MCP Registry Listed
Version: 0.7.1
Downloads/month (PyPI): 168
Downloads/week (PyPI): 21
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 3.16.0
Forks (GitHub): 25
Stars (GitHub): 210
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:eab0bb62611a
Forks (GitHub): 25
Stars (GitHub): 210
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.Mediaeater/swarm-at vs MCP Task Orchestrator
Factio.github.Mediaeater/swarm-atMCP Task Orchestrator
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)1 (worse)210 (better)
Forks (GitHub) (differs)0 (worse)25 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.swarm.at)On your machine (ghcr.io/jpicklyk/task-orchestrator:3.16.0)
Transport (differs)SSEstdio
Tools it declares (differs)Not published42
Environment variables it asks for (differs)2, secrets among them: 17, secrets among them: 0
Licence (differs)Not statedMIT
Repository (differs)github.com/mediaeater/swarm-at-ledgergithub.com/jpicklyk/task-orchestrator
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-12no 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

io.github.Mediaeater/swarm-at

In its own words, on Official MCP Registry:

Settlement protocol for AI agent swarms — hash-chained ledger, trust, 48 blueprints, 18 tools

MCP Task Orchestrator

In its own words, on Official MCP Registry:

Server-enforced workflow discipline for AI agents: work items, dependency graphs, quality gates

How to run each

io.github.Mediaeater/swarm-at As a remote MCP server

Claude Code
claude mcp add --transport sse swarm-at https://api.swarm.at

Requires: SWARM_API_KEY (secret)

MCP Task Orchestrator As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio task-orchestrator -- docker run -i --rm -v mcp-task-data:/app/data ghcr.io/jpicklyk/task-orchestrator:3.16.0

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

Only io.github.Mediaeater/swarm-at has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of io.github.Mediaeater/swarm-at publish no list of tools, so we do not compare tools.

Settings each asks for

Only io.github.Mediaeater/swarm-at asks for

  • SWARM_API_KEY (secret)
  • SWARM_API_URL

Only MCP Task Orchestrator asks for

  • AGENT_CONFIG_DIR
  • DATABASE_PATH
  • LOG_FILE
  • LOG_LEVEL
  • MCP_HTTP_PORT
  • MCP_TRANSPORT
  • USE_FLYWAY

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

What it can do: io.github.Mediaeater/swarm-at · What it can do: MCP Task Orchestrator · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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