Ext Ops Panel
Open dashboard
Comparison

decision-council vs mumo

decision-council is a plugin bundle for AI coding tools published by fusion-software-ltd. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). mumo is an MCP server published by mumo.chat. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-25. 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
Marketplacedecision-councilmumo
Claude Code: claude-plugins-community Listed
Version: 1.18.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.2.2
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 0
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

decision-council vs mumo
Factdecision-councilmumo
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mumo.chat/api/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)172
Licence (differs)proprietaryMIT
Repository (differs)github.com/fusion-software-ltd/decision-councilgithub.com/mumo-chat/mumo-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 days ago

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

decision-council

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

AI advisory panel for decisions that matter. Decision Council assembles a panel of independent AI advisors to debate your decision from multiple angles, cross-examine each other's reasoning, and deliver a scored recommendation with a visual dashboard. Includes a brutal-truth Mirror agent, pre-mortem analysis, and a structured decision-recording flow that builds your decision track record over time.

mumo

In its own words, on Official MCP Registry:

Multi-model deliberation over MCP: full responses plus typed cross-model reactions from other labs.

How to run each

decision-council As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install decision-council@claude-community

mumo As a remote MCP server

Claude Code
claude mcp add --transport http mumo https://mumo.chat/api/mcp --header "Authorization: Bearer <YOUR_MUMO_API_KEY>"

Requires: Authorization header

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

Only mumo 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: decision-council · What it can do: mumo · 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