Ext Ops Panel
Open dashboard
Comparison

the-council vs Perspect

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. Perspect is an MCP server published by tryperspect.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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

Where each is published
Marketplacethe-councilPerspect
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.0.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

the-council vs Perspect
Factthe-councilno longer listed · Perspect
Marketplaces that list it (differs)01
Stars (GitHub) (differs)30
Forks (GitHub) (differs)30
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (perspect-ai-backend.onrender.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/dantespeak85/the-councilgithub.com/nkbros12k/perspect-mcp
Changes in the last 7 days00
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-24

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.

  • vern

    Multi-LLM discovery pipelines, competing AI personas, VernHole council tiers, Historian indexing, and Oracle vision. One idea in, battle-tested plan out. Run your idea through…

    by Justin Donohoo · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • Pilot5

    Five AI models debate your decision blind, then give one recommendation and the strongest objection.

    by pilot5.ai · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • 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.

    by 2steaks · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • Council of High Intelligence

    18 AI personas deliberate your hardest decisions — structured multi-round deliberation with genuine model diversity. One command: /council

    by 0xNyk · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • Advisor

    Consult a stronger model before major decisions, when stuck, and before declaring done.

    by Cursor · Plugin bundle

    Listed on: Cursor: cursor/plugins · Describes nearly the same job

  • LLM Council Creator

    Scaffold new LLM Council projects from existing templates (Template, Grounded, Decide) or build bespoke council repos for specific purposes.

    by danielrosehill · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

the-council

In its own words, on Community GitHub marketplaces:

Multi-model advisory board using Codex CLI and Gemini CLI

Perspect

In its own words, on Official MCP Registry:

Convene a panel of expert AI personas to debate any decision from every side.

How to run each

the-council

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

Perspect As a remote MCP server

Claude Code
claude mcp add --transport http perspect https://perspect-ai-backend.onrender.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 Perspect 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: Perspect · 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.

Where the data comes from: how the catalog is built