the-council vs Meta Council
the-council is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.
the-council is a plugin bundle for AI coding tools published by Tom Wolinitz. No marketplace we read lists it any more. Meta Council is an MCP server published by meta-council.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Meta Council | |
|---|---|---|
| Community marketplace dantespeak85/the-council | Removed on 2026-10-17 Version: 1.6.5 Forks (GitHub): 3 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.4.0 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
| Fact | the-councilno longer listed · | Meta Council |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | No figure on GitHub |
| Forks (GitHub) (differs) | 3 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (meta-council.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/dantespeak85/the-council | github.com/daliu/meta-council |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 2 days ago returned HTTP 405 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of the-council
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Five AI models debate your decision blind, then give one recommendation and the strongest objection.
-
team-deliberation
Stress-test an idea or decision with a panel of independent specialist subagents: blind analysis, cross-examination, fact checks and a synthesis that keeps the dissent.
-
18 AI personas deliberate your hardest decisions — structured multi-round deliberation with genuine model diversity. One command: /council
-
Put a decision to a council of top AI models and get one brief: verdict, splits, risks, next steps.
-
agent-council
Run a structured multi-agent debate by spawning a panel of expert agents on any question, with convergence-aware iteration and typed synthesis output via the `agent-council` CLI…
-
Consult a stronger model before major decisions, when stuck, and before declaring done.
What each says it does
the-council
Multi-model advisory board using Codex CLI and Gemini CLI
Meta Council
Multi-expert decision intelligence with transparent synthesis and auditable workflows.
How to run each
the-council
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Meta Council As a remote MCP server
claude mcp add --transport http decision-intelligence https://meta-council.com/mcp --header "X-API-Key: <YOUR_X_API_KEY>"Requires: X-API-Key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Meta Council 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: the-council · What it can do: Meta Council · 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.