Ext Ops Panel
Open dashboard
Comparison

io.github.mcpware/claude-code-organizer vs walkerOS Flow

io.github.mcpware/claude-code-organizer is an MCP server published by mcpware. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). walkerOS Flow is an MCP server published by walkeros.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
Marketplaceio.github.mcpware/claude-code-organizerwalkerOS Flow
Official MCP Registry Listed
Version: 0.10.2
Downloads/month (npm): 346
Downloads/week (npm): 74
Forks (GitHub): 33
Stars (GitHub): 383
Not marked · First seen
Listed
Version: 4.5.0
Downloads/month (npm): 2 857
Downloads/week (npm): 902
Forks (GitHub): 23
Stars (GitHub): 348
Not marked · First seen
Claude Code: claude-plugins-community Listed
Version: 0.2.5
Forks (GitHub): 33
Stars (GitHub): 383
Not marked · First seen
Not listed

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

io.github.mcpware/claude-code-organizer vs walkerOS Flow
Factio.github.mcpware/claude-code-organizerwalkerOS Flow
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)383 (better)348 (worse)
Forks (GitHub) (differs)33 (better)23 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@mcpware/claude-code-organizer)On your machine (@walkeros/mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/mcpware/claude-code-organizergithub.com/elbwalker/walkeros
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

io.github.mcpware/claude-code-organizer

In its own words, on Official MCP Registry:

Organize Claude Code memories, skills, MCP servers, commands, agents, rules via drag-and-drop.

walkerOS Flow

In its own words, on Official MCP Registry:

Build, validate, simulate, and deploy walkerOS event pipelines

How to run each

io.github.mcpware/claude-code-organizer As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio claude-code-organizer -- npx -y @mcpware/claude-code-organizer

walkerOS Flow As a local MCP server: npm package

Claude Code
claude mcp add --env "WALKEROS_TOKEN=<YOUR_WALKEROS_TOKEN>" --transport stdio flow -- npx -y @walkeros/mcp

Requires: WALKEROS_TOKEN (secret)

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

Tools each declares

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

Settings each asks for

The marketplaces of io.github.mcpware/claude-code-organizer publish no settings it asks for, so we do not compare settings.

What it can do: io.github.mcpware/claude-code-organizer · What it can do: walkerOS Flow · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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