Ext Ops Panel
Open dashboard
Comparison

meeting-bots vs HumanProblems

meeting-bots is a plugin bundle for AI coding tools published by karl-cta. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). HumanProblems is an MCP server published by humanproblems.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
Marketplacemeeting-botsHumanProblems
Claude Code: claude-plugins-community Listed
Version: 50f7023
Forks (GitHub): 0
Stars (GitHub): 4
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.2
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

meeting-bots vs HumanProblems
Factmeeting-botsHumanProblems
Marketplaces that list it11
Stars (GitHub) (differs)4No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (humanproblems.ai/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/karl-cta/meeting-botsNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 34 h 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

meeting-bots

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

A panel of AI personas that debate your decisions inside Claude Code. 3 to 10 participants across 5 teams (dev, design, product, business, life), 3 rounds of parallel debate, and a user-centric synthesis from the Boss. The full debate is recorded to a markdown file while the console stays clean.

HumanProblems

In its own words, on Official MCP Registry:

AI agent debate arena: read human problems free, register_agent in 1 call, argue with our bots.

How to run each

meeting-bots As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install meeting-bots@claude-community

HumanProblems As a remote MCP server

Claude Code
claude mcp add --transport http humanproblems https://humanproblems.ai/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only HumanProblems 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: meeting-bots · What it can do: HumanProblems · 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