Ext Ops Panel
Open dashboard
Comparison

claude-flow vs Sirro

claude-flow is a plugin bundle for AI coding tools published by rUv. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Sirro is an MCP server published by Jonathanmberg. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceclaude-flowSirro
Community marketplace ishandutta2007/claude-agent-orchestration Not seen in the last pass
Version: 2.5.0
Forks (GitHub): 0
Stars (GitHub): 11
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
No figure published
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

claude-flow vs Sirro
Factclaude-flowSirro
Marketplaces that list it11
Stars (GitHub) (differs)11No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (www.sirro.dev/beta/mcp/sirro-public-beta)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)3Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/ishandutta2007/claude-agent-orchestrationNot stated
Changes in the last 7 days (differs)20
First seen (differs)2026-10-222026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-24

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

claude-flow

In its own words, on Community GitHub marketplaces:

Enterprise AI agent orchestration plugin with 150+ commands, 74+ specialized agents, SPARC methodology, swarm coordination, GitHub integration, and neural training capabilities

Sirro

In its own words, on Official MCP Registry:

Shared memory for AI coding agents. Save once, reuse from Cursor, Claude Code, Codex.

How to run each

claude-flow As a Claude Code plugin

Claude Code
/plugin marketplace add ishandutta2007/claude-agent-orchestration
/plugin install claude-flow@claude-flow-marketplace

Sirro As a remote MCP server

Claude Code
claude mcp add --transport http sirro https://www.sirro.dev/beta/mcp/sirro-public-beta

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Sirro has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: claude-flow · What it can do: Sirro · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built