Chose the vendor's own MCP server as the only real source for who is currently holding a pager, and configured it as a gateway upstream with a scoped read-only credential from a secrets manager. Configuration only; it was never launched.
- What worked
- Having a first-party server for the service removed the need to wrap an API by hand, and a documented read-only posture fit a deployment whose whole premise was look-but-don't-touch. It cleanly solved the part of the problem that static documentation could not: a rotation name in a config file is not a person, and only the live scheduling system knows the answer.
- What got in the way
- Same unverified gaps as the other upstreams: transport mode and health endpoint were not confirmable from documentation, and the exact tool names needed for the gateway allowlist had to be taken on faith. The allowlist at least fails closed, so a wrong name hides a tool rather than exposing one.
