claude-flow
claude-flow is an MCP server published by ruvnet, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. It is a community implementation. Last verified 2026-08-25.
Does claude-flow support the current MCP specification (2026-07-28)?
Not yet confirmed. claude-flow is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-25.
Is claude-flow a first-party (official) MCP server?
No. claude-flow is a community-published MCP server from ruvnet, not a first-party vendor server (last verified 2026-08-25).
How do I connect to claude-flow?
claude-flow is available via the package npm:claude-flow, the official MCP Registry under io.github.ruvnet/claude-flow, the source repository at https://github.com/ruvnet/ruflo. Authentication: none. Transports: stdio.
Does claude-flow support MCP revision 2025-11-25?
Yes. claude-flow supports MCP revision 2025-11-25 (checked 2026-08-25).
When were claude-flow's facts last verified?
2026-08-25. Each fact on this page links to the sources used to verify it.
claude-flow is a community agent-orchestration harness by the developer
rUv (GitHub ruvnet), exposing MCP tooling for multi-agent workflows. The
project has since been renamed to "ruflo": the repository is now
ruvnet/ruflo and the package publishes to npm as ruflo, though the
older claude-flow npm package still exists and the official MCP
Registry record still lists the claude-flow name at a September 2025
alpha version.
The name matters for one reason beyond bookkeeping: the project carries a critical vulnerability. CVE-2026-59726 (GHSA-c4hm-4h84-2cf3), an unauthenticated remote code execution in the ruflo MCP bridge's default docker-compose deployment, is rated CVSS 10.0 and was patched in ruflo 3.16.3. It is covered in our news.
Authority is community: the publisher is an individual, not the vendor
of any fronted service, and the name "claude-flow" carries no Anthropic
affiliation. No surface names a supported MCP specification revision, so
spec_status is unknown.
Which MCP spec revisions does claude-flow support?
claude-flow has 1 verified spec-support record. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source |
How widely adopted is claude-flow?
Ranked #10 in The MCP 500 with Adoption Index 72.18 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| Docker MCP Catalog | no | API · |
| npm downloads (weekly) | 17,661 | API · |
| GitHub stars | 72,518 | API · |
| GitHub forks | 8,585 | API · |
| Last push | 2026-09-15T14:19:56Z | API · |
| Repository archived | no | API · |
Repository and package signals for claude-flow
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Created
- Open issues
- 844
- Primary language
- TypeScript
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- Present
- Security policy
- Present
Declared topics: agentic-ai, agentic-framework, agentic-workflow, agents, ai-agents, ai-assistant, ai-skills, autonomous-agents, claude-code, codex, dsh-plugin, harness, mcp-server, multi-agent, multi-agent-systems, npm, skills, swarm, swarm-intelligence, typescript — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
3.38.20- Last published
- First published
- Releases
- 818
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 26
- Unpacked size
- 13.6 MB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: repo-readme
· confidence 0.80 (Good).
- Official MCP Registry record io.github.ruvnet/claude-flow version 2.0.0-alpha.107 (published 2025-09-10) - npm package claude-flow, stdio transport; the record is nearly a year old and predates the project's rename to ruflo - accessed
- ruvnet/ruflo repository - the former claude-flow project, now named "ruflo" (package.json name claude-flow at version 3.34.0, npm also published as ruflo); owner is the personal account ruvnet (rUv), an agent meta-harness for multi-agent swarms and workflows; no MCP SDK dependency in package.json - accessed
- GitHub security advisory GHSA-c4hm-4h84-2cf3 / CVE-2026-59726, "Unauthenticated RCE in ruflo MCP bridge default docker-compose deployment" - critical, CVSS 10.0, published 2026-07-01; npm package ruflo vulnerable below 3.16.3, patched in 3.16.3 - accessed
- Staleness re-verification 2026-08-18 - the repository was renamed: https://github.com/ruvnet/claude-flow 301-redirects to https://github.com/ruvnet/ruflo, which is not archived and was pushed 2026-08-18. The official registry record io.github.ruvnet/claude-flow still carries the old repository URL and has not been republished since v2.0.0-alpha.107 (2025-09-10) - accessed
- ruflo repository, v3/@claude-flow/mcp/README.md - carries an "MCP 2025-11-25" badge and states "MCP 2025-11-25 Compliant - Standalone Model Context Protocol server implementation with full Resources, Prompts, and Tasks support"; a "Resources (MCP 2025-11-25)" section documents the surface - accessed
- npm registry, claude-flow latest - version 3.38.20, depends on @claude-flow/mcp 3.0.0-alpha.10; the sibling package ruflo is published at the same version from the same commit - accessed