Pipedrive MCP: Official Server on Every Plan
Yes — Pipedrive has an official MCP server. Pipedrive built and hosts a native, remote MCP server (https://mcp.pipedrive.ai/mcp) that lets any MCP-compatible AI tool read and update your CRM by natural language — search deals, create records, update contacts, schedule activities, analyze pipelines. It launched June 30, 2026, it’s available on every Pipedrive plan, and connecting takes an OAuth login with no code. So if you’re searching “Pipedrive MCP,” the connection you want is real and it comes straight from Pipedrive.
The thing worth knowing before you set it up: an MCP server hands your CRM to an AI inside a conversation you start. It’s a doorway, not a worker. Nothing watches Pipedrive for you, nothing fires when a deal changes stage, and nothing runs while the chat is closed. Here’s exactly what the Pipedrive MCP does, how to turn it on, where it stops — and what to use when you want Pipedrive work that runs on its own.
Pipedrive is one of many — the complete list of MCP servers covers every app that ships one, grouped by category.
What the Pipedrive MCP server does
Model Context Protocol (MCP) is the open standard that lets an AI client — Claude, ChatGPT, Cursor, VS Code, and others — talk to an outside app through a shared interface. Pipedrive hosts its own remote server (currently labeled “Pipedrive MCP BETA” in the connector setup), so there’s nothing to build or run yourself. It respects your existing user permissions — the AI can only touch data and take actions your Pipedrive account is already authorized for.
With it connected, an AI client can:
- Look up records — “pull the Acme deal and its linked contacts and activities” answered from the live CRM, not a training-data guess.
- Search and filter — “which deals in the pipeline have no activity scheduled this week?” run against real data.
- Create and update — add a contact, move a deal to the next stage, log an activity, convert a lead into a deal without opening Pipedrive.
- Reason across your pipeline — summarize where deals are stalling, turn meeting notes into structured records, draft follow-ups from actual deal history.
It’s genuinely useful for ad-hoc work: ask a question, get an answer grounded in your CRM, make a change on the spot.
How to set up the Pipedrive MCP server
The remote server is the quick path — no code, no hosting. Using Claude as the example (ChatGPT and other MCP clients are similar):
- In your AI client’s connector settings, choose Add custom connector and paste the server URL
https://mcp.pipedrive.ai/mcp. - Authorize it against your Pipedrive account through the OAuth prompt, then review and approve the requested permissions in the Pipedrive pop-up — you’re granting the AI the same access your own user has.
- Confirm the tools appear in the client, then start a chat and ask it to read or update a record.
Pipedrive’s own setup guides cover the exact clicks for Claude and ChatGPT, and the connection works on all Pipedrive plans.
Where the Pipedrive MCP stops
None of this is a knock on MCP — it’s just the shape of the protocol. Four limits show up the moment you want more than a conversation:
- It only works inside a chat you start. Close the window and nothing happens. The AI doesn’t watch Pipedrive; it waits for you to ask.
- No triggers. A deal moving to Won, a new lead landing in your inbox, a deal going quiet for a week — none of these can start anything through MCP. There’s no “when this happens in Pipedrive, do that.”
- It’s one app at a time. The Pipedrive MCP knows Pipedrive. Getting a won deal into QuickBooks, a Slack channel, and a Google Sheet means wiring up (and authing) a separate MCP server for each, then hoping your client can juggle them in one turn.
- You own the scopes and the blast radius. The AI acts as your Pipedrive user, and the read/write access it’s granted over your whole CRM is on you to manage.
So the Pipedrive MCP is a great way to ask Pipedrive things and make one-off edits. It is not a way to make Pipedrive run — to have work happen on a schedule or in reaction to an event, across the other tools a deal touches.
Running Pipedrive work that doesn’t need a chat open
That “run on its own, across apps” gap is exactly where Carly fits. Carly connects to Pipedrive natively — no MCP server to point at, no OAuth plumbing to babysit — and to the ~260 other apps it supports, plus anything with a public API through your own key. The difference from MCP is the important part: Carly’s workflows are triggered and scheduled, so Pipedrive work happens whether or not anyone has a chat window open.
A few things that MCP can’t do but a Carly workflow can:
- When a deal hits Won → create the QuickBooks customer, post to the
#closed-wonSlack channel, and add a row to the revenue sheet — automatically, the moment it happens. - Every morning → summarize deals with no activity in 7 days and send the list to the deal owner.
- When a new lead comes in → enrich the contact, assign it to the right rep by territory, and draft the first outreach email for approval.
The non-AI steps — the moving, matching, and routing between apps — are free and unlimited, the Zapier-style backbone of the workflow. The AI steps (drafting, summarizing, deciding) start at $35/month. You describe the outcome in plain language and Carly wires up the Pipedrive connection and everything downstream.
If you just want to interrogate your CRM from a chat, Pipedrive’s official MCP server is the right tool and it’s free to connect. If you want Pipedrive to actually do things — on a trigger, on a schedule, across every app a deal flows through — that’s the job MCP wasn’t built for, and it’s the one Carly was.
FAQ
Does Pipedrive have an official MCP server?
Yes. Pipedrive launched its native, hosted MCP server at https://mcp.pipedrive.ai/mcp on June 30, 2026. It’s built and maintained by Pipedrive, connects by OAuth with no code, gives MCP-compatible AI tools read/write access to your CRM, and is available on all Pipedrive plans.
Is the Pipedrive MCP server free? Connecting it is free — you’re authorizing an AI client against your existing Pipedrive account and permissions. You still need whatever Pipedrive plan your CRM data lives on, and the server works across all tiers.
Can the Pipedrive MCP trigger automations? No. MCP is request/response inside an AI chat — it has no triggers and nothing runs when the conversation is closed. For event- or schedule-driven Pipedrive work across apps, you need a workflow tool like Carly rather than an MCP server.
Can I connect Pipedrive to AI without coding or hosting a server? Yes. You don’t have to touch MCP at all. Carly connects to Pipedrive for you and lets you build the automation in plain language — describe what you want to happen and it wires up the CRM and the other apps involved, with no server to host and no code to write.
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
