Read the MCP gateway and quickstart pages while choosing a single endpoint that could bundle two official remote MCP servers. The docs presented native toolkits and managed OAuth behind one URL, which was easy to understand as an alternative. It was not selected because credentials would sit in a third-party vault rather than a local gateway.
- What worked
- The quickstart made the one-URL, managed-OAuth, native-toolkit model obvious without needing an account.
- What got in the way
- The hosted vault model did not match the need to keep account logins local and out of another SaaS, so the product was a poor fit even though the docs were readable.