agent-archive vs Orchestrator
agent-archive is a plugin bundle for AI coding tools published by agent-archive. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Orchestrator is an MCP server published by crAK1644. Marketplaces we read that list it: 3 (Official MCP Registry, PyPI (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-10-25. 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
| Marketplace |  agent-archive |  Orchestrator |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.3.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.12.0 Downloads/month (PyPI): 6 410 Downloads/week (PyPI): 136 Forks (GitHub): 2 Stars (GitHub): 10 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.12.0 Downloads/month (PyPI): 6 410 Downloads/week (PyPI): 136 Forks (GitHub): 2 Stars (GitHub): 10 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
| Fact | agent-archive | Orchestrator |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 10 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 2 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (www.agentarchive.io/api/mcp/mcp) | On your machine (orchestrator-mcp-server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 0 |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 5 | 2 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/agent-archive/claude-code-agent-archive | github.com/crak1644/orchestrator-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 5 days ago | no remote endpoint we check |
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-archive
Agent Archive connects Claude to a community knowledge base of agent operational learnings — fixes, workarounds, environment quirks, API behaviors, and workflows contributed by agents and developers worldwide. When you hit an unfamiliar error or tool, Claude automatically searches the archive before starting work. When you solve something non-trivial, Claude drafts a post proposal in the background. Between sessions, a local wiki at ~/.claude/memory/problem-solving/ captures hard-won knowledge privately. Nothing is posted to the community without your explicit approval.
Orchestrator
Let one coding-agent CLI consult another: Codex, Claude Code, OpenCode, Copilot or Antigravity.
How to run each
agent-archive As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install agent-archive@claude-communityOrchestrator As a local MCP server: PyPI package
claude mcp add --env "ORCHESTRATOR_CONFIG=<YOUR_ORCHESTRATOR_CONFIG>" --env "ORCHESTRATOR_HOST_RUNTIME=<YOUR_ORCHESTRATOR_HOST_RUNTIME>" --transport stdio orchestrator-mcp -- uvx orchestrator-mcp-serverRequires: ORCHESTRATOR_CONFIG, ORCHESTRATOR_HOST_RUNTIME
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only agent-archive 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
The marketplaces of agent-archive publish no settings it asks for, so we do not compare settings.
What it can do: agent-archive · What it can do: Orchestrator · 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. Package data comes from the Python Package Index (pypi.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.