Connect an MCP client to P2HS
Use the remote endpoint below, complete the owner-approved OAuth flow and begin with the smallest scope your workflow needs.
1. Use the remote endpoint
MCP server URL
https://mcp.p2hs.com/mcp
2. Authorize with OAuth
The gateway supports authorization code flow with S256 PKCE and dynamic public-client registration. Your MCP client should follow the protected-resource metadata, open the consent flow, and store the returned access and refresh tokens securely.
Access is represented by a scoped grant. Workspace service accounts can be limited to selected projects, given an expiry and revoked by the workspace owner.
3. Start with read access
projects.read
List projects, inspect a project, review builds and estimate a build.
projects.create
Create a project when the grant explicitly includes creation.
4. Make safe mutations
Mutation tools require a request key. If a client retries, send the same arguments with the same key. Keys are scoped to the grant, and durable operations can be polled with get_operation.
Billing reminder
Credit purchases can charge real money. Use the current catalog price, respect the workspace owner’s approval and spending cap, and poll the resulting operation instead of creating a replacement request.