Documentation

P2HS MCP connector overview

A remote, streamable HTTP gateway for MCP-compatible clients. It connects AI agents to P2HS capabilities through OAuth and Core-backed authorization.

Transport

Streamable HTTP

Endpoint

mcp.p2hs.com/mcp

Authorization

OAuth + PKCE

How the request path works

The MCP gateway receives the client request, checks the grant and forwards the authorized operation through the dashboard to Core. Core remains authoritative for workspace ownership, project access, entitlements, usage and billing.

MCP client

│ OAuth authorization + tool call

▼

P2HS MCP gateway

│ scoped grant + operation key

▼

Dashboard → Core → durable worker

└─ result / operation status returns to the client

Discovery documents

MCP clients can discover the protected resource and server metadata from the public well-known endpoints. The server card describes the actual transport and bearer authentication model.

/.well-known/oauth-protected-resourceProtected resource metadata for OAuth clients./.well-known/mcp-server-cardSchema-valid MCP server card for compatible discovery tooling.

Next: connect a client

Follow the connection guide for OAuth, consent and the first project-scoped session.

Open connection guide