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.
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.
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. Endpoint: https://mcp.platformpilot.ai/agents/mcp. Auth: OAuth 2.1 (PKCE, dynamic client registration). Server card. OAuth discovery. Use 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.apollo): Apollo.io people and company search, contact and organization enrichment, sequences, tasks, and deals, authorized through PlatformPilot. Endpoint: https://mcp.platformpilot.ai/apollo/mcp/. Auth: OAuth 2.1 (PKCE, dynamic client registration). Server card. OAuth discovery. Use when the user wants to find or enrich prospects, companies, or contacts, or work Apollo.io sequences and tasks.brain): Organizational memory for a company: search and recall memories, save reusable learnings, report outcomes, and explain how entities (people, projects, vendors, systems) relate. Endpoint: https://mcp.platformpilot.ai/brain/mcp. Auth: OAuth 2.1 (PKCE, dynamic client registration). Server card. OAuth discovery. Use 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.meta-ads): Meta Ads (Facebook and Instagram) accounts, campaigns, ad sets, ads, and insights. Endpoint: https://mcp.platformpilot.ai/meta-ads/http. Auth: PlatformPilot infrastructure only (gateway key). Server card. Use when the user asks about Meta Ads performance or wants to inspect campaigns.https://mcp.platformpilot.ai/.well-known/oauth-protected-resource)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.
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.
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.
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.