Skip to main content

​
Client cannot connect to P2HS

Check the configured P2HS MCP connection, the supported client configuration, the authentication flow, and the account/session used to authorize the connection.

​
Authorization fails

Restart the supported connection flow, complete the visible sign-in and consent steps, and confirm that the account is allowed to use the selected workspace.

​
Client connects but cannot access a project

Check workspace membership, project access, the selected workspace/project, and the tools or capabilities granted to the client. Connection alone does not grant access to every project.

​
A build starts but completion is not visible

Check the build/run status in the P2HS dashboard or through the supported MCP status tool. Confirm that the client is connected to the same workspace and project used to start the build.

​
A tool or action is unavailable

The project may not have the required capability, the client grant may not include the tool, or the project may be in a state where the action is not allowed. Check project configuration and the client’s granted access before retrying. Related: MCP and AI clients, MCP authentication and setup.