Import a GraphQL schema into private PipMCP
Preview and explicitly upload a reviewed API definition with one PipMCP key. Review and publish selected tools in the workspace, configure a connection and use explicit custom-api integration selection.
Use the project that fits your workflow
Use the repository release matching the documented SDK/bridge version; existing repository publication does not prove every newer asset is released.
Access and approval
- PIPMCP_API_KEY with integrations:read/integrations:write for import
- Same key with connectors:read/connectors:call for published tools
- Explicit published PIPMCP_INTEGRATION_ID for custom-api
Input upload requires --execute --confirm-import. Import, workspace publication, provider connection and hosted action confirmation are separate steps.
Start from the matching SDK release
Node.js
npm start
npm run doctorResource examples assume an initialized SDK client with your workspace key. The fixture workflow executes synthetic backend responses; it makes no provider calls. Live execution requires the documented account access and checkpoint/review options.
Capability and evidence
Contract-tested client code; version-specific release required. Not established by task discovery. A published repository, a discovered tool and a successful provider result are different facts.