Connect Pipedrive to Claude Code

Make Claude create deals, log activities, and update records in Pipedrive. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Pipedrive to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Pipedrive, you add a Pipedrive MCP server: a small hosted service that exposes Pipedrive's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Pipedrive account. No API keys pasted into config files.

claude mcp add --transport http pipedrive https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Pipedrive once connected?

Full read-write Pipedrive access lets Claude create a deal in the right pipeline and stage, add or update people and organizations, log calls and meetings, advance a deal forward, and attach notes, all from the same conversation where you discuss the work. The CRM upkeep that used to mean switching tabs happens inline.

Create a new deal in the right pipeline and stage with its value and owner
Add or update a person and link them to an organization
Log a call, meeting, or email as an activity on a deal
Move a deal to the next stage or mark it won or lost after you confirm
Add a note to a deal or contact summarizing a conversation
Find every open deal matching a filter and propose follow-up activities

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Pipedrive access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Pipedrive API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Pipedrive changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Pipedrive connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Pipedrive connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Pipedrive account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Pipedrive's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Pipedrive?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Pipedrive account it signs in with. Revoking access is one click in Pipedrive.

More on the Pipedrive connector

Pipedrive connector for claude.ai Salesforce + Claude Code HubSpot + Claude Code Zoho CRM + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us