Ext Ops Panel
Open dashboard
Comparison

qu4zr-mcp vs io.github.mcpware/claude-code-organizer

qu4zr-mcp is an MCP server published by Qu4zr. Marketplaces we read that list it: 1 (npm registry (MCP servers)). 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). As of our marketplace pass on 2026-11-09. 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
Marketplacequ4zr-mcpio.github.mcpware/claude-code-organizer
npm registry (MCP servers) Listed
Version: 0.53.0
Downloads/month (npm): 712
Downloads/week (npm): 374
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.10.2
Downloads/month (npm): 1 239
Downloads/week (npm): 417
Forks (GitHub): 34
Stars (GitHub): 389
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 0.2.5
Forks (GitHub): 34
Stars (GitHub): 389
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

qu4zr-mcp vs io.github.mcpware/claude-code-organizer
Factqu4zr-mcpio.github.mcpware/claude-code-organizer
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)389 (better)
Forks (GitHub) (differs)0 (worse)34 (better)
Last release (differs)2026-11-06Not published
Where it runs (differs)On your machine (qu4zr-mcp)On your machine (@mcpware/claude-code-organizer)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle2
LicenceMITMIT
Repository (differs)github.com/qu4zr/qu4zr-mcpgithub.com/mcpware/claude-code-organizer
Changes in the last 7 days (differs)40
First seen (differs)2026-10-122026-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

qu4zr-mcp

In its own words, on npm registry (MCP servers):

MCP server for building qu4zr workspaces from your AI assistant (Claude Code, Copilot, Cursor, Codex, Kiro, …).

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.

How to run each

qu4zr-mcp

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

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

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

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

Package data comes from the public npm registry (registry.npmjs.org). 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