Ext Ops Panel
Open dashboard
Comparison

agent-council vs Scope

agent-council is a plugin bundle for AI coding tools published by Avyayalaya. Marketplaces we read that list it: 2 (Copilot CLI: github/awesome-copilot, Community GitHub marketplaces). Scope is an MCP server published by jackgillen15-dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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
Marketplaceagent-councilScope
Copilot CLI: github/awesome-copilot Listed
Version: 0.1.3
Forks (GitHub): 7
Stars (GitHub): 11
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
Downloads/month (npm): 116
Downloads/week (npm): 30
Forks (GitHub): 1
Stars (GitHub): 1
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

agent-council vs Scope
Factagent-councilScope
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)11 (better)1 (worse)
Forks (GitHub) (differs)7 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@jackgillen15-dev/scope-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 03, secrets among them: 1
Parts of the bundle (differs)8Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/avyayalaya/agent-councilgithub.com/scope-bid/scope-mcp
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

agent-council

In its own words, on Copilot CLI: github/awesome-copilot:

A runtime-portable 5-agent quality gate that adjudicates text artifacts before they ship. Five role-conditioned LLM deliberators run a 2-round async protocol with cross-read rebuttal and return one verdict — SHIP, REVISE, or HOLD — plus a structured revision brief and a full audit transcript.

Scope

In its own words, on Official MCP Registry:

Dispatch litigation work to legal-services vendors from any MCP-compatible AI workflow.

How to run each

agent-council As a Claude Code plugin

Claude Code
/plugin marketplace add avyayalaya/agent-council
/plugin install agent-council@agent-council

Scope As a local MCP server: npm package

Claude Code
claude mcp add --env "SCOPE_API_TOKEN=<YOUR_SCOPE_API_TOKEN>" --transport stdio scope-mcp -- npx -y @jackgillen15-dev/scope-mcp

Requires: SCOPE_API_TOKEN (secret)

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

Only agent-council asks for

  • COUNCIL_CONFIG

Only Scope asks for

  • SCOPE_API_BASE
  • SCOPE_API_TOKEN (secret)
  • SCOPE_ORG_SLUG

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: agent-council · What it can do: Scope · Compare two other plugins

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