🔌Using the P0 AI Gateway

See registered clients, configured MCP servers, and call activity in Agentic Access, and connect your own agents to a configured gateway.

The Agentic Access page is where you see what's connected to your gateway: registered clients, the MCP servers they can reach, and their MCP and A2A call activity. It appears once a gateway is registered, to Owners, Security Reviewers, Assessment Users, and Assessment Viewers. Configuring the gateway itself, and the MCP servers and A2A bridges behind it, is covered by the component pages.

Agentic Access

Clients

Lists every MCP client and agent identity registered to connect through the gateway: its provider (a federated identity, or a client platform like Claude Code), its client ID, and who registered it and when. Select a row for more detail. Some roles can also register a client directly from this tab. See Connect an MCP client.

MCP servers

Lists the MCP servers this gateway exposes to registered clients, with each one's type and endpoint. This tab is read-only — configure what it shows on the MCP server component page.

Event log

Lists the MCP tool calls and A2A agent calls this tenant's gateways observed. See Event log for filtering, export, and the full API reference.

Connect your own agents

• Connect an MCP client: register an MCP client and connect it to a server behind the gateway, with a Python example. The client registration API scripts the registration step.

• JWT-SVID: authenticate an unattended workload to the gateway with a SPIFFE JWT-SVID instead of an interactive sign-in.

• Requesting access: how an agent requests, checks, uses, and relinquishes just-in-time access to the servers and agents behind the gateway.

• Use MCP servers with Claude Code: connect a Claude Code client to the servers behind the gateway with the P0 CLI.