OpenImageDebugger MCP vs Orchestrator
OpenImageDebugger MCP is an MCP server published by OpenImageDebugger. Marketplaces we read that list it: 1 (Official MCP Registry). 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-10-29. 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
| Marketplace |  OpenImageDebugger MCP |  Orchestrator |
|---|---|---|
| Official MCP Registry | Listed Version: 0.3.6 Downloads/month (PyPI): 128 Downloads/week (PyPI): 24 Forks (GitHub): 51 Stars (GitHub): 250 Not marked · First seen |
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
| Fact | OpenImageDebugger MCP | Orchestrator |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 250 (better) | 10 (worse) |
| Forks (GitHub) (differs) | 51 (better) | 2 (worse) |
| Last release (differs) | 2026-10-26 | Not published |
| Where it runs (differs) | On your machine (oid-mcp) | On your machine (orchestrator-mcp-server) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 0 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/openimagedebugger/openimagedebugger | github.com/crak1644/orchestrator-mcp |
| Changes in the last 7 days (differs) | 1 | 2 |
| First seen | 2026-10-11 | 2026-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
OpenImageDebugger MCP
MCP server giving AI agents eyes on OpenImageDebugger buffers in live gdb/lldb sessions
Orchestrator
Let one coding-agent CLI consult another: Codex, Claude Code, OpenCode, Copilot or Antigravity.
How to run each
OpenImageDebugger MCP As a local MCP server: PyPI package
claude mcp add --transport stdio oid-mcp -- uvx oid-mcpOrchestrator 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-serverRequires: 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 OpenImageDebugger MCP publish no settings it asks for, so we do not compare settings.
What it can do: OpenImageDebugger MCP · What it can do: Orchestrator · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). 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.