PlugWiki
ruv-swarm logo

ruv-swarm MCP Server: Setup for Claude Code, Cursor and Other Apps

CommunityLocal

Lets Claude run a local swarm of named agents with a task queue and small neural networks, tracked in a database on your machine.

ruv-swarm is a community server by ruvnet. It runs on your computer through npx, with no account or API key. Your assistant uses it to create swarms, add agents, queue tasks and read results back.

The tools manage swarm state and neural network experiments inside the package. Treat it as an orchestration and tracking layer. The agents it creates are records in a local database, so check the task results it returns before you rely on them.

Good for

  • Developers trying multi-agent workflows in Claude Code
  • People who want to track agents and tasks in one place
  • Tinkerers curious about WebAssembly neural networks

Works in

12 should work

Tap an app to see how to set it up and any known problems.

Install ruv-swarm MCP

Claude Code

  1. 1

    Copy this prompt.

    Add the ruv-swarm MCP server to Claude Code. Run this command:
    
    claude mcp add ruv-swarm -- npx -y ruv-swarm mcp start
    
    Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js 18+.

This adds the mcp start subcommand, which the package needs to run as an MCP server.

Built from the package data we hold. Not yet tested by us.

Tools

  • Starts a swarm of agents with a layout you choose

    Creates a new swarm on your machine. You pick the layout (mesh, hierarchical, ring or star), a cap of 1 to 100 agents and how work is shared. The swarm is saved to a local database.

    Try: “Start a mesh swarm with up to 8 agents.”

    Write · swarm_init

  • Adds an agent to the swarm

    Adds one agent of a type you choose (researcher, coder, analyst, optimizer or coordinator), with an optional name and list of skills. The agent is saved to the local database.

    Try: “Add a researcher agent called "Docs reader".”

    Write · agent_spawn

  • Hands a task to the swarm

    Records a task, assigns it to agents in the active swarm and returns a task id. You choose a parallel, sequential or adaptive plan and a priority, and the task is saved to the local database.

    Try: “Run "audit the auth module" across the swarm, in parallel.”

    Write · task_orchestrate

  • Shows the current swarm and its agents

    Reports the active swarm and its agents. Ask for the verbose form to see each agent.

    Try: “What is the status of my swarm?”

    Read · swarm_status

  • Lists agents, filtered by state

    Lists the agents in the swarm. You can show all of them or only active, idle or busy ones.

    Try: “Which agents are idle right now?”

    Read · agent_list

  • Shows performance numbers for agents

    Returns metrics for all agents or one agent id, including stored neural network details.

    Try: “Show metrics for the coder agent.”

    Read · agent_metrics

  • Checks how running tasks are going

    Reports progress for running tasks, or for one task id, with an optional detailed view.

    Try: “How far along is task task-123?”

    Read · task_status

  • Fetches what a finished task produced

    Returns the stored result of a completed task by id, as a summary, in detail or raw.

    Try: “Show me the full results for task task-123.”

    Read · task_results

  • Watches swarm activity for a few seconds

    Samples swarm activity at an interval you set for a set time, 10 seconds by default. It also logs a monitoring event to the local database.

    Try: “Monitor the swarm for 30 seconds.”

    Write · swarm_monitor

  • Times the swarm engine on your machine

    Runs speed tests on the WebAssembly engine, swarm creation, agents and tasks for up to 100 iterations. It uses your CPU while it runs.

    Try: “Run all benchmarks for 20 iterations.”

    Runs code · benchmark_run

  • Checks what your machine supports

    Reports which runtime features are available, such as WebAssembly, SIMD, memory and platform details.

    Try: “Does this machine support SIMD?”

    Read · features_detect

  • Shows how much memory the swarm uses

    Reports memory use for the WebAssembly engine and JavaScript, in summary, in detail or per agent. It also stores those readings in the local database.

    Try: “Show memory use by agent.”

    Write · memory_usage

Read from the source code

Permissions

medium risk · 4 things to watch

Medium risk

Its listed tools save swarm, agent and task records to a database on your computer and do not delete anything. It has no read-only mode, so only run it where those files can change.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It writes swarm state to a local database

    Creating swarms, agents and tasks, training networks and some monitoring calls save to a SQLite file (data/ruv-swarm.db) inside the package folder. Delete that file if you want a clean slate. github.com

  • Three more tools work than the server lists

    The server lists 25 tools: 15 core tools and 10 DAA (autonomous agent) tools. It also accepts calls to three others by name: pool_health, pool_stats and persistence_stats, which report on the database connection pool. Your assistant will not see them unless it already knows the names. github.com

  • Benchmarks and training use your CPU

    Benchmark and training calls run for up to 100 rounds on your machine. Ask for small numbers first. github.com

  • The README's environment variables are not read

    The README sets RUV_SWARM_LOG_LEVEL and RUV_SWARM_ENABLE_SIMD in one example and SWARM_CONFIG and MAX_AGENTS in another. The 1.0.20 server code does not read any of them. Its logger reads LOG_LEVEL, LOG_TO_FILE, LOG_FORMAT and LOG_DIR instead. github.com

Security advisories

No published security advisories as of Nov 1, 2026.

Technical details
Turning on read-onlyNo read-only mode is documented. Tools that create swarms, agents and tasks write to a local database.
Sign-in and keysNo account or API key. State is stored in a SQLite database inside the package folder.

Questions

Is ruv-swarm official?

No. It is a community project by ruvnet (Reuven Cohen), not a server from the maker of an app it connects to. It is listed in the official MCP Registry.

What does ruv-swarm actually do?

It keeps a local model of a swarm: swarms, agents, tasks and small neural networks, stored in a SQLite database on your machine. Your assistant creates and reads them through tools. The tools only manage this state; they do not call a hosted ruv-swarm service.

Does it need an API key?

No. The server needs Node.js and runs locally. No account, key or sign-in is used.

Which clients does it work with?

It runs over stdio, so any client that starts local servers can use it. The README gives a Claude Desktop config and a Claude Code command, and the install box has the others.

Is it free?

Yes. The package declares MIT OR Apache-2.0, though the published files include no license text. It has no paid tier.

Can it run read-only?

No. There is no read-only option. Most tools create or change swarm, agent or workflow state in the local database, and you cannot turn that off.

Does it have more tools than the list shows?

Yes, three. The server lists 25 tools, all shown on this page. It also answers calls to pool_health, pool_stats and persistence_stats by name, and your assistant will only use them if it knows the names.

Why do my environment variables have no effect?

The 1.0.20 code does not read the variables shown in the README (RUV_SWARM_LOG_LEVEL, RUV_SWARM_ENABLE_SIMD, SWARM_CONFIG, MAX_AGENTS). The logger reads LOG_LEVEL, LOG_TO_FILE, LOG_FORMAT and LOG_DIR, and the database sits in the package's own data folder.

Information

updated Nov 2, 2026

Publisher
Community
Package
ruv-swarm
Registry
npm
Transport
stdio
Version
1.0.20
License
MIT OR Apache-2.0
Last commit
Aug 9, 2026
Open issues
37
Listed in
Official MCP registry

GitHubnpmOfficial MCP Registry

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 6
  1. www.npmjs.com · npmjs.com
  2. github.com · github.com
  3. github.com · github.com
  4. github.com · github.com
  5. github.com · github.com
  6. github.com · github.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 2, 2026.