← Back to directory

Agent Swarm

Official

A multi-agent orchestration operating system for companies.

GitHub source repository ↗

★ 723 Stars Category · Dev Tools Very popular Source revision 08547fc16e07

54FMRS · D

Reliability

8/20

Security and permissions

9/20

Maintenance

12/20

Documentation

14/20

Setup experience

11/20

The supplied material identifies Agent Swarm as an open-source, desplega-ai-maintained multi-agent orchestration system using streamable HTTP MCP transport. It supports local SQLite storage, Docker workers, shared memory, workflows, and multiple task integrations. The manifest does not list specific MCP tool names or client compatibility, so those fields remain empty.

Read the FMRS scoring method →

Agent Swarm is an open-source multi-agent orchestration API and MCP server with local SQLite storage. A lead agent breaks down tasks and delegates them to worker agents running in isolated Docker environments, with shared memory, persistent identity, workflows, scheduling, and human approval gates.

Tools

The tool list has not been reviewed yet.

Setup

Provide Docker and credentials for at least one supported agent harness. Run @desplega.ai/agent-swarm onboard with bunx or npx, or configure Docker Compose as described in the repository. After starting the MCP service, connect with the instance URL, a Bearer API key, and the X-Agent-ID of a registered agent.

Fit and risk

Best for

Teams seeking self-hosted multi-agent orchestration
Engineering and operations teams that want a lead agent to coordinate specialized workers
Organizations needing shared memory, persistent identity, workflows, or human approval gates
Users able to manage Docker, API keys, and agent-harness credentials

Not for

Users who only need a single MCP tool or simple chat assistant
Environments that cannot run Docker or manage agent-harness credentials
Teams that do not want tasks to flow among multiple agents, shared memory, or external integrations
Users requiring documented compatibility with a ready-made desktop client

Required permissions

Access to the local or remote Agent Swarm MCP endpoint
An Agent Swarm API key supplied through an Authorization header with the Bearer prefix
The X-Agent-ID of a registered agent
Depending on enabled integrations and harnesses, credentials for Slack, code hosting, email, Linear, Jira, or other services

Risks and side effects

Worker agents execute tasks in isolated Docker environments but may access the code, files, and services configured for them
Shared memory retains learnings across sessions and can broaden the context visible to later tasks
Enabled integrations can cause messages, emails, ticket updates, code changes, or pull requests
Misconfigured API keys, Bearer headers, or agent IDs can cause connection failures or access to the wrong agent instance
Automated workflows and external actions should be reviewed with human approval gates, especially for irreversible operations

Troubleshooting

Confirm that the Agent Swarm instance is running and check the port used in the MCP URL; the manifest defaults to 3000 while the quick-start example uses 3013
Confirm that AGENT_SWARM_API_KEY is set and that the Authorization header contains Bearer followed by the key
Confirm that X-Agent-ID belongs to a registered agent in the target instance
Confirm that Docker is installed and running and that credentials for the selected agent harness are configured
Use http://localhost:{port}/mcp for a local connection; for a remote connection, replace it with your own swarm host
Check that the instance, port, API key, and agent ID match between the client configuration and the running server

Use cases

Route tasks from Slack, GitHub, GitLab, email, Linear, Jira, or the API to an agent team

Execute software development tasks in isolated Docker containers and produce pull requests

Run workflows with human approval, retries, and deterministic fan-out and join behavior

Support ongoing customer support, content generation, reporting, and code-health work with shared memory and schedules

Supported clients

Supported clients have not been confirmed yet.

Related MCP servers

Compare with other MCP servers