# PlatformPilot MCP Gateway > Hosted Model Context Protocol (MCP) servers for PlatformPilot. Point an MCP client at a server endpoint below. OAuth-aware servers authenticate with OAuth 2.1 (PKCE and dynamic client registration) and need no API key. The gateway routes MCP traffic to the backend that serves each server, applies rate limits, and hosts the OAuth discovery documents and authorization endpoints for every server. ## When to use - Use this gateway when a user wants PlatformPilot capabilities from an MCP client such as Claude, Cursor, or ChatGPT: the company's memory, its investigation and scoring agents, or the third-party tools PlatformPilot hosts. - Use PlatformPilot Agents when the user wants PlatformPilot to investigate an incident or signal, score or rank candidates against an explicit rubric, or run a PlatformPilot chat turn from another client. - Use Apollo.io via PlatformPilot when the user wants to find or enrich prospects, companies, or contacts, or work Apollo.io sequences and tasks. - Use PlatformPilot Brain when the user asks what the company knows, learned, or decided; wants to save a learning or an outcome; or asks how two entities connect or what an entity affects. - Use Meta Ads via PlatformPilot when the user asks about Meta Ads performance or wants to inspect campaigns. ## MCP servers - [PlatformPilot Agents](https://mcp.platformpilot.ai/agents/.well-known/mcp/server-card.json) (`agents`): PlatformPilot's agents as MCP tools: hypothetico-deductive investigation of events and alerts, defeasible-reasoning scoring of candidates against a rubric, and the PlatformPilot chat assistant. MCP endpoint: https://mcp.platformpilot.ai/agents/mcp. Auth: OAuth 2.1 (PKCE, dynamic client registration). Discovery: https://mcp.platformpilot.ai/agents/.well-known/oauth-protected-resource - [Apollo.io via PlatformPilot](https://mcp.platformpilot.ai/apollo/.well-known/mcp/server-card.json) (`apollo`): Apollo.io people and company search, contact and organization enrichment, sequences, tasks, and deals, authorized through PlatformPilot. MCP endpoint: https://mcp.platformpilot.ai/apollo/mcp/. Auth: OAuth 2.1 (PKCE, dynamic client registration). Discovery: https://mcp.platformpilot.ai/apollo/.well-known/oauth-protected-resource - [PlatformPilot Brain](https://mcp.platformpilot.ai/brain/.well-known/mcp/server-card.json) (`brain`): Organizational memory for a company: search and recall memories, save reusable learnings, report outcomes, and explain how entities (people, projects, vendors, systems) relate. MCP endpoint: https://mcp.platformpilot.ai/brain/mcp. Auth: OAuth 2.1 (PKCE, dynamic client registration). Discovery: https://mcp.platformpilot.ai/brain/.well-known/oauth-protected-resource - [Meta Ads via PlatformPilot](https://mcp.platformpilot.ai/meta-ads/.well-known/mcp/server-card.json) (`meta-ads`): Meta Ads (Facebook and Instagram) accounts, campaigns, ad sets, ads, and insights. MCP endpoint: https://mcp.platformpilot.ai/meta-ads/http. Auth: PlatformPilot infrastructure only (gateway key). ## How to connect 1. Send any request to the MCP endpoint without credentials. The 401 carries a WWW-Authenticate header naming the protected-resource metadata URL. 2. Follow [auth.md](https://mcp.platformpilot.ai/auth.md): discover the authorization server, register a client (RFC 7591), run the authorization code flow with PKCE, and send the access token as a Bearer header. 3. The [agent skill](https://mcp.platformpilot.ai/.well-known/agent-skills/platformpilot-mcp/SKILL.md) walks an agent through the same steps. ## OAuth discovery - Root: https://mcp.platformpilot.ai/.well-known/oauth-protected-resource - Per server: https://mcp.platformpilot.ai//.well-known/oauth-protected-resource and https://mcp.platformpilot.ai//.well-known/oauth-authorization-server - Endpoints: https://mcp.platformpilot.ai//oauth/authorize, https://mcp.platformpilot.ai//oauth/token, https://mcp.platformpilot.ai//oauth/register (RFC 7591 dynamic client registration) ## Catalogs - [AI catalog](https://mcp.platformpilot.ai/.well-known/ai-catalog.json) (Agentic Resource Discovery) - [MCP server card](https://mcp.platformpilot.ai/.well-known/mcp/server-card.json) (default server; per server at https://mcp.platformpilot.ai//.well-known/mcp/server-card.json) - [API catalog](https://mcp.platformpilot.ai/.well-known/api-catalog) (RFC 9727) - [Agent skills index](https://mcp.platformpilot.ai/.well-known/agent-skills/index.json) ## FAQ ### How do I connect an MCP client? Add the server's MCP endpoint as a Streamable HTTP server. The first request returns 401 with a WWW-Authenticate header; the client discovers the authorization server, registers itself, and opens the sign-in page. After consent, every request carries a Bearer token. ### Do I need an API key? No. OAuth-aware servers use OAuth 2.1 with PKCE and dynamic client registration against a PlatformPilot account. Servers marked gateway-key only are PlatformPilot infrastructure and have no self-service path. ### What can an agent read without signing in? The discovery documents on this host and, for servers that opened their handshake, the tool list (initialize and tools/list). Every tool call needs a token. ### Where does the data live? On PlatformPilot's backends, scoped to the signed-in user's organization. The gateway routes and rate-limits; it stores no user data and no credentials. ## References - [Developer portal](https://platformpilot.ai/developers) (API reference, authentication, examples) - [OpenAPI document](https://mcp.platformpilot.ai/openapi.json) - [Interactive API docs](https://mcp.platformpilot.ai/docs) - [PlatformPilot](https://platformpilot.ai): [developers](https://platformpilot.ai/developers), [pricing](https://platformpilot.ai/#explore-plans), [about](https://platformpilot.ai/about), [contact](https://platformpilot.ai/contact), [privacy](https://platformpilot.ai/privacy-policy)