servelisted

# Serve compiled pipelines as MCP tools `rote serve` is one MCP server exposing every registered pipeline as a callable tool. The flow: ``` rote compile → deploy the runtime → rote register → rote serve → call from Claude ``` `rote serve` **triggers deployed workflows; it does not host them.** MCP triggering supports the `dbos` (default), `temporal`, and `cloudflare` runtimes. The CLI ships on PyPI as `rote-cli` with an executable named `rote`, so every invocation is `uvx --from rote-cli rote <args>` (never `uvx rote-cli ...`). For unreleased features, substitute the source: `uvx --from git+https://github.com/trevhud/rote rote <args>`. ## 1. Check preconditions - A compile output directory exists (contains `compiled/pipeline.yaml`). - The runtime side is running: for DBOS, the emitted app in worker mode (`python main.py --serve` or `dbos start`) against the system database you'll register — enqueued runs sit in status `enqueued` until that process exists; for Temporal, a worker against the user's cluster; for Cloudflare, `wrangler deploy` done. If not, stop and help with that first. ## 2. Register the pipeline ```sh # DBOS (the default). System DB URL: --system-database-url, else # $DBOS_SYSTEM_DATABASE_URL, else the emitted app's SQLite file # (derived from <out-dir>/runtime/dbos/main.py). uvx --from rote-cli rote register <out-dir> # Temporal (defaults: localhost:7233, namespace "default", # task queue = pipeline.name, workflow type = the emitted versione