MCP server
Configure upstream MCP servers behind the P0 AI Gateway to make them available to P0-managed agents under policy.
The MCP server component configures an upstream MCP server behind the P0 AI Gateway. Once an MCP server is configured, it is available to agents through the gateway. Every tool call is authenticated and checked against policy before reaching the upstream server.
Prerequisites
A registered Gateway component, and the gateway deployed in your environment. See Deploying the P0 AI Gateway.
Server definitions
When you add a server, you set its Definition: a server predefined by P0, or a Custom server you define yourself. For the full list of predefined servers, see the left navigation.
Authorization models
When you set up a server, you choose an Access control method. This decides what calls an agent can make in the upstream system:
Native: The upstream system enforces authorization using its native controls. The gateway passes each call through, and the upstream system's own permissions allow or deny it. Choose this when the system has a deep integration with P0 and the system uses native or WIF credentials.
Tool (Preview): The gateway decides, by tool name. An agent asks for the specific tools it needs. The gateway allows those and blocks every other tool. Choose this for systems without deep integration to P0, or systems that rely on user OAuth credentials.
Annotation (Preview): The gateway decides, by what each tool does. Tools are grouped as read-only, write (non-destructive), or destructive. An agent asks for one or more groups, and the gateway allows any tool in a granted group. A tool with no label is treated as destructive.
To set the access control method when you configure a server, see Custom MCP server.
Add an MCP server
Every MCP server starts with the same steps. The final configuration screen differs by server. When you reach it, continue to the page for the predefined server you chose in the left navigation, or to Custom MCP server.
Navigate to Integrations on p0.app and select Agentic gateway, then choose the MCP server component.
Click Add server.
Enter the server details, then click Next:
Server identifier: a name for this server within P0.
Gateway: the registered gateway that hosts this server.
Set the Credential source, which selects how the gateway authenticates to the upstream:
OAuth
Set the Definition, which selects what the server actually exposes:
P0: a predefined server. Follow its page in the left navigation.
Custom: a server you define yourself. See Custom MCP server.
Configure with Terraform
Use the P0 Terraform provider to configure an MCP server outside the console. The p0_agentic_server resource takes the hosting gateway's id, the server's own id, a definition (p0 or custom), and a credential source (aws, gcp, or oauth) — the same choices as the console fields described earlier.
Related docs
Connect an MCP client to the P0 AI Gateway: Learn how to register a client and connect an agent to an MCP server through the gateway.
Use MCP servers with Claude Code: Connect Claude Code to MCP servers managed by P0.
Last updated