Ext Ops Panel
Open dashboard
Comparison

mexus-agent-team vs AI2Human

mexus-agent-team is a plugin bundle for AI coding tools published by yofine. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). AI2Human is an MCP server published by richard7463. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
Marketplacemexus-agent-teamAI2Human
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 11
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.2
Downloads/month (PyPI): 102
Downloads/week (PyPI): 23
Forks (GitHub): 2
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

mexus-agent-team vs AI2Human
Factmexus-agent-teamAI2Human
Marketplaces that list it11
Stars (GitHub) (differs)11 (better)1 (worse)
Forks (GitHub) (differs)0 (worse)2 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (ai2human-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 2
Parts of the bundle (differs)5Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/yofine/mexus-agent-teamgithub.com/ai2humanagent/ai2humanwork
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

mexus-agent-team

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

Standalone Markdown-only Agent Team plugin for Claude Code and Codex. Coordination happens through ordinary Markdown files in the current project: agent-team/ ├── mission-workflow.md ├── agents.md └── missions/<mission-name>/ ├── mission.md ├── agents.md ├── kanban.md ├── roundtable.md └── squad-lead.md

AI2Human

In its own words, on Official MCP Registry:

Dispatch human-execution tasks with proof verification, local checks, and compliance reviews.

How to run each

mexus-agent-team As a Claude Code plugin

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

AI2Human As a local MCP server: PyPI package

Claude Code
claude mcp add --env "AI2HUMAN_AGENT_KEY=<YOUR_AI2HUMAN_AGENT_KEY>" --env "AI2HUMAN_API_KEY=<YOUR_AI2HUMAN_API_KEY>" --transport stdio ai2human-mcp -- uvx ai2human-mcp

Requires: AI2HUMAN_AGENT_KEY (secret), AI2HUMAN_API_KEY (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

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

What it can do: mexus-agent-team · What it can do: AI2Human · 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