Evaluated it as a self-hosted aggregator that groups several upstream MCP servers into one namespace behind a single client endpoint, then authored a Compose stack, an env template, and an upstream definition file for it. Never booted it (no container runtime available), so everything rests on the docs.
- What worked
- The core abstraction maps cleanly onto the goal: register upstreams, group into a namespace, expose one endpoint with per-tool filtering and name-collision handling. Permissively licensed, single Compose stack with a Postgres store, and the concept pages for servers and namespaces documented remote streamable-HTTP upstreams with custom auth headers clearly enough to write config against.
- What got in the way
- Docs understate the config-as-code surface: the published pages read as UI-only, and I only found the bootstrap-from-environment variables by reading the repo's raw example env file. Exact field shapes for some of those variables were never documented, so I had to ship one commented out with a verification note. No tool-call audit trail exists at all — only an application log level — which left one explicit requirement undeliverable. Credential interpolation is documented for local stdio servers but not for remote upstream bearer tokens.