mcp-workbay-orchestrator

# WorkBay Orchestrator MCP > **Component of the `workbay` stack.** You usually install `workbay`, not this package directly. MCP server for orchestration, lane management, worker daemons, review dispatch, and ACE metrics. ## Installation ### From PyPI (recommended) ```bash pip install mcp-workbay-orchestrator # or, as an isolated tool: uv tool install mcp-workbay-orchestrator # or, ad-hoc without installing: uvx mcp-workbay-orchestrator --help ``` `mcp-workbay-orchestrator` declares `mcp-workbay-handoff>=0.5.0,<0.6.0` as a required dependency; pip resolves it from PyPI automatically. `workbay-codex-bridge` remains optional unless you want the local bridge backend. ### From the monorepo source tree (development) From this package root inside `workbay`: ```bash cd packages/mcp-workbay-orchestrator python -m pip install -e ".[dev]" ``` When developing both MCP servers in lockstep, install the sibling handoff package as an editable first so the orchestrator picks it up: ```bash pip install -e ../mcp-workbay-handoff pip install -e ".[dev]" ``` ## Development Run package-local commands from the package root: ```bash make lint-orchestrator make fix-lint-orchestrator make format-orchestrator make mypy-orchestrator make test-orchestrator make check-orchestrator ``` The package Makefile keeps `workbay-codex-bridge` as an optional sibling source path for local bridge-backend development, but it expects `mcp-workbay-handoff` to be installed as a normal package dependency. Direct commands also work: ```bash PYTHONPATH=src python -m ruff check src tests PYTHONPATH=src python -m mypy src PYTHONPATH=src python -m pytest tests -q ``` ## Token-Efficient Usage For bounded reads and compact caller patterns, follow the shared guide in [`packages/mcp-workbay-handoff/docs/guides/token-efficient-usage.md`](../mcp-workbay-handoff/docs/guides/token-efficient-usage.md). The orchestrator package reuses that guidance instead of maintaining a separate copy of the same paramet…