Skip to content
PipMCP

Connect credentials

Add a connection so PipMCP can call your API, test it, and understand how secrets are stored.

A connection holds everything PipMCP needs to call one API on behalf of an agent: the base URL, the auth type and the secrets. An integration can have several connections, for example production and sandbox, and each MCP endpoint uses one connection per integration.

Create a connection

  1. Open Connections and choose Connect an API, or start from the integration page.
  2. Pick the integration. PipMCP pre-selects the auth type found in the spec.
  3. Choose the environment: Production, Sandbox or Custom (with your own base URL).
  4. Fill in the fields for the auth type and save.
  5. Choose Test connection.

For the supported auth types and their fields, see Authentication.

Testing a connection

Test connection calls the first read-only (GET) operation of the integration that has no required parameters and reports the HTTP status. If there is no such operation, the test tells you so; call a tool from the tool page or from an AI client to verify instead.

The result, the last successful call and the last error are shown on the connection page.

How secrets are stored

  • Every secret value is envelope-encrypted: it is encrypted with its own random data key, and that key is wrapped by a versioned master key.
  • Secrets are decrypted only immediately before an upstream request, and only in memory.
  • Once saved, a secret is never shown again, in the dashboard or through the API. To change it, enter a new value.
  • Secrets are never written to logs; request logs pass through a redactor first (see Logs).
  • Secrets are never sent to AI models, and never returned to AI clients.

Restricting hosts

A connection can carry an allowed hosts list. When set, PipMCP refuses to send requests (including redirects) to any host not on the list. This is useful when a spec lists several servers and you want to be sure credentials only go to one of them.

Independently of that list, PipMCP never forwards credentials to a different host after a redirect, and never calls private or reserved network addresses.

OAuth 2.0 connections

For the authorization code flow, register this redirect URL with your OAuth provider:

https://pipmcp.com/app/oauth/callback

After saving the connection, choose Connect account to sign in with the provider. Access tokens are refreshed automatically before they expire. If the refresh fails, tool calls return TOKEN_EXPIRED until someone reconnects the account.

OAuth connections are available on paid plans.

Deleting a connection

Deleting a connection deletes its encrypted secrets. MCP endpoints that used it stop serving that integration's tools until you choose another connection.