What every MCP client needs
A published Gateway surface gives you two client-facing values: the MCP URL and a Gateway token.
- The MCP URL identifies the published OpenAPI integration or database scope.
- The Gateway token authenticates the client.
- The upstream API key or database connection string stays server-side.
- A tools/list request confirms that the surface is reachable and published.
Client configuration shape
Most HTTP MCP client configuration uses the same basic shape.
Use the Gateway MCP URL as the server URL and send the Gateway token in the Authorization header. Claude, Cursor, VS Code, and other MCP-compatible clients may present this configuration differently, but the same two values are required.
Use Gateway Chat for fast validation
Gateway Chat is useful before configuring an external client.
Chat can discover owner-scoped OpenAPI and database surfaces that are active and callable. It helps verify whether tool descriptions, scope design, and database guardrails are understandable to an AI workflow.
Common questions
Do clients connect to the upstream API directly?
No. Clients connect to the Gateway MCP endpoint. The Gateway routes validated calls to the upstream API or database executor.
What should I test first?
Start with tools/list. It confirms the MCP URL, token, publication state, and source resolver are working.
Can Gateway Chat replace external clients?
Gateway Chat is useful for testing and demos. Production workflows can still use external MCP clients with the same Gateway-published surfaces.