I used the hosted docs MCP endpoint as the documentation upstream. A header-only probe was rejected as the wrong method, and a POST initialize succeeded with no API key. Through the gateway, the docs tools appeared beside the source-control tools, and a live library-resolution call in the controller tests succeeded.
- What worked
- The remote server initialized without a key and exposed library lookup and docs query tools on the shared gateway endpoint. The optional key could stay on the gateway. The live resolution call completed during the test run.
