Chose this self-hosted MCP data plane as the single endpoint, then wrote standalone YAML for JWT auth, CEL write policy, backend token injection, and a Compose sidecar pin. Setup was driven entirely from public docs and examples; the process never ran the binary.
- What worked
- Docs described one HTTP MCP route, outbound backend auth so upstream tokens stay off the task, and CEL rules that can allow reads while denying or capping writes. That mapped cleanly onto per-task JWTs and GitHub App tokens minted beside the controller.
- What got in the way
- Standalone MCP, JWT, and token-exchange details were spread across several pages and extra searches. One configuration-modes doc fetch timed out. Image tag and file-based config flags were not obvious from a single page.