> For the complete documentation index, see [llms.txt](https://docs.p0.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.p0.dev/agentic-access.md).

# Agentic access

- [AI gateway](https://docs.p0.dev/agentic-access/agentic-gateway.md): Configure the P0 AI Gateway and the upstream MCP servers and agents it fronts, so P0-managed AI agents can reach them under runtime authorization policy.
- [Gateway](https://docs.p0.dev/agentic-access/agentic-gateway/gateway.md): What registering a P0 AI Gateway with P0 establishes, and how to register a gateway you deployed yourself.
- [Deploying the gateway](https://docs.p0.dev/agentic-access/agentic-gateway/gateway/deploy.md): Deploy the self-hosted P0 AI Gateway and Auth Server from the P0 console, with the batteries-included Helm chart, or with the basic Helm chart.
- [Install from the P0 console](https://docs.p0.dev/agentic-access/agentic-gateway/gateway/deploy/install-from-the-p0-console.md): Deploy the gateway with the Terraform the P0 console generates, and register it with P0 in the same pass.
- [Install the batteries-included Helm chart](https://docs.p0.dev/agentic-access/agentic-gateway/gateway/deploy/install-the-batteries-included-chart.md): Deploy the p0security/ai-gateway-stack chart with helm instead of the Terraform the P0 console generates, then register the gateway with P0.
- [Upgrade the gateway](https://docs.p0.dev/agentic-access/agentic-gateway/gateway/deploy/upgrade-the-gateway.md): Move a running gateway to a newer chart version with Terraform or Helm, and confirm it still serves.
- [Helm chart values reference](https://docs.p0.dev/agentic-access/agentic-gateway/gateway/deploy/chart-values.md): Reference for the values you can set when deploying the P0 AI Gateway with its Helm charts.
- [Batteries-included chart values](https://docs.p0.dev/agentic-access/agentic-gateway/gateway/deploy/chart-values/batteries-included-chart.md): Every value in the p0security/ai-gateway-stack Helm chart, with whether it is required and its default.
- [Gateway chart values](https://docs.p0.dev/agentic-access/agentic-gateway/gateway/deploy/chart-values/gateway-chart.md): Every value in the p0security/ai-gateway Helm chart, with whether it is required and its default.
- [MCP server](https://docs.p0.dev/agentic-access/agentic-gateway/mcp-server.md): Configure upstream MCP servers behind the P0 AI Gateway to make them available to P0-managed agents under policy.
- [AWS](https://docs.p0.dev/agentic-access/agentic-gateway/mcp-server/aws.md): Install the predefined AWS MCP server behind the P0 AI Gateway, giving agents policy-scoped, credential-free access to the AWS CLI.
- [Datadog](https://docs.p0.dev/agentic-access/agentic-gateway/mcp-server/datadog.md): Install the Datadog agentic integration and its MCP server so agents behind the P0 AI Gateway can request scoped access to your Datadog organization.
- [PostgreSQL on AWS RDS](https://docs.p0.dev/agentic-access/agentic-gateway/mcp-server/rds-postgres.md): Install the predefined PostgreSQL on AWS RDS MCP server behind the P0 AI Gateway, so agents can query RDS PostgreSQL databases with a just-in-time database role.
- [GCP](https://docs.p0.dev/agentic-access/agentic-gateway/mcp-server/gcp.md): Install the predefined GCP MCP servers behind the P0 AI Gateway, giving agents policy-scoped, credential-free access to Google Cloud APIs.
- [Compute Engine](https://docs.p0.dev/agentic-access/agentic-gateway/mcp-server/gcp/compute.md): Install the predefined Compute Engine MCP server behind the P0 AI Gateway, giving agents policy-scoped, credential-free access to the Google Cloud Compute Engine API.
- [Cloud Storage](https://docs.p0.dev/agentic-access/agentic-gateway/mcp-server/gcp/storage.md): Install the predefined Cloud Storage MCP server behind the P0 AI Gateway, giving agents policy-scoped, credential-free access to the Google Cloud Storage API.
- [BigQuery](https://docs.p0.dev/agentic-access/agentic-gateway/mcp-server/gcp/bigquery.md): Install the predefined BigQuery MCP server behind the P0 AI Gateway, giving agents policy-scoped, credential-free access to the Google Cloud BigQuery API.
- [Cloud Monitoring](https://docs.p0.dev/agentic-access/agentic-gateway/mcp-server/gcp/monitoring.md): Install the predefined Cloud Monitoring MCP server behind the P0 AI Gateway, giving agents policy-scoped, credential-free access to the Google Cloud Monitoring API.
- [IAM](https://docs.p0.dev/agentic-access/agentic-gateway/mcp-server/gcp/iam.md): Install the predefined IAM MCP server behind the P0 AI Gateway, giving agents policy-scoped, credential-free access to the Google Cloud IAM API.
- [GitHub](https://docs.p0.dev/agentic-access/agentic-gateway/mcp-server/github.md): Install the GitHub App integration and its MCP server so agents behind the P0 AI Gateway can request scoped access to your GitHub repositories.
- [Google Drive](https://docs.p0.dev/agentic-access/agentic-gateway/mcp-server/google-drive.md): Install the Google Drive integration and its MCP server so agents behind the P0 AI Gateway can request access to folders and files in your Google shared drives.
- [Jira](https://docs.p0.dev/agentic-access/agentic-gateway/mcp-server/jira.md): Install the Jira agent access integration and its MCP server so agents behind the P0 AI Gateway can request Jira tools in one space at a time.
- [PagerDuty](https://docs.p0.dev/agentic-access/agentic-gateway/mcp-server/pagerduty.md): Install the PagerDuty integration and its MCP server so agents behind the P0 AI Gateway can request scoped access to your PagerDuty account.
- [Salesforce](https://docs.p0.dev/agentic-access/agentic-gateway/mcp-server/salesforce.md): Install the Salesforce (AI) integration and its MCP server so agents behind the P0 AI Gateway can request Salesforce permission sets.
- [ServiceNow](https://docs.p0.dev/agentic-access/agentic-gateway/mcp-server/servicenow.md): Install the ServiceNow (AI) integration and its MCP server so agents behind the P0 AI Gateway can request ServiceNow roles.
- [SaaS](https://docs.p0.dev/agentic-access/agentic-gateway/mcp-server/saas.md): Install P0's predefined SaaS MCP servers behind the P0 AI Gateway, giving agents OAuth-authenticated, policy-scoped access to each SaaS tool.
- [Custom](https://docs.p0.dev/agentic-access/agentic-gateway/mcp-server/custom.md): Define and configure a custom MCP server behind the P0 AI Gateway when P0 does not ship a predefined server for it.
- [A2A bridge](https://docs.p0.dev/agentic-access/agentic-gateway/a2a-bridge.md): Configure an A2A bridge behind the P0 AI Gateway so P0-managed agents reach upstream agents under runtime authorization policy.
- [Log provider](https://docs.p0.dev/agentic-access/agentic-gateway/log-provider.md): Point P0 at the logs that hold your gateway's MCP and A2A activity, so the P0 console can show every tool call the gateway handled.
- [VictoriaLogs](https://docs.p0.dev/agentic-access/agentic-gateway/log-provider/victorialogs.md): Read gateway activity from the VictoriaLogs instance the batteries-included chart deploys in your cluster.
- [Google Cloud Logging](https://docs.p0.dev/agentic-access/agentic-gateway/log-provider/gcp-cloud-logging.md): Export gateway activity to Google Cloud Logging and let P0 read it from your project.
- [Identity provider](https://docs.p0.dev/agentic-access/identity-provider.md): Enroll an identity provider with the P0 AI Gateway so its JWT-authenticated agents are trusted to access the gateway.
- [Credential sources](https://docs.p0.dev/agentic-access/credential-sources.md): Install the credential sources the P0 AI Gateway needs to create short-lived identities in your cloud accounts for MCP servers.
- [AWS OIDC](https://docs.p0.dev/agentic-access/credential-sources/aws-oidc.md): Install the AWS OIDC federation component so P0 can grant and revoke AWS access for OIDC-authenticated agents running through the P0 AI Gateway.
- [GCP Workload Identity Federation](https://docs.p0.dev/agentic-access/credential-sources/gcp-wif.md): Install the GCP Workload Identity Federation component so P0 can grant and revoke Google Cloud access for OIDC-authenticated agents running through the P0 AI Gateway.
- [GCP Service Account Creator](https://docs.p0.dev/agentic-access/credential-sources/gcp-service-account-creator.md): Install the GCP Service Account Creator so P0 can create a short-lived Google Cloud service account for each agent grant made through the P0 AI Gateway.
- [Using the P0 AI Gateway](https://docs.p0.dev/agentic-access/using-the-gateway.md): See registered clients, configured MCP servers, and call activity in Agentic Access, and connect your own agents to a configured gateway.
- [Connect an MCP client](https://docs.p0.dev/agentic-access/using-the-gateway/connect-an-mcp-client.md): Register an MCP client and connect it to an MCP server configured behind the P0 AI Gateway.
- [Agentic client registration API](https://docs.p0.dev/agentic-access/using-the-gateway/connect-an-mcp-client/client-registration-api.md): Register, list, and update the MCP clients that authenticate to a server behind the P0 AI Gateway.
- [JWT-SVID](https://docs.p0.dev/agentic-access/using-the-gateway/spiffe-svid.md): Enroll a SPIFFE identity provider with P0, and authenticate an unattended workload to the P0 AI Gateway with an existing JWT-SVID from Python.
- [OAuth servers from a headless agent](https://docs.p0.dev/agentic-access/using-the-gateway/headless-oauth-credentials.md): Register an OAuth credential for a federated client, so a headless agent can call an OAuth MCP server behind the P0 AI Gateway with no one signed in.
- [Requesting access](https://docs.p0.dev/agentic-access/using-the-gateway/requesting-access.md): How an AI agent requests, checks, uses, and relinquishes just-in-time access to the MCP servers and agents behind the P0 AI Gateway.
- [Event log](https://docs.p0.dev/agentic-access/using-the-gateway/event-log.md): Review the MCP tool calls and A2A agent calls the P0 AI Gateway observed, filter and export them, and open the access request behind each one.
- [Use MCP servers with Claude Code](https://docs.p0.dev/agentic-access/using-the-gateway/using-mcp-servers.md): Connect your Claude Code client to the MCP servers behind the P0 AI Gateway, so your agent's tool calls are authenticated and governed by policy.