Agent Swarm
Agent Swarm is an MCP server published by Desplega Labs; its MCP spec-revision support has not been verified yet. It is the first-party server from Desplega Labs. Last verified 2026-09-03.
Does Agent Swarm support the current MCP specification (2026-07-28)?
Undetermined. We have not verified which MCP specification revision Agent Swarm supports (as of 2026-09-03).
Is Agent Swarm a first-party (official) MCP server?
Yes. Agent Swarm is the first-party MCP server published by Desplega Labs (last verified 2026-09-03).
How do I connect to Agent Swarm?
Agent Swarm is available via the package npm:@desplega.ai/agent-swarm, the official MCP Registry under io.github.desplega-ai/agent-swarm, the source repository at https://github.com/desplega-ai/agent-swarm. Authentication: api_key. Transports: streamable-http, stdio.
What tools does Agent Swarm expose?
Agent Swarm exposes several tools, including join-swarm, poll-task, send-task, steer-task, store-progress, memory-search (last verified 2026-09-03).
When were Agent Swarm's facts last verified?
2026-09-03. Each fact on this page links to the sources used to verify it.
Which tools does Agent Swarm expose?
Key tools verified:
join-swarmpoll-tasksend-tasksteer-taskstore-progressmemory-searchmemory-storedb-query
Desplega Labs' first-party MCP server for agent-swarm, its multi-agent orchestration system. A lead agent decomposes a goal into tasks and routes them to worker agents running in isolated Docker containers, with shared memory, scheduling, tracker state and review gates persisted in a local SQLite database. The MCP server is the interface those agents use: joining a swarm, polling and steering tasks, recording progress, and reading and writing memory.
It is self-hosted rather than a vendor service. The registry declares the
remote as https://{swarm_host}/mcp, where the operator supplies the host
of the instance they deployed, so there is no public endpoint to probe;
authentication is a bearer API key plus an X-Agent-ID header identifying
a registered agent. A hosted dashboard exists at app.agent-swarm.dev,
but the MCP endpoint itself runs wherever the operator puts it.
Authority is first-party: the company's own site lists agent-swarm among the things it built. The project ships very fast, with 160 tagged releases between 2026-02-27 and 2026-09-03, which is genuine cadence rather than version inflation. Spec-revision support is unverified: no surface states a revision, and the two protocol versions that appear in source are code defaults, one in an outbound client wrapper and one in a generated debug snippet, neither of which describes what this server serves.
How was this verified, and what are the sources?
Verified · method: vendor-announcement
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.desplega-ai/agent-swarm, fetched 2026-09-03 - version 1.137.0 published 2026-09-03, package npm @desplega.ai/agent-swarm with streamable-http transport, remote https://{swarm_host}/mcp, website https://docs.agent-swarm.dev - accessed
- Desplega Labs site, fetched 2026-09-03 - lists "agent-swarm" under "Things we built", establishing first_party authority for a server fronting the publisher's own product - accessed
- Repository README, fetched 2026-09-03 - "an open-source operating system for AI work: a lead agent breaks goals into tasks, routes them to specialized workers... runs each worker in an isolated container, and preserves shared memory, tools, schedules, and review gates"; documents the MCP API server alongside a SQLite database and Docker workers - accessed
- Repository metadata, fetched 2026-09-03 - MIT, 737 stars, 93 forks, created 2025-12-19, last push 2026-09-03, not archived, no published security advisories; 160 tagged releases since 2026-02-27 - accessed
- Documentation, fetched 2026-09-03 - confirms the self-hosted model ("users run their own instance via Docker or locally") and documents MCP server management and a reduced scripts-only MCP mode - accessed