Full Agent Swarm API and MCP server with local SQLite storage for multi-agent orchestration.
io.github.desplega-ai/agent-swarm MCP Server
The io.github.desplega-ai/agent-swarm MCP server provides a “Full Agent Swarm API” for multi-agent orchestration, backed by local SQLite storage. Its scope centers on agent teams, orchestration, and memory-oriented components, integrating with LLM-based workflows and execution/harness layers for agent coordination.
🛠️ Key Features
Full Agent Swarm API and MCP server
Local SQLite storage for orchestration
Multi-agent and agent-team orchestration
Agent memory / AI memory components
Harness execution layer integration
🚀 Use Cases
Orchestrating agent swarms and agent teams
Building human-in-the-loop agent workflows
Running self-hosted multi-agent systems
Coordinating LLM-driven agents with persistent local state
⚡ Developer Benefits
Agent Swarm API available via MCP
Local SQLite persistence for agent orchestration state
Tooling aligned to harness-engineering and execution layers
Support for agent memory patterns (ai-memory/agent-memory)
⚠️ Limitations
No tool count or specific MCP tools are provided in the available source data.
agent-swarm.dev is an open-source operating system for AI work. A lead agent delegates goals to workers such as Claude Code or Codex. Isolated containers, shared memory, tools, schedules, and review gates preserve work across sessions.
What you get
A lead agent that receives work from Slack, repositories, issue trackers, email, or the API
Workers in isolated Docker containers with development environments
Memory and identity that persist across sessions, with citation ratings and self-rating hints enabled by default
Workflows, schedules, scripts, and apps for recurring work
Extensions for trusted TypeScript hooks, installed as agent-owned inert drafts and activated by a trusted lead, operator, or dashboard user
Realtime rooms for shared page state, presence, and live channels
Your choice of harness and models: Claude Code, Codex, pi, opencode, Cursor, Amp, Grok, Devin, or ACP agents
flowchart LR
subgraph IN["Tasks come in"]
direction TB
S["Slack"]
G["GitHub / GitLab"]
E["Email"]
A["API / CLI"]
end
LEAD(["Lead Agent<br/>plans & delegates"])
subgraph WORKERS["Workers in Docker"]
direction TB
W1["Worker"]
W2["Worker"]
W3["Worker"]
end
subgraph BRAIN["Persistent brain"]
direction TB
MEM["Memory<br/>(vector search)"]
ID["Identity<br/>(SOUL, CLAUDE.md)"]
end
subgraph OUT["Work ships"]
direction TB
PR["Pull Requests"]
REPLY["Slack replies"]
EMAIL["Email replies"]
end
IN --> LEAD --> WORKERS
WORKERS -->|reads context| BRAIN
WORKERS -->|writes learnings| BRAIN
WORKERS --> OUT
Quick Start
Give your coding agent the operator skill for Docker Compose or Kubernetes:
bash
npx skills add desplega-ai/agent-swarm
Or install it as a plugin in your harness:
Harness
Command
Claude Code
/plugin marketplace add desplega-ai/agent-swarm then /plugin install agent-swarm@agent-swarm
droid plugin marketplace add https://github.com/desplega-ai/agent-swarm then droid plugin install agent-swarm@agent-swarm
OpenCode, pi, Devin, Kimi, others
npx skills add desplega-ai/agent-swarm
The plugin's privacy and
terms links describe the Agent Swarm website and
Cloud service. The self-hosted software remains covered by the MIT License.
Or self-host. docker-compose.example.yml is the reference deployment: deploy every agent in it by default (1 lead and 11 workers on the official templates), and remove agents only when you have a reason to.
The one-shot installer checks Docker and Compose v2, installs Bun when missing, runs agent-swarm onboard --yes, and prints the dashboard /setup link. It defaults to the single-agent solo preset, so pass --preset full for every official template (it runs one coder where the example runs two):
bash
curl -fsSL https://raw.githubusercontent.com/desplega-ai/agent-swarm/main/install.sh | bash -s -- --preset full
Or use the examples directly:
bash
git clone https://github.com/desplega-ai/agent-swarm.git && cd agent-swarm
cp .env.docker.example .env# Set API_KEY and the credential for your HARNESS_PROVIDER.
openssl rand -base64 32 > encryption_key
chmod 600 .env encryption_key
docker compose -f docker-compose.example.yml --env-file .env up -d
Agent ID variables are optional. Each container generates a UUID on first boot and keeps it in its personal volume, so identity survives restarts. Pin *_AGENT_ID in .env only to keep an existing identity or to survive removing volumes.
Read the Compose checklist before starting. API: http://localhost:3013, with /docs and /openapi.json.
Next, open the dashboard and connect it to your API with API_KEY. A new install lands on /setup, a guided first run that covers providers, agents, memory, integrations, and a first task.
Kubernetes: install the OCI Helm chart.
AgentMail archives verified inbound deliveries before acknowledging them and retains the archive for 30 days, including mail excluded from task routing. See the contact inbox triage runbook for retention, coverage limits, and rollout instructions.
Public ranking: opt in with Get ranked (Settings → Configuration → Branding) to rank your install by tokens used on agent-swarm.dev/ranking. It shows at the next hourly refresh. Token totals are public and exact; telemetry, the organization name and website must be set.
Fresh deployments enable Slack thread renderer v2, queued Slack steering to the lead,
task steering, multi-runtime workers, RBAC, and task-tool preloading. Hybrid memory
search and graph expansion are also enabled. Explicit environment/config overrides
remain supported; see the environment reference.
When upgrading older workers, keep MULTI_RUNTIME_ENABLED=false until they support
runtime identities. Slack delegation rendering remains opt-in, and database retention
continues to default to dry-run.
