Connect Pexi MCP to Claude

Custom connectors require a paid Claude plan (Pro, Max, Team, or Enterprise). On Team/Enterprise plans, an Owner must add the connector first — members can then individually authenticate via Settings → Connectors.

Step 1: Open Connector Settings

Open Claude.ai in your browser or the Claude app. Click your profile icon in the bottom-left corner and select Settings. In the left sidebar, click on Connectors. This is where all your connected and available integrations are managed.

Step 2: Add Pexi as a Custom Connector

At the bottom of the Connectors list, click "Add custom connector". You'll see a form with the following fields:

• Name: Enter Pexi
• MCP Server URL: Enter https://dash.pexi.nl/mcp/banner

Optionally, click "Advanced settings" to specify an OAuth Client ID and OAuth Client Secret. In most cases you can leave these empty — Pexi's MCP server handles the OAuth configuration automatically through dynamic client registration.

Click "Add" to save the connector. Pexi will now appear in your Connectors list with a "Connect" button.

Step 3: Start the OAuth Authentication Flow

Click "Connect" next to the Pexi entry. This initiates the OAuth 2.0 authorization flow:

1. Claude generates an authorization request and redirects your browser to Pexi's login page at dash.pexi.nl.
2. Your browser opens the Pexi authentication screen. Claude never sees or stores your Pexi password — the entire login happens directly between your browser and Pexi's servers.

If your organization uses DPG OneLogin, you'll see an option to sign in with your DPG account instead of a standard username/password form.

Step 4: Review and Approve Permissions

After logging in, Pexi will display a consent screen showing which permissions Claude is requesting. This typically includes read access to your campaigns, banners, and performance data, as well as the ability to manage banner files.

Review the requested scopes carefully. If you're comfortable, click "Authorize" or "Allow". This tells Pexi to issue an OAuth access token (and a refresh token) to Claude.

• The access token is what Claude uses to make API calls to Pexi on your behalf. It has a limited lifespan.
• The refresh token allows Claude to silently request a new access token when the current one expires, so you don't have to log in again.

Both tokens are stored encrypted by Anthropic. You can revoke them at any time.

Step 5: Confirm the Connection

After you authorize, Pexi redirects your browser back to Claude's OAuth callback URL (https://claude.ai/api/mcp/auth_callback). Claude receives the tokens and completes the handshake.

The Pexi connector in your Settings should now show as Connected. If it still shows "Disconnected", try refreshing the page or restarting the Claude app.

Step 6: Verify in a Conversation

Open a new conversation in Claude (existing conversations may not detect newly added connectors). Try a simple prompt such as:

"Search for my banners in Pexi"

If Claude responds with actual data from your Pexi account, everything is working. You can now use any of the available Pexi MCP tools through natural language.

Disconnecting or Re-authenticating

To disconnect Pexi, go to Settings → Connectors, find the Pexi entry, and click "Disconnect". This revokes Claude's access tokens.

If your Pexi password changes or your token becomes invalid, simply disconnect and reconnect the connector to trigger a fresh OAuth flow.