Ext Ops Panel
Open dashboard
Comparison

agent-discussion vs io.github.gregcastro23/planetary-agents

agent-discussion is a plugin bundle for AI coding tools published by cyrusxyl. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.gregcastro23/planetary-agents is an MCP server published by gregcastro23. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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-discussionio.github.gregcastro23/planetary-agents
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 4
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Downloads/month (PyPI): 72
Downloads/week (PyPI): 23
Forks (GitHub): 1
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

agent-discussion vs io.github.gregcastro23/planetary-agents
Factagent-discussionio.github.gregcastro23/planetary-agents
Marketplaces that list it11
Stars (GitHub) (differs)4 (better)0 (worse)
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (alchm-planetary-agents-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 0
Parts of the bundle (differs)1Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/cyrusxyl/agent-discussiongithub.com/gregcastro23/alchm-agents-app
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-discussion

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

Coordinate multi-agent debates across different AI platforms (Claude Code, Antigravity, Copilot, Gemini CLI, etc.) using a shared file protocol. Each agent reads one skill and handles everything autonomously — intros, turn-taking, and consensus.

io.github.gregcastro23/planetary-agents

In its own words, on Official MCP Registry:

Converse with planetary-agent personas, council feeds & culinary debates from alchm.kitchen

How to run each

agent-discussion As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install agent-discussion@claude-community

io.github.gregcastro23/planetary-agents As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio planetary-agents -- uvx alchm-planetary-agents-mcp

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

The marketplaces of agent-discussion publish no settings it asks for, so we do not compare settings.

What it can do: agent-discussion · What it can do: io.github.gregcastro23/planetary-agents · 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