P0 MCP Gateway
The P0 MCP Gateway is a self-hosted runtime enforcement layer for agentic authorization. It sits in the data path between AI agents (MCP clients) and upstream MCP servers: it proxies MCP tool calls, verifies the identity token binding user + agent on every call, evaluates least-privilege policy, launches isolated per-session containers with short-lived just-in-time credentials for upstream servers that need them, and ships audit activity to a SIEM. It syncs MCP server definitions and tool catalogs from, and drives the request/approval/grant/revoke lifecycle through, the P0 Controller (SaaS). A companion self-hosted P0 OAuth server federates with the customer IdP (Okta, Entra ID, Google) and brokers downstream credentials.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Documentation
Documentation link · transport http
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.
Work with this as data
Every MCP server here is available over the APIs.io API and to AI agents over MCP.