Ext Ops Panel
Open dashboard
Comparison

bOpen Core vs Orchestrator

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

bOpen Core is a plugin bundle for AI coding tools published by b-open-io. No marketplace we read lists it any more. Orchestrator is an MCP server published by crAK1644. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-13. 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
MarketplacebOpen CoreOrchestrator
Community marketplace b-open-io/claude-plugins Removed on 2026-10-17
Version: 1.1.177
Forks (GitHub): 4
Stars (GitHub): 16
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.12.0
Downloads/month (PyPI): 6 410
Downloads/week (PyPI): 52
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): 52
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

bOpen Core vs Orchestrator
FactbOpen Coreno longer listed · Orchestrator
Marketplaces that list it (differs)02
Stars (GitHub) (differs)1610
Forks (GitHub) (differs)42
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)27Not a bundle
Licence (differs)Not statedMIT
Repository (differs)github.com/b-open-io/promptsgithub.com/crak1644/orchestrator-mcp
Changes in the last 7 days00
First seen (differs)2026-10-152026-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 bOpen Core

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

  • claude-code-survival-kit

    10 slash commands and 3 agent definitions distilled from 6 months of daily Claude Code use. Not a framework -- just the patterns that survived: multi-agent build pipelines…

    by rjspence3 · Plugin bundle

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

  • claude-mods

    Skills, rules, hooks, agents and output styles for Claude Code: test-gated landing for parallel agent work, framework knowledge with staleness verifiers, and security checks aimed…

    by 0xDarkMatter · Plugin bundle

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

  • closedloop

    Open-source Claude Code plugins for multi-agent software delivery. Plan-first SDLC workflow, code review, LLM quality judges, and self-learning — grounded in your codebase…

    by closedloop-ai · Plugin bundle

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

  • claude-forge

    Production-grade development environment for Claude Code with 16 specialized agents, 35 slash commands, 33 skills, 22 hooks + 9 opt-in examples (21 events), 14 rules, and 4 MCP…

    by Sangrok Jung · Plugin bundle

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

  • agentic-bundle-essentials

    Install the "Essentials" editorial skill bundle for Claude Code.

    by sickn33 and contributors · Plugin bundle

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

  • conjure

    Build Claude Code skills, agents, hooks, and MCP servers from plain-language descriptions. Generate, validate, and ship plugins without writing boilerplate.

    by john-farina · Plugin bundle

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

Its card, with similar plugins by marketplace

What each says it does

bOpen Core

In its own words, on Community GitHub marketplaces:

Cross-agent development skills, hooks, orchestration, and optional custom-agent adapters for Claude Code, Codex, and Grok Build

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

bOpen Core

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

What it can do: bOpen Core · 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