Skip to main content
hc
Submit
mcpSource-backed

Ruflo MCP Server

MCP server and CLI for Ruflo's multi-agent Claude Code and Codex workflow harness, exposing tools for swarms, agents, memory, hooks, daemons, plugins, federation, and project automation.

by RuvNet · submitted by oktofeesh1·added 2026-06-06·
Claude CodeCodexCursorClaude Desktop
HarnessClaude CodeCodexCursorClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/mcp/ruflo-mcp-server
Source URLs
https://raw.githubusercontent.com/ruvnet/ruflo/main/README.md, https://github.com/ruvnet/ruflo
Brand
Ruflo
Brand domain
github.com
Safety notes
Ruflo's full CLI install can add project files, MCP configuration, hooks, helper scripts, memory state, commands, skills, and background automation., The MCP surface includes tools for agent spawning, swarm coordination, memory operations, hook execution, daemon control, plugins, security scans, and federation., Background daemons and hooks can run automatically based on session, task, file, or worker events; inspect generated settings before relying on them., Some workflows can execute shell commands, edit project files, scan dependencies, start services, or dispatch multi-step agent tasks., Federation and HTTP transport modes can expose agent coordination outside the local stdio boundary; keep them disabled unless you have reviewed network trust., Use least-privilege repositories and require human review before accepting generated code, security fixes, plugin installs, or automated workflow changes.
Privacy notes
Ruflo memory, hooks, logs, telemetry-style metrics, worker output, prompts, code snippets, file paths, and task history may be stored under project-local state., Agent memory and embeddings can preserve sensitive implementation details beyond the current chat session., Federation, hosted UI, remote provider, plugin, or HTTP transport workflows may move task context beyond the local machine if enabled., Security scans, dependency checks, and code analysis can reveal private package names, vulnerabilities, paths, branch names, and repository structure., Review `.claude`, `.claude-flow`, helper scripts, logs, and exported memory before sharing a repository or support bundle.
Author
RuvNet
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as source-backed.

    Done

  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done

  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    No package verification flag provided.

    Pending

  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

20 minutes

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

5 to clear

Platforms

4 listed

Install type

CLI install

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done

  • Review privacy notesRequired

    Privacy notes are present.

    Done

  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

5 prerequisites to line up before setup. Includes a review or approval gate.

0/5 ready
Install & runtime2Configuration1Network & hosting1Review & approval120 minutes

Safety & privacy surface

Safety & privacy surface

6 safety and 5 privacy notes across 4 risk areas. Review closely: credentials & tokens, network access.

4 areas
  • SafetyLocal filesRuflo's full CLI install can add project files, MCP configuration, hooks, helper scripts, memory state, commands, skills, and background automation.
  • SafetyExecution & processesThe MCP surface includes tools for agent spawning, swarm coordination, memory operations, hook execution, daemon control, plugins, security scans, and federation.
  • SafetyCredentials & tokensBackground daemons and hooks can run automatically based on session, task, file, or worker events; inspect generated settings before relying on them.
  • SafetyLocal filesSome workflows can execute shell commands, edit project files, scan dependencies, start services, or dispatch multi-step agent tasks.
  • SafetyNetwork accessFederation and HTTP transport modes can expose agent coordination outside the local stdio boundary; keep them disabled unless you have reviewed network trust.
  • SafetyExecution & processesUse least-privilege repositories and require human review before accepting generated code, security fixes, plugin installs, or automated workflow changes.
  • PrivacyLocal filesRuflo memory, hooks, logs, telemetry-style metrics, worker output, prompts, code snippets, file paths, and task history may be stored under project-local state.
  • PrivacyCredentials & tokensAgent memory and embeddings can preserve sensitive implementation details beyond the current chat session.
  • PrivacyNetwork accessFederation, hosted UI, remote provider, plugin, or HTTP transport workflows may move task context beyond the local machine if enabled.
  • PrivacyLocal filesSecurity scans, dependency checks, and code analysis can reveal private package names, vulnerabilities, paths, branch names, and repository structure.
  • PrivacyExecution & processesReview `.claude`, `.claude-flow`, helper scripts, logs, and exported memory before sharing a repository or support bundle.

Disclosure: MIT-licensed open source MCP server and CLI from RuvNet. Ruflo also references hosted demos, plugins, sponsorship, and broader commercial ecosystem pages; this entry covers the source-available local MCP server path.

Safety notes

  • Ruflo's full CLI install can add project files, MCP configuration, hooks, helper scripts, memory state, commands, skills, and background automation.
  • The MCP surface includes tools for agent spawning, swarm coordination, memory operations, hook execution, daemon control, plugins, security scans, and federation.
  • Background daemons and hooks can run automatically based on session, task, file, or worker events; inspect generated settings before relying on them.
  • Some workflows can execute shell commands, edit project files, scan dependencies, start services, or dispatch multi-step agent tasks.
  • Federation and HTTP transport modes can expose agent coordination outside the local stdio boundary; keep them disabled unless you have reviewed network trust.
  • Use least-privilege repositories and require human review before accepting generated code, security fixes, plugin installs, or automated workflow changes.

Privacy notes

  • Ruflo memory, hooks, logs, telemetry-style metrics, worker output, prompts, code snippets, file paths, and task history may be stored under project-local state.
  • Agent memory and embeddings can preserve sensitive implementation details beyond the current chat session.
  • Federation, hosted UI, remote provider, plugin, or HTTP transport workflows may move task context beyond the local machine if enabled.
  • Security scans, dependency checks, and code analysis can reveal private package names, vulnerabilities, paths, branch names, and repository structure.
  • Review `.claude`, `.claude-flow`, helper scripts, logs, and exported memory before sharing a repository or support bundle.

Prerequisites

  • Node.js 20 or newer.
  • Claude Code or another MCP client that can launch stdio servers.
  • A repository where Ruflo-generated `.claude`, `.claude-flow`, settings, helpers, hooks, and memory files are acceptable.
  • Review of which MCP tool groups, hooks, plugins, providers, and background workers should be enabled.
  • A plan for any optional HTTP transport, federation, remote model providers, or hosted UI integrations before enabling them.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
20 minutes
Difficulty
advanced
Tool listing metadata
Disclosure
MIT-licensed open source MCP server and CLI from RuvNet. Ruflo also references hosted demos, plugins, sponsorship, and broader commercial ecosystem pages; this entry covers the source-available local MCP server path.
Full copyable content
{
  "mcpServers": {
    "ruflo": {
      "command": "npx",
      "args": ["-y", "ruflo@latest", "mcp", "start"]
    }
  }
}

About this resource

Content

Ruflo MCP Server connects Claude and other MCP clients to Ruflo, a multi-agent workflow harness for Claude Code and Codex-style development environments. Its MCP mode exposes coordinated agents, swarms, memory, hooks, daemon controls, plugins, security workflows, and federation-oriented tools.

Use it when Claude needs supervised access to a broad local agent-coordination system rather than a narrow single-purpose tool. Start with the minimal MCP server configuration, then enable hooks, daemons, plugins, and federation only after reviewing their generated files and runtime behavior.

Source Review

These sources were reviewed on 2026-06-06. Prefer the live repository, README, npm metadata, license, security policy, user guide, Ruflo package metadata, CLI entrypoint, MCP bridge, and MCP package metadata for current setup and behavior details.

Features

  • Start a Ruflo MCP server for Claude Code or other stdio-compatible MCP clients.
  • Coordinate agent swarms and spawn specialized agents for coding, review, testing, docs, architecture, and security workflows.
  • Store and search persistent memory through Ruflo and AgentDB-backed workflows.
  • Use hook-based task routing, session lifecycle events, progress checks, and worker dispatch.
  • Manage plugins that add tools, hooks, workers, providers, and domain-specific workflows.
  • Run background daemon commands for audits, optimization, mapping, and worker status.
  • Configure MCP tool groups to reduce the enabled surface for specific workflows.
  • Use optional federation and HTTP transport modes when remote coordination is intentionally required.

Installation

Run the interactive initializer when you want Ruflo to set up a project:

npx ruflo@latest init wizard

For Claude Code MCP registration, use the upstream command:

claude mcp add ruflo -- npx -y ruflo@latest mcp start

Other MCP clients can launch the same stdio server:

{
  "mcpServers": {
    "ruflo": {
      "command": "npx",
      "args": ["-y", "ruflo@latest", "mcp", "start"]
    }
  }
}

Keep the initial install minimal until you know which hooks, daemons, plugins, memory backends, model providers, and transports your project actually needs.

Use Cases

  • Coordinate several specialized agents around a large feature, refactor, or review plan.
  • Persist useful implementation patterns and retrieve them across later Claude sessions.
  • Route tasks through review, testing, documentation, architecture, or security agent roles.
  • Run progress checks and worker status commands from a Claude Code session.
  • Add a focused plugin only after reviewing the extra MCP tools, hooks, and background behavior it enables.
  • Experiment with local-only swarm coordination before considering federation or HTTP transport.

Safety and Privacy

Ruflo is closer to an agent operating layer than a small utility server. Treat its MCP tools, generated project files, hooks, daemons, plugin installs, and memory state as changes to your development environment, not just chat context.

Run it first in a disposable or low-risk repository, inspect generated files, and limit enabled tool groups. Do not enable federation, hosted UI, HTTP transport, remote providers, or autonomous background workers until your team has reviewed what task context, code, memory, logs, and credentials could be exposed.

#agents#swarm#memory#claude-code#workflow-automation

Source citations

Add this badge to your README

Show that Ruflo MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/ruflo-mcp-server.svg)](https://heyclau.de/entry/mcp/ruflo-mcp-server)

How it compares

Ruflo MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field
Ruflo MCP Server

MCP server and CLI for Ruflo's multi-agent Claude Code and Codex workflow harness, exposing tools for swarms, agents, memory, hooks, daemons, plugins, federation, and project automation.

Open dossier
CodeDB logoCodeDB MCP Server

Code intelligence MCP server with a Zig core for local project indexing, structural outlines, symbol lookup, search, dependency graphs, snapshots, remote public-repo queries, and fallback edits.

Open dossier
Memory Bank MCP Server

MCP server for remote project memory-bank management, with multi-project directories, file listing, read/write/update tools, and path isolation.

Open dossier
Agentset logoAgentset MCP Server

Official Agentset MCP server that lets Claude retrieve cited knowledge-base results from an Agentset namespace through the `knowledge-base-retrieve` tool, with optional tenant scoping and custom tool descriptions.

Open dossier
Next steps
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
Submitteroktofeesh1oktofeesh1oktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brand—CodeDB logoCodeDB—Agentset logoAgentset
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorRuvNetjustrachAliosh PimentaAgentset
Added2026-06-062026-06-062026-06-062026-06-06
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Harness
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓Ruflo's full CLI install can add project files, MCP configuration, hooks, helper scripts, memory state, commands, skills, and background automation. The MCP surface includes tools for agent spawning, swarm coordination, memory operations, hook execution, daemon control, plugins, security scans, and federation. Background daemons and hooks can run automatically based on session, task, file, or worker events; inspect generated settings before relying on them. Some workflows can execute shell commands, edit project files, scan dependencies, start services, or dispatch multi-step agent tasks. Federation and HTTP transport modes can expose agent coordination outside the local stdio boundary; keep them disabled unless you have reviewed network trust. Use least-privilege repositories and require human review before accepting generated code, security fixes, plugin installs, or automated workflow changes.✓CodeDB indexes local projects and exposes file tree, outline, search, symbol, caller, dependency, read, snapshot, project, and context tools to the MCP client. CodeDB's `codedb_edit` tool exists as a fallback editing tool and can create, replace, insert, delete, or modify files when used by a client without native edit tooling. The npm package runs a postinstall step that downloads a native binary from GitHub Releases; review package and release provenance in environments that restrict native binaries. Remote repo queries use the public `api.wiki.codes` service and should be treated as network access outside the local repository. The upstream README marks the project as alpha software, with parser coverage and snapshot formats still stabilizing.✓Memory Bank MCP can read, create, and update files inside the configured memory-bank root. Do not point `MEMORY_BANK_ROOT` at a home directory, source repository root, cloud-sync folder, or any directory containing secrets. Avoid auto-approving write and update tools until the expected file structure and naming rules are established. The path validator rejects path traversal and slash-containing file/project names, but users should still keep the root directory narrow and dedicated. Docker mode requires a bind mount for the memory bank; review the host path and container path before granting write access.✓The MCP server sends Claude's retrieval queries to the Agentset API using the configured API key and namespace. The `knowledge-base-retrieve` tool can return up to 100 results per call and can rerank results by relevance. Namespace and tenant selection control which indexed documents are searchable; review them before connecting a shared agent. API keys should be scoped, rotated, and stored only in the MCP server environment or a secret manager. Custom tool descriptions can influence when the model calls the retrieval tool, so review them before use in production workflows.
Privacy notes✓Ruflo memory, hooks, logs, telemetry-style metrics, worker output, prompts, code snippets, file paths, and task history may be stored under project-local state. Agent memory and embeddings can preserve sensitive implementation details beyond the current chat session. Federation, hosted UI, remote provider, plugin, or HTTP transport workflows may move task context beyond the local machine if enabled. Security scans, dependency checks, and code analysis can reveal private package names, vulnerabilities, paths, branch names, and repository structure. Review `.claude`, `.claude-flow`, helper scripts, logs, and exported memory before sharing a repository or support bundle.✓Local indexes, snapshots, file trees, symbol names, dependency graphs, snippets, read results, and search results can reveal proprietary code structure and implementation details. Upstream documents sensitive-file blocking for patterns such as environment files, credentials, and keys, but users should still review ignore rules and avoid indexing secret-heavy directories. CodeDB writes telemetry to `~/.codedb/telemetry.ndjson` unless `CODEDB_NO_TELEMETRY=1` is set, then syncs aggregate tool counts, latency, startup, file count, line count, language, version, and platform data on MCP session close. Upstream telemetry docs state that source code, file contents, file paths, and search queries are not collected. Remote public-repo queries and local MCP responses may still be logged by MCP clients, model providers, and terminal history.✓Memory-bank files can contain project plans, architecture notes, decisions, credentials accidentally pasted into notes, customer context, meeting details, or personal information. Tool calls may expose project names, file names, memory contents, root-path assumptions, and update text to the MCP client and model provider. Multi-project listing can reveal all projects stored under the memory-bank root. Auto-approved memory tools can persist model-generated statements as project memory without human review. Back up important memory-bank directories and review retention expectations before sharing them across clients or machines.✓Retrieved chunks can include private documents, product specs, policies, support content, internal procedures, historical project information, or customer-specific data. Retrieval queries, namespace IDs, tenant IDs, document chunks, citations, and tool outputs may be visible to the MCP client, model provider, Agentset logs, and application telemetry. Tenant IDs are useful for data segregation, but incorrect tenant or namespace configuration can expose the wrong knowledge base. Do not paste API keys, namespace IDs, tenant IDs, or retrieved private chunks into shared issue reports, screenshots, or repository files.
Prerequisites
  • Node.js 20 or newer.
  • Claude Code or another MCP client that can launch stdio servers.
  • A repository where Ruflo-generated `.claude`, `.claude-flow`, settings, helpers, hooks, and memory files are acceptable.
  • Review of which MCP tool groups, hooks, plugins, providers, and background workers should be enabled.
  • macOS or Linux on x64 or arm64 for the published native binary launcher.
  • Node.js 18 or newer when using the `codedeebee` npm launcher.
  • A local project directory that the MCP client exposes through roots or launches from.
  • Review of which local repositories, file types, generated artifacts, and secrets patterns may be indexed.
  • Node.js and npm available for `npx`.
  • A dedicated memory-bank root directory, separate from source repositories and secrets.
  • Project-specific subdirectories created under `MEMORY_BANK_ROOT`.
  • MCP client approval rules reviewed before allowing write or update operations.
  • Agentset account or self-hosted Agentset deployment with a populated namespace.
  • Agentset API key with access to the namespace Claude should query.
  • Node.js 18.17 or newer for running the `@agentset/mcp` package.
  • Namespace ID selected with `--ns` or `AGENTSET_NAMESPACE_ID`.
Install
npx ruflo@latest init wizard
npx -y codedeebee mcp
MEMORY_BANK_ROOT=ABSOLUTE_PATH_TO_MEMORY_BANK npx -y @allpepper/memory-bank-mcp@latest
Run `npx @agentset/mcp --ns <namespace-id>` with `AGENTSET_API_KEY` set in the MCP server environment.
Config
{
  "mcpServers": {
    "ruflo": {
      "command": "npx",
      "args": [
        "-y",
        "ruflo@latest",
        "mcp",
        "start"
      ],
      "type": "stdio"
    }
  }
}
{
  "mcpServers": {
    "codedb": {
      "command": "npx",
      "args": [
        "-y",
        "codedeebee",
        "mcp"
      ],
      "type": "stdio"
    }
  }
}
Manual-only setup:
MEMORY_BANK_ROOT=ABSOLUTE_PATH_TO_MEMORY_BANK npx -y @allpepper/memory-bank-mcp@latest
{
  "mcpServers": {
    "agentset": {
      "command": "npx",
      "args": ["-y", "@agentset/mcp@latest", "--ns", "ns_xxx"],
      "env": {
        "AGENTSET_API_KEY": "agentset_xxx"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Source-backed guides for putting this to work.

Compaction and Memory Hygiene for Long Claude Sessions

Use /compact, /memory, and CLAUDE.md hygiene to keep long Claude Code sessions accurate.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by kiannidev

Manage Prompt and Context Hygiene in Long Coding Sessions

Keep long Claude Code sessions focused and reviewable.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by MkDev11

Sandboxed Bash Setup For Autonomous Coding Agents

Configure Claude Code bash sandboxing for safer autonomous shell use.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by kiannidev

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.