Ext Ops Panel
Open dashboard
Comparison

mako-ai vs io.github.mcpware/claude-code-organizer

mako-ai is a plugin bundle for AI coding tools published by drhalto. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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-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
Marketplacemako-aiio.github.mcpware/claude-code-organizer
Claude Code: claude-plugins-community Listed
Version: 0.4.3
Forks (GitHub): 4
Stars (GitHub): 54
Not marked · First seen
Listed
Version: 0.2.5
Forks (GitHub): 34
Stars (GitHub): 385
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 0.10.2
Downloads/month (npm): 346
Downloads/week (npm): 74
Forks (GitHub): 34
Stars (GitHub): 385
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

mako-ai vs io.github.mcpware/claude-code-organizer
Factmako-aiio.github.mcpware/claude-code-organizer
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)54 (worse)385 (better)
Forks (GitHub) (differs)4 (worse)34 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (agentmako)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)92
Licence (differs)Not statedMIT
Repository (differs)github.com/drhalto/agentmakogithub.com/mcpware/claude-code-organizer
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

mako-ai

In its own words, on Claude Code: claude-plugins-community:

Project intelligence skills for Claude Code. Teaches Claude when to use Mako's MCP tools (context packets, code and schema search, diagnostics, RLS audits) instead of grep-walking the repo. Pairs with the agentmako CLI/MCP server (npm install -g agentmako).

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

mako-ai As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install mako-ai@claude-community

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: mako-ai · What it can do: io.github.mcpware/claude-code-organizer · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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