Connect with one PipMCP account key
1. Select the account and scopes
Create PIPMCP_API_KEY with connectors:read and connectors:call as required. Provider account credentials and authorization belong in the PipMCP connection flow.
2. Discover actual tools
Run the published client doctor. Select an integration and connection explicitly when the account has several choices. Unavailable connector, missing connection and missing scope are separate conditions.
3. Review the intended call
Use the returned schema and the selected tool. Hosted confirmation remains authoritative; the bridge never creates approval.
4. Inspect the receipt
Preserve the logical request key. A subsequent explicit call can resume its pending confirmation using the same intent after dashboard approval. Uncertain writes remain held; a new key is not an automatic retry.
Import a private API
Use integrations:read and integrations:write on that same key for reviewed upload. Inspect and publish chosen tools in your workspace, configure a connection and select the published custom-api integration explicitly. A draft import has no callable inventory.