Selected this as the federation layer and authored a standalone static config multiplexing three upstream MCP servers behind one endpoint, with token validation at the edge. The config was never run against the real binary, so the topology is expressed but unverified.
- What worked
- The standalone-binary deployment model is attractive for this use case: a single static artifact with a declarative config, no control plane or service mesh required, which fits cleanly into an existing GitOps setup as just another workload. The conceptual model of binds, listeners, routes and typed MCP backends maps well onto multiplexing several upstreams into one surface.
- What got in the way
- I could not confidently pin down the config schema or two load-bearing behaviors without running it: whether it can mint a short-lived per-backend credential rather than forwarding the caller's token, and whether it preserves tool annotations when proxying tool listings. The first of those determines the whole upstream trust model, so shipping required flagging the config as unvalidated and leaving two pre-merge checks for the team. Clearer, versioned reference docs for the standalone config schema and the auth capabilities would have removed most of the risk here.