How to connect a Pipedrive MCP with Claude Code (5 steps)

Developers building RevOps automations or sales tooling need live Pipedrive data to write logic against: which deals crossed a threshold, which contacts haven't been touched in two weeks, which stages are bottlenecking, and more.

Getting that data currently means leaving the terminal, pulling a filter in Pipedrive's UI, and copying results back manually.

To help your developers query and update Pipedrive records directly from a coding session, we'll show you how to connect Pipedrive with Merge Agent Handler's Pipedrive MCP server.

How it works

Merge Agent Handler acts as a secure bridge between Claude Code and the Pipedrive API. When you configure a Tool Pack and Registered User, Merge generates a unique MCP URL that Claude Code accesses via HTTP. Authentication uses an API key generated in Merge Agent Handler. Claude Code never touches your Pipedrive credentials directly.

Here's the connection config before you substitute your specific values:

claude mcp add 
--transport http --header "Authorization: Bearer YOUR_API_KEY"
agent-handler
"https://ah-api.merge.dev/api/v1/tool-packs/YOUR_TOOL_PACK_ID/registered-users/YOUR_REGISTERED_USER_ID/mcp"

Claude Code sends requests to that MCP URL, and Merge handles authentication and API calls to Pipedrive on the backend. You don't manage Pipedrive API tokens locally or handle credential rotation. Merge handles both.

Prerequisites

Before getting started, you'll need the following:

• A Merge Agent Handler account
• Claude Code installed (run claude --version to confirm)
• A Pipedrive account with API access

Related: How to integrate with a Salesforce MCP via Claude Code

1. Create a Tool Pack

Log into Merge Agent Handler and navigate to Tool Packs. Click Create Tool Pack and give it a name tied to your use case, like Deal pipeline agent.

Under connectors, select Pipedrive, and choose which tools to enable.

For pipeline monitoring and reporting workflows, enabling deal retrieval, pipeline listing, stage lookup, and person search covers the core cases. Add write tools like create_deal, update_deal, or create_note if your agent needs to create or update records directly.

Save the Tool Pack. You'll return here in step 4 to copy your MCP URL.

2. Add a Registered User

Inside your Tool Pack, create a Registered User. This is the identity context under which your agent operates: the Pipedrive account it acts on behalf of when calling the API.

Give it a name that maps to your environment, like dev-local or your own name. Once created, Merge generates a unique MCP URL scoped to this user.

3. Authenticate Pipedrive

From the Registered User detail page, click Add Connector and select Pipedrive. This kicks off a standard OAuth flow.

Sign in with the Pipedrive account that has access to the pipelines and records you want Claude Code to reach, and grant the requested permissions.

Once the OAuth flow completes, Merge stores and manages the access token. You won't need to re-authenticate unless you revoke access.

4. Gather your credentials

You need two things before configuring Claude Code:

1. MCP URL: found on the Tool Pack detail page under the Registered User you just created. It looks like this:

‍https://ah-api.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp

2. API key: found in Settings > API Keys in your Merge Agent Handler dashboard. Create one if you don't have one yet.

Keep both handy for the next step.

5. Configure Claude Code with Pipedrive

Run the following command in your terminal, substituting your actual MCP URL and API key:

claude mcp add 
--transport http --header "Authorization: Bearer YOUR_API_KEY"
agent-handler
"https://ah-api.merge.dev/api/v1/tool-packs/YOUR_TOOL_PACK_ID/registered-users/YOUR_REGISTERED_USER_ID/mcp"

Verify the connection registered with the command claude mcp list. agent-handler should appear in the output with a connected status.

To confirm the connector is accessible, open a Claude Code session and run a command like "Show me all deals that haven't had any activity in the last 14 days and are currently in the Proposal Sent stage."

You should see an output that looks something like the following:

{{this-blog-only-cta}}

Pipedrive MCP FAQ

In case you have more questions on setting up and using the Pipedrive MCP in Claude Code, we've addressed several more commonly-asked questions below.

What can you do once the Pipedrive MCP is connected to Claude Code?

With Pipedrive connected, Claude Code can:

• Search and retrieve deals: pull deals by stage, owner, pipeline, or value without opening a browser or exporting a CSV

• Query pipeline and stage data: list pipelines, check which stages deals are sitting in, and surface bottlenecks across the funnel

• Look up contacts and organizations: fetch person and company records with full activity history to give agents the context they need before acting

• Create and update records: log new deals, move stage, add notes, or create activities directly from the terminal if write tools are enabled

• Read activity logs: surface calls, meetings, and tasks against any deal or contact to understand what has happened before taking the next step

• Cross-reference CRM data: combine Pipedrive records with data from other connected tools, such as pulling deal details alongside a Slack thread or a Jira ticket in a single session

Why use Merge Agent Handler vs. a self-hosted Pipedrive MCP server?

Pipedrive has a well-documented REST API, which makes it a reasonable candidate for a self-hosted MCP server. For a solo developer writing agents against their own Pipedrive account, that path works: generate an API token, write tool schemas for the endpoints you need, and wire it to Claude Code.

The friction compounds at scale.

Pipedrive API tokens are scoped to individual users, so each developer who needs agent access ends up managing their own token. There's no shared way to control which deals, pipelines, or fields an agent is allowed to touch, and no audit trail showing what the agent queried or updated. When a token needs to be rotated, every developer's local setup breaks until they update it manually.

Pipedrive also has a broad API surface. Covering deals, persons, organizations, activities, notes, pipelines, and stages with correct pagination, field mappings, and error handling is non-trivial to maintain as Pipedrive ships API updates.

Merge Agent Handler centralizes all of that. Authentication is managed once. Each developer gets a Registered User with isolated credentials, so revoking one person's access doesn't affect anyone else. And Tool Packs let you scope exactly which Pipedrive operations each agent can perform, so a pipeline reporting agent never gets access to delete_deal.

Why connect Pipedrive to Claude Code?

Pipedrive holds the data that drives sales execution: which deals are active, which have stalled, what activity happened last, and who owns what. Developers building agents that automate any part of that workflow need live CRM data, and right now that means a browser, an API client, or a one-off script.

With the Pipedrive MCP connected, Claude Code can query deals, surface contacts, and update records without a context switch.

This matters most when CRM data is an input to a larger automated workflow: checking deal stage before sending a follow-up, pulling contact history before drafting an outreach, scanning for stale deals before generating a weekly pipeline report, and more.