Import swagger into PipMCP
Preview a reviewed API definition, upload it with one scoped account key, then choose which tools to publish and connect in your workspace.
Preview before upload
The default command previews a bundled synthetic request offline. It does not run a local provider compiler or execute an API.
npm ci --ignore-scripts
npm test
npm start
node example.mjs ./your-api.json --name "My private API" --execute --confirm-importUse JSON for OpenAPI3, Swagger2 and Postman v2. GraphQL accepts supported SDL or introspection JSON; use its real endpoint when required. Remove credential values and customer examples from the input.
Keep the same PipMCP key
PIPMCP_API_KEY needs integrations:read and integrations:write for duplicate-check and import, plus connectors:read and connectors:call for subsequent discovery/calls. Existing keys do not receive scopes automatically.
Import creates a private integration draft. Review and publish selected tools in PipMCP, configure an authorized connection, then set the explicit PIPMCP_INTEGRATION_ID. A draft has no callable inventory.
npm run doctor
# Uses custom-api with the explicit published integration ID
npm run serverThe custom-api inventory and calls remain scoped to your selected published integration and current key. No provider credentials or private execution mappings are bundled in this client.
Evidence and version
Client fixtures test the request and transport contract. A preview, import receipt or discovered tool does not establish successful provider execution. Historical local compiler releases have their own behavior and original license.