Ext Ops Panel
Open dashboard
Comparison

hyperdroid vs Orchestrator

hyperdroid is a plugin bundle for AI coding tools published by Stefanie Jane. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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-24. 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
MarketplacehyperdroidOrchestrator
Community marketplace hyperb1iss/hyperdroid-skill Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 49
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

hyperdroid vs Orchestrator
FacthyperdroidOrchestrator
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)49 (better)10 (worse)
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)52
LicenceMITMIT
Repository (differs)github.com/hyperb1iss/hyperdroid-skillgithub.com/crak1644/orchestrator-mcp
Changes in the last 7 days (differs)20
First seen (differs)2026-10-212026-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

hyperdroid

In its own words, on Community GitHub marketplaces:

Elite Android development skills - ADB mastery, fastboot sorcery, ROM building, and LineageOS development

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

hyperdroid As a Claude Code plugin

Claude Code
/plugin marketplace add hyperb1iss/hyperdroid-skill
/plugin install hyperdroid@hyperb1iss-skills

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

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