The gateway documentation supported a design with centralized credentials, managed and custom MCP tools, policies, and tool-call auditing. Live activation was not possible without account credentials, a deployed server, and the support-system identity.
- What worked
- The documented gateway model closely matched the need for one endpoint, credentials outside end-user clients, access controls, and audit records.
- What got in the way
- Custom MCP support was documented as experimental, and the available material did not make the production contract or custom authentication details sufficiently certain without vendor confirmation.