Mmcp.market

Swarm Rd Orchestrator MCP server

by RudrenduPaul·io.github.RudrenduPaul/swarm-rd-orchestrator·v0.0.3
No reviews yet

Append-only event log for cross-agent context/memory sharing via 3 MCP tools.

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
New

0 stars16 downloads/wk

Reviews

Write one

Nobody has reviewed Swarm Rd Orchestrator yet.

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

Swarm Rd Orchestrator tools (3)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • append_delta

    Append a delta (a finding/result/tool-output) to the event log for a task. Raises on missing task_id/agent_id/content.

  • list_tasks

    List every task_id currently in the event log, with its delta count.

  • pull_deltas

    Pull every delta for a task with id > since_cursor, oldest first. A cursor past the latest delta returns an empty list.

Public scan report

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

no findings
  • Code scan5 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 15 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

What the publisher says

From the Swarm Rd Orchestrator repository's README, as published. We do not edit it. Read it on GitHub

<!-- mcp-name: io.github.RudrenduPaul/swarm-rd-orchestrator -->

swarm-rd-orchestrator-cli

Install • Quickstart • Command reference • MCP Server • Comparison • FAQ

Ray-native context and memory sharing for parallel research agents, with an agent-native CLI and MCP server.

An append-only, SQLite-WAL-backed event log wrapped as a Ray actor, so parallel agents can write findings and pull each other's without a shared mutable store, plus a CLI and MCP server so both humans and other agents can drive it directly.

This is a Milestone 1 prototype (2026-08-03): validate the approach on a real task before building further. See Locked decisions below and spike.py for the actual validation harness.

Install

pip install swarm-rd-orchestrator-cli
# or
npm install -g swarm-rd-orchestrator-cli

Either gives you a swarm-rd-cli command on your PATH. The npm package is a thin wrapper around the Python CLI: it execs the real binary, it does not reimplement it. Install the Python package too if you use the npm one.

Status: live on both registries (PyPI published via GitHub Actions OIDC, no stored token). Both were verified with a real install and a real command run in a clean environment, not just a successful upload.

[!WARNING]

This is a pre-validation Milestone 1 spike (0.0.x), not yet a stable release. Tested on macOS only; Windows support is unverified since Ray's own Windows support is more limited than Linux/macOS upstream.

Quickstart

swarm-rd-cli append task-1 agent-a "found a race condition in the retry loop" --kind result
swarm-rd-cli append task-1 agent-b "confirmed: retry loop isn't holding the lock" --kind result
swarm-rd-cli pull task-1
# [1] (agent-a/result) found a race condition in the retry loop
# [2] (agent-b/result) confirmed: retry loop isn't holding the lock

swarm-rd-cli --json pull task-1     # structured output for scripts/agents
swarm-rd-cli list-tasks             # every task_id with a delta count
swarm-rd-cli mcp                    # run as an MCP server over stdio

Every data-returning command supports --json for agent and script consumption, no screen-scraping required. The mcp subcommand exposes appenddelta, pulldeltas, and list_tasks as typed MCP tools over stdio, so an agent can call this programmatically instead of shelling out.

Features

Shortened. The full README is on GitHub.

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

Install directly

claude mcp add swarm-rd-orchestrator -- uvx swarm-rd-orchestrator-cli
Add to Cursor

Swarm Rd Orchestrator: common questions

Is Swarm Rd Orchestrator MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Swarm Rd Orchestrator safety report
How do I install Swarm Rd Orchestrator?
It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does Swarm Rd Orchestrator need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Swarm Rd Orchestrator maintained?
The last commit was 16 days ago (2026-09-08). The latest release is v0.0.3.
What can I use instead of Swarm Rd Orchestrator?
Servers from other publishers that do the same job: three.ws Provenance MCP server, rag-rat MCP server and Basic Memory MCP server. Compare all Swarm Rd Orchestrator alternatives.

Alternatives to Swarm Rd Orchestrator

Same job from other publishers: the closest match first, then the best rated.

All Swarm Rd Orchestrator alternatives →
  • three.ws Provenance
    Append-only, signed, on-chain-verifiable agent action log — record and audit what agents did.
    B
  • rag-rat
    Repository intelligence, code graph, history, papertrail, and cross-agent memory for coding agents.
    B
  • Basic Memory
    Local-first knowledge management with bi-directional LLM sync via Markdown files.
    C
  • IWE
    Markdown knowledge base as agent memory. Runs against the notes directory it is started in.
    A
  • Agent-Native Plan
    Structured visual plans and PR recaps with diagrams, prototypes, annotations, and sharing
    A
Swarm Rd Orchestrator vs three.ws ProvenanceSwarm Rd Orchestrator vs rag-ratSwarm Rd Orchestrator vs Basic Memory

More from RudrenduPaul →