Skip to main content

Connecting Pinpoint to Claude via MCP

Written by Emilia Carvell

This guide walks you through connecting your Pinpoint account to Claude so you can ask Claude questions about your Pinpoint data directly in chat.

Step 1: Create a Pinpoint API Key


You will need an API key from Pinpoint so Claude can securely access your account.

  1. Log in to your Pinpoint account.

  2. Click Settings in the left-hand sidebar.

  3. Select API & Webhooks.

  4. In the top-right of that page, make sure the Pinpoint API toggle is switched on.

  5. Click "create new" in the top right hand corner to create an API Key

Important: create the key with read-only permission. This prevents claude from accidentally changing or deleting any data in your account.

Step 2: Find Your Pinpoint Subdomain


Your subdomain is the part of your Pinpoint URL before .pinpointhq.com. For example, if you log in at acme.pinpointhq.com, your subdomain is acme


Step 3: Connect Pinpoint to Claude

  1. Open Claude at claude.ai.

  2. Click into "customize" in the left hand navigation bar and go to the "connectors" tab

  3. Find Pinpoint in the list of available connectors and click Connect.

  4. When prompted, enter:

  5. Save or confirm the connection.

If you do not see a Pinpoint connector in the list, you can connect manually. In Claude’s MCP settings, add a new server with the URL https://developers.pinpointhq.com/mcp and the headers X-API-KEY (your API key) and X-Original-Host (your subdomain URL).


Step 4: Test the Connection

Once connected, start a new chat in Claude and try asking something like:

  • “Which countries do we get the most applications from?”

  • “Show me a summary of our last 50 candidates.”

  • “How do I create a new application in Pinpoint?”

Claude should now be able to answer using live data from your Pinpoint account.

Keep your API key private. Do not share it in emails, documents, or anywhere publicly accessible. If you believe your key has been exposed, go back to Settings > API & Webhooks in Pinpoint, delete the compromised key immediately, and create a new one.

Did this answer your question?