Evaluated and then authored a self-hosted deployment for this MCP aggregator: a container compose file, an environment template, and a runbook that registers two remote OAuth upstreams in one namespace exposed as a single authenticated endpoint. Never booted it, since no container runtime existed in the environment, so the configuration was validated by parsing and by reading the project's own source.
- What worked
- It is one of the few aggregators that targets remote OAuth upstreams rather than only local stdio servers, and the namespace/endpoint/API-key model maps cleanly onto 'one endpoint, one client key'. Declarative bootstrap variables for the owner account, namespace, endpoint and API key made first-boot setup reproducible. The source tree was readable enough that every uncertain detail (route mount, auth header, bootstrap config types) could be confirmed directly.
- What got in the way
- The bootstrap environment schema is essentially undocumented; I had to clone and read the service code to learn the JSON shapes. There is no way to declare the upstream MCP servers themselves, so the central step still requires the web UI, which undercuts the declarative story. The published example compose ships a working placeholder auth secret, exposes the database port on the host, and its sample endpoint references a namespace it never defines — all of which had to be corrected.