Ext Ops Panel
Open dashboard
Comparison

kit vs Orchestrator

kit is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.

kit is a plugin bundle for AI coding tools published by agents-kit. No marketplace we read lists it any more. 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. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplacekitOrchestrator
Community marketplace alopezari/agents-kit Removed on 2026-10-15
Version: 0.5.0
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

kit vs Orchestrator
Factkitno longer listed · Orchestrator
Marketplaces that list it (differs)03
Stars (GitHub) (differs)010
Forks (GitHub) (differs)02
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (orchestrator-mcp-server)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
Parts of the bundle (differs)Not published2
Licence (differs)Not statedMIT
Repository (differs)github.com/alopezari/agents-kitgithub.com/crak1644/orchestrator-mcp
Changes in the last 7 days00
First seen (differs)2026-10-142026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of kit

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • Endor Labs Agent Kit

    Endor Labs workflow agents and setup for Claude Code.

    by Endor Labs · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • Endor Labs Agent Kit

    Endor Labs workflow agents and setup for Claude Code.

    by Endor Labs · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • gitkb

    Give Claude Code the knowledge layer your agents deserve: local code intelligence, a persistent knowledge graph, task context, and team sync.

    by gitkb · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • agent-sdk-dev

    Development kit for working with the Claude Agent SDK

    by Ashwin Bhat · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • harness-boot

    Multi-agent development harness for Claude Code. Your AI has speed; we give it direction — through living specs and focused specialist agents.

    by qwerfunch · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • claude-agent-sdk-dev

    Development tools and documentation for building applications with the Claude Agent SDK. Covers Python and TypeScript APIs, core features, advanced features, and integrations.

    by Em · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

kit

In its own words, on Community GitHub marketplaces:

The agents kit inside Claude Code: the /flow pane

Orchestrator

In its own words, on Official MCP Registry:

Let one coding-agent CLI consult another: Codex, Claude Code, OpenCode, Copilot or Antigravity.

How to run each

kit

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Orchestrator As a local MCP server: PyPI package

Claude Code
claude mcp add --env "ORCHESTRATOR_CONFIG=<YOUR_ORCHESTRATOR_CONFIG>" --env "ORCHESTRATOR_HOST_RUNTIME=<YOUR_ORCHESTRATOR_HOST_RUNTIME>" --transport stdio orchestrator-mcp -- uvx orchestrator-mcp-server

Requires: ORCHESTRATOR_CONFIG, ORCHESTRATOR_HOST_RUNTIME

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 kit publish no settings it asks for, so we do not compare settings.

What it can do: kit · What it can do: Orchestrator · Compare two other plugins

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. Package data comes from the Python Package Index (pypi.org). 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