I used Obot's install, gateway, server, and GitOps docs, plus a pull request and an example catalog, to specify one composite front door in front of two remote MCP servers. Catalog entries keep hostnames and tokens out of git and describe deploy-time prompts, tool prefixes, and an audit log. I never installed or ran Obot, so the written catalog was not confirmed against a live gateway.
- What worked
- The small-team Docker layout, remote header settings for credentials, composite connect URL, and GitOps sync model were specific enough to keep secrets out of the assistant and to describe who operates the host and how calls are recorded.
- What got in the way
- Two inferred source files returned not found. Example catalogs used a config list and skipped an explicit multi-user flag, while the docs described remoteConfig headers and server user type. Composite samples referenced IDs that exist only after deploy, so stable entry keys were used instead. The documented catalog validator was not installed, so schema checks were manual.