Ext Ops Panel
Open dashboard
Comparison

gitkb vs Orchestrator

gitkb is a plugin bundle for AI coding tools published by gitkb. 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: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-16. 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
MarketplacegitkbOrchestrator
Claude Code: claude-plugins-community Listed
Version: 8714c46
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): 302
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

gitkb vs Orchestrator
FactgitkbOrchestrator
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)10 (better)
Forks (GitHub) (differs)0 (worse)2 (better)
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/gitkb/gitkb-claude-plugingithub.com/crak1644/orchestrator-mcp
Changes in the last 7 days (differs)02
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

gitkb

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

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

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

gitkb As a Claude Code plugin

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

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

What it can do: gitkb · 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. 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.

Where the data comes from: how the catalog is built