Agent Swarm is listed as active in the registry but did not answer our last check. 3 214 installs a week from npm. Last commit 9 Nov 2026.
Full Agent Swarm API and MCP server with local SQLite storage for multi-agent orchestration.
What the code does
We read the source, 23 h ago · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
await Bun.$`rm -rf ${EXTENSIONS_TMP_PARENT}/${name}`.quiet();
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const proc = Bun.spawn(
return { entry, specJson: readFileSync(path.join(directory, entry.specFile), "utf-8") };
const fn = new Function(
raw = subprocess.run(["ffmpeg", "-v", "error", "-i", path, "-ac", "1", "-ar", str(SR), "-f", "f32le", "-"], capture_output=True, check=True).stdout
drop = ph + k * p
function applyTheme(){root.classList.toggle('dark',theme==='dark');tb.innerHTML=theme==='dark'?SUN:MOON;try{localStorage.swarmMock=theme}catch(e){}}
const entries = await readdir(skillsDir);
&& curl -fsSL https://deb.nodesource.com/setup_22.x | bash - \
USER root
env=dict(os.environ, AGENT_FS_HOME=T+"/home", AGENT_FS_STORAGE_PROVIDER="local", SERVER_PORT=str(port), SERVER_HOST="127.0.0.1",
const dockerHost = env.RUNTIME_DOCKER_HOST || env.DOCKER_HOST || "unix:///var/run/docker.sock";
["api.telegram.org", { provider: "telegram", type: "comms" }],
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found things in this code
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Agent Swarm and you get told the day something new turns up.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.
claude mcp add agent-swarm --transport http 'https://{swarm_host}/mcp'https://{swarm_host}/mcp[mcp_servers.agent-swarm]
url = "https://{swarm_host}/mcp"{
"mcpServers": {
"agent-swarm": {
"url": "https://{swarm_host}/mcp"
}
}
}{
"servers": {
"agent-swarm": {
"type": "http",
"url": "https://{swarm_host}/mcp"
}
}
}This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://{swarm_host}/mcp | streamable-http | answering | 0 ms | 1 min ago |
| https://{swarm_host}/mcp-user | streamable-http | answering | 0 ms | 1 min ago |
Alternatives to Agent Swarm
same job, measured the same wayMCP server for the Withings Health API with OAuth, local SQLite cache, and trend analysis.
MCP server for the Google Health API, with a local SQLite cache and trend analysis.
MCP server for local SQLite database operations
Local-first, auditable memory for MCP-compatible AI agents with explicit writes and SQLite storage.
SQLite MCP server with 73 tools for JSONB, full-text search, geospatial, and analytics.
MCP server for SQLCipher 4 encrypted SQLite databases with full CRUD operations and query support
Local FAISS vector database for RAG with document ingestion, semantic search, and MCP prompts.
Every Datto RMM API operation, plus a local SQLite fleet store and fleet-wide analytics no other
Agent Swarm — questions
Answers built from our own checks of this server.