MCP Gateway

The MCP Gateway exposes approved Answerplane capabilities to agents through the Model Context Protocol.

Governed tools

Tools are generated from enabled source objects and organization context. They inherit catalog, access, plan, query-bound, and tenant controls. Do not treat MCP as a bypass around source governance.

Connect a client

Create a scoped credential, register the gateway URL in the MCP client, and test discovery with a non-sensitive organization. Consult MCP Gateway in the app and the API reference for the current transport and authentication contract.

External MCP servers

Approve external servers based on their data access, actions, authentication, and ownership. Read-only tools and tools with side effects should be separated clearly.

Production checklist

• restrict available tools to the workload
• keep credentials outside prompts and client logs
• test tenant isolation
• require approval for consequential actions
• inspect gateway and organization logs
• revoke unused clients