MCP.Market

mcp-crewd-rs MCP server

by DioNanos·io.github.DioNanos/mcp-crewd-rs·v0.1.4

Cell fabric daemon: spawn and coordinate Claude/Codex/pi worker cells over MCP. Audited.

C63/100grade C
What users say
No reviews yet
Be the first
Safety scan
C63/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed mcp-crewd-rs yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

mcp-crewd-rs tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualityno auth information5/15
  • Maintenancelast push 82 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 63/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How mcp-crewd-rs compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
63/100
higher than 18% of 48,255 servers

Install mcp-crewd-rs in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the mcp-crewd-rs repository's README, as published. We do not edit it. Read it on GitHub

mcp-crewd-rs

crewd is a cell fabric daemon for AI agents: it lets one AI session (Claude Code, Codex CLI, or any MCP client) spawn, coordinate and message other AI worker sessions — cells — through a single MCP server. Rust, one static binary per component, no network listener: everything runs over a local Unix socket.

Part of the mcp-*-rs family of Rust MCP servers.

┌────────────┐  MCP stdio   ┌──────┐   UDS (NDJSON)   ┌───────┐  spawns   ┌─────────────────┐
│ Claude Code│─────────────▶│ crew │─────────────────▶│ crewd │──────────▶│ engine processes│
│ / Codex CLI│  cell_* tools│ shim │  0600 socket     │daemon │           │ claude / codex  │
└────────────┘              └──────┘                  └───────┘           │ / pi workers    │
                                                                          └─────────────────┘

Components

MCP tools

Mounted per-cell via crew mcp:

cellsendtask, cellstatus, cellresult, cellcancel, celllist

  • Fabric — cell_spawn (launch a worker cell: engine + profile + task),

(ask ticket + long-poll reply), cellreply, cellbroadcast, cell_inbox

  • Bus — cellsend (fire-and-forget), cellask / cell_await

Worker cells get the same shim with --worker-mode, which hides the spawn surface (no uncontrolled nested fan-out).

Engines

Claude profiles select where the engine gets its credentials. max (the default) uses the host's own Claude credentials and needs no extra config. Additional profiles route the engine to an Anthropic-compatible endpoint, reading that profile's bearer token from keysenvpath (never from crewd.toml, argv or logs); the built-in ones are defined in the engine-claude adapter.

A cell's identity is its working directory: the spawned engine loads whatever CLAUDE.md, .mcp.json, memory and skills live in the cwd you pass to cell_spawn. One daemon can therefore serve several "personas" by spawning cells in different project roots.

Install

Prebuilt binaries (recommended) — download the archive for your platform from the latest release and extract; it contains crewd, crew and the shim/ directory:

tar xzf mcp-crewd-rs-x86_64-unknown-linux-gnu.tar.gz
install -m755 mcp-crewd-rs-*/crewd mcp-crewd-rs-*/crew ~/.local/bin/

Prebuilt targets (Linux + Android): x8664-unknown-linux-gnu, x8664-unknown-linux-musl, aarch64-unknown-linux-gnu, aarch64-unknown-linux-musl (edge / ARM), aarch64-linux-android (Termux).

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

mcp-crewd-rs: common questions

Is mcp-crewd-rs MCP server safe?
With care: it is graded C, so read the findings first (63/100). Read the mcp-crewd-rs safety report
Does mcp-crewd-rs need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is mcp-crewd-rs maintained?
The last commit was 121 days ago (2026-07-06). The latest release is v0.1.4.

More from DioNanos →