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
| Marketplace | ||
|---|---|---|
| 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
| Fact | bOpen Coreno longer listed · | Orchestrator |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 16 | 10 |
| Forks (GitHub) (differs) | 4 | 2 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (orchestrator-mcp-server) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 0 |
| Parts of the bundle (differs) | 27 | Not a bundle |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/b-open-io/prompts | github.com/crak1644/orchestrator-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 2026-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.
-
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…
-
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…
-
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…
-
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…
-
Install the "Essentials" editorial skill bundle for Claude Code.
-
Build Claude Code skills, agents, hooks, and MCP servers from plain-language descriptions. Generate, validate, and ship plugins without writing boilerplate.
What each says it does
bOpen Core
Cross-agent development skills, hooks, orchestration, and optional custom-agent adapters for Claude Code, Codex, and Grok Build
Orchestrator
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 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.