Pipedrive MCP Server: Official CRM AI Connector (2026)
Pipedrive shipped an official MCP server in 2026 linking Claude and Cursor to CRM data via OAuth. Open source servers add 155 tools for deals and contacts free.
Pipedrive MCP Server connects AI agents directly to your Pipedrive CRM. The official version, launched June 30, 2026, uses OAuth and needs no setup, free on any paid plan. Open source alternatives like the 155-tool ckalima server run locally via an API token for teams that want full control over deals, contacts and pipeline automation.
Pipedrive MCP Server is the official Model Context Protocol connector Pipedrive launched on June 30, 2026 at mcp.pipedrive.ai. It uses OAuth 2.0, so agents like Claude, ChatGPT and Cursor read and write deals, contacts and pipelines with no API key or code. It is free on every Pipedrive plan, starting at $14 per seat monthly. Open source community servers add over 150 more tools.
Maker: Pipedrive · Protocol: MCP · Auth: oauth
Compatible agents: Claude Desktop, Claude Code, Claude for Cowork, ChatGPT / OpenAI Agents SDK, Cursor, Windsurf, any MCP-compatible client
Required runtime: None for the official hosted server (OAuth only), Node.js 18+ for community STDIO servers, Docker optional for containerized community deployments
About Pipedrive MCP Server
Pipedrive MCP Server is the connector that lets an AI agent read and act on your Pipedrive CRM data instead of a human copying it by hand. Pipedrive, the CRM company founded in Tallinn, Estonia in 2010 and now used by more than 100,000 companies in 179 countries, launched its own official Model Context Protocol server on June 30, 2026, at mcp.pipedrive.ai. Alongside it, a set of open source community servers built on the same Pipedrive REST API already existed, the largest exposing over 300 individual tools. The official server is a hosted remote MCP endpoint reachable over HTTP, not a program you install. An agent connects to https://mcp.pipedrive.ai/mcp, the user authorizes access through a standard OAuth 2.0 popup, and every action the agent takes afterward is logged in Pipedrive's own change log and respects that user's existing role and visibility permissions. There is no API key to copy or rotate. Community servers work differently: they run as a local Node.js or Python process launched with a single command, authenticate with a personal Pipedrive API token set as an environment variable, and expose their tools over STDIO to any MCP-compatible client. Both flavors are usable from Claude Desktop, Claude Code, Claude for Cowork, ChatGPT's Agents SDK, Cursor and Windsurf, since all of them speak the same MCP protocol. The best-documented open source option, ckalima's pipedrive-mcp-server, exposes 155 tools across deals, persons, organizations, activities, leads, notes, products and pipelines, is contract-tested against Pipedrive's own OpenAPI spec with more than 1,700 tests, and gates destructive actions like delete behind an explicit flag. This makes it a solid fit for sales teams that want an agent to draft follow-up notes, move deals through stages, or summarize a pipeline without a human clicking through Pipedrive's UI for each task. The official server is free with any Pipedrive plan, which runs from Essential at $14 per seat per month to Enterprise at $79 per seat per month. The MIT-licensed community servers cost nothing beyond a Pipedrive account and API token. Pipedrive's own API enforces a daily token budget (30,000 base tokens times a plan multiplier times seat count) and burst limits of 20 to 120 requests per 2 seconds depending on plan, so heavy agent use shares the same quota as human API consumers. The official connector is still labeled Beta as of its June 2026 launch and its exact tool list is not publicly documented, unlike the transparent, versioned schemas the community servers publish on GitHub. Pipedrive's API is also mid-migration from v1 to v2, with v1 endpoints scheduled to sunset July 31, 2026, so any server still relying purely on v1 will need an update soon after.
Key Features
- Official OAuth connector: Pipedrive's own hosted MCP server at mcp.pipedrive.ai launched June 30, 2026, needs no API key and authorizes through a standard OAuth 2.0 popup.
- 155+ open source tools available: The leading community server, ckalima/pipedrive-mcp-server, exposes 155 tools across deals, persons, organizations, leads, products and pipelines under an MIT license.
- Permission-aware actions: Actions taken through the official connector inherit the connected user's existing Pipedrive role and visibility settings and are written to Pipedrive's audit log.
- Contract-tested against the real API: ckalima's server runs over 1,700 tests against Pipedrive's vendored OpenAPI spec and is v2-first with v1 fallback ahead of the July 31, 2026 v1 API sunset.
- Safe-write guardrails: Destructive operations like delete require an explicit confirm: "DELETE" parameter, and a dry_run flag lets an agent preview a write before committing it.
- Human-readable custom fields: Write tools accept custom_fields_by_name so an agent can set values like Tier or Expected Revenue by name instead of Pipedrive's internal hash keys.
Use Cases
- Agent-drafted deal follow-ups: An AI agent reads a stalled deal's history via pipedrive_get_deal and pipedrive_list_notes, then drafts and logs a follow-up note without a rep opening Pipedrive.
- Natural-language pipeline summaries: A sales manager asks Claude to summarize this week's pipeline movement; the agent calls list_deals and list_stages and returns a plain-English rollup instead of building a report by hand.
- Bulk contact and organization cleanup: An agent searches for duplicate persons or organizations, flags them, and merges or updates records in batches using the search and update tools instead of manual CSV exports.
- Lead-to-deal conversion automation: When a lead meets a scoring threshold, an agent calls pipedrive_convert_lead_to_deal to move it into the active pipeline automatically.
- Cross-tool CRM sync: An agent orchestrating a support ticket, a calendar invite and a Pipedrive deal keeps all three in sync in one conversation, since the CRM step is just another MCP tool call.
Install
Official (recommended): add connector URL https://mcp.pipedrive.ai/mcp in your MCP client and authorize via OAuth. Open source alternative: npx -y @ckalima/pipedrive-mcp-server
Requirements
- A Pipedrive account on any paid plan (Essential $14/seat/mo or higher)
- For the official server: authorize the connector via OAuth 2.0 in your MCP client (Claude Customize > Connectors > Add custom connector)
- For open source servers: Node.js 18+ and a personal Pipedrive API token set as PIPEDRIVE_API_TOKEN
- For open source servers: your Pipedrive company domain set as PIPEDRIVE_COMPANY_DOMAIN
Actions
List Deals
Returns a paginated list of deals, optionally filtered by stage, owner or status.
npx -y @ckalima/pipedrive-mcp-server
# then call tool: pipedrive_list_deals { "status": "open", "limit": 25 }status(string): Filter by deal status: open, won, lost or deleted.limit(number): Number of results per page.cursor(string): Pagination cursor from a previous response.
Create Deal
Creates a new deal in a pipeline stage.
pipedrive_create_deal { "title": "Acme Corp - Annual Plan", "value": 12000, "currency": "USD", "person_id": 42 }title(string) — required: Deal title.value(number): Deal monetary value.currency(string): ISO currency code.person_id(number): Linked contact person id.custom_fields_by_name(object): Custom field values keyed by human-readable field name instead of internal hash key.
Update Deal
Updates fields on an existing deal, such as moving it to a new stage.
pipedrive_update_deal { "id": 501, "stage_id": 3, "value": 15000 }id(number) — required: Deal id to update.stage_id(number): New pipeline stage id.value(number): Updated deal value.dry_run(boolean): Preview the change without applying it.
Search Deals
Full-text search across deal titles and notes.
pipedrive_search_deals { "term": "Acme renewal" }term(string) — required: Search query text.limit(number): Max results to return.
Delete Deal
Permanently deletes a deal. Disabled by default and requires an explicit confirmation string.
pipedrive_delete_deal { "id": 501, "confirm": "DELETE" }id(number) — required: Deal id to delete.confirm(string) — required: Must be the literal string DELETE to proceed.
List Persons
Returns a paginated list of contact records (people).
pipedrive_list_persons { "limit": 50 }limit(number): Results per page.offset(number): Pagination offset.
Create Person
Creates a new contact record.
pipedrive_create_person { "name": "Jane Lee", "email": "jane@acme.com", "org_id": 88 }name(string) — required: Contact's full name.email(string): Contact's email address.org_id(number): Linked organization id.
List Organizations
Returns companies/organizations stored in the CRM.
pipedrive_list_organizations { "limit": 25 }limit(number): Results per page.
Create Activity
Schedules a task, call or meeting linked to a deal or contact.
pipedrive_create_activity { "subject": "Follow-up call", "type": "call", "deal_id": 501, "due_date": "2026-07-10" }subject(string) — required: Activity title.type(string): Activity type: call, meeting, task, email or deadline.deal_id(number): Linked deal id.due_date(string): Due date in YYYY-MM-DD format.
Create Note
Adds a note to a deal, person or organization.
pipedrive_create_note { "content": "Customer wants a Q3 renewal quote.", "deal_id": 501 }content(string) — required: Note text.deal_id(number): Deal to attach the note to.person_id(number): Person to attach the note to.
List Leads
Returns leads that have not yet been converted into deals.
pipedrive_list_leads { "limit": 25 }limit(number): Results per page.
Convert Lead to Deal
Promotes a qualified lead into an active deal in the pipeline.
pipedrive_convert_lead_to_deal { "lead_id": 217, "pipeline_id": 1 }lead_id(string) — required: Id of the lead to convert.pipeline_id(number): Target pipeline for the new deal.
List Pipelines
Returns all sales pipelines and their stages configured in the account.
pipedrive_list_pipelines {}Get Current User
Returns the identity and permissions of the account the agent is authenticated as.
pipedrive_get_current_user {}
How to Invoke
The official server exposes CRM actions as MCP tools over a hosted HTTP/SSE endpoint (mcp.pipedrive.ai/mcp) that any MCP client calls by tool name once OAuth is authorized. Open source servers (e.g. ckalima/pipedrive-mcp-server) run locally via npx and expose the same style of tools (pipedrive_list_deals, pipedrive_create_person, etc.) over STDIO.
Pricing
The official MCP server is included free with any Pipedrive CRM plan: Essential $14/seat/mo, Advanced, Professional, Power, up to Enterprise $79/seat/mo. Open source community servers (MIT license, e.g. ckalima/pipedrive-mcp-server, comma-compliance/pipedrive-mcp, @nubiia/mcp-pipedrive) are free to self-host and only require a Pipedrive account and API token.
Strengths
- The official server requires zero setup beyond an OAuth click, no API key to generate or rotate.
- Open source servers are MIT-licensed, actively maintained, and cover the vast majority of the Pipedrive API (up to 307 tools in the largest implementation).
- Rate limits scale with plan tier, and OAuth apps get 4x the burst allowance of API-token access.
- Works across every major MCP client: Claude, ChatGPT, Cursor and Windsurf, without per-client custom code.
Weaknesses
- The official server's exact tool list is not publicly documented and it is still labeled Beta as of its June 2026 launch.
- Community STDIO servers only run locally, so they need a machine or container to host them for always-on agent use.
- API token auth on community servers attributes every action to one Pipedrive user, without OAuth-level per-user scoping.
- Search calls cost 40 rate-limit tokens each, which can burn through the daily budget fast on data-heavy agent workflows.
Frequently Asked Questions
What is Pipedrive MCP Server and what does it do?
Pipedrive MCP Server is a Model Context Protocol connector that lets an AI agent read and update your Pipedrive CRM data directly. Pipedrive, the CRM founded in Tallinn, Estonia in 2010 and used by more than 100,000 companies, launched its own official version on June 30, 2026 at mcp.pipedrive.ai. It exposes CRM objects like deals, contacts, organizations, activities and leads as callable tools an agent can list, create, update, search and sometimes delete. Open source community servers built on the same Pipedrive REST API existed before the official launch and remain available, with the largest exposing over 300 tools. In practice this means you can ask Claude or ChatGPT to summarize your pipeline, log a call, or move a deal to a new stage without opening the Pipedrive interface yourself.
How do I install and set up Pipedrive MCP Server?
For the official server, no installation is required: in Claude, go to Customize, then Connectors, then Add custom connector, name it Pipedrive MCP BETA, and paste the connection URL https://mcp.pipedrive.ai/mcp, then authorize through the OAuth popup with your Pipedrive login. For open source servers such as ckalima/pipedrive-mcp-server, you need Node.js 18 or newer and run npx -y @ckalima/pipedrive-mcp-server after setting PIPEDRIVE_API_TOKEN and PIPEDRIVE_COMPANY_DOMAIN as environment variables. The API token comes from your Pipedrive account under Settings, then Personal preferences, then API. Both routes require an active paid Pipedrive plan, since the CRM itself is the data source. After setup, most MCP clients need a restart to detect the new tools.
Which agents and LLMs support Pipedrive MCP Server?
Because it speaks the open Model Context Protocol, Pipedrive MCP Server works with any MCP-compatible client. Confirmed support includes Claude Desktop, Claude Code and Claude for Cowork, OpenAI's ChatGPT and Agents SDK, Cursor, and Windsurf. Third-party platforms like Zapier, n8n, Pipedream and Activepieces also expose hosted Pipedrive MCP endpoints so agents built on those platforms can reach the same CRM data without running a local server. The official connector uses HTTP with OAuth, while open source community servers typically run over STDIO, so which one fits depends on whether your agent runs locally or in the cloud. Any agent framework that can register an MCP tool server, including custom LangChain or LlamaIndex agents, can integrate it as well.
How much does Pipedrive MCP Server cost?
The official MCP server has no separate fee: it is bundled free with any paid Pipedrive CRM plan, which ranges from Essential at $14 per seat per month up to Enterprise at $79 per seat per month, billed annually. There is no Pipedrive free tier, so you need at least the Essential plan to use the connector at all. Open source community servers like ckalima/pipedrive-mcp-server, comma-compliance/pipedrive-mcp and Nubiia's mcp-pipedrive are released under the MIT license and cost nothing to run beyond your existing Pipedrive subscription and an API token. A small number of niche community servers, such as one built on the CData connector or a non-commercial GarethWright build, carry their own separate license fees or usage restrictions. For most teams the real cost is simply the Pipedrive seat price, not the MCP layer itself.
Is Pipedrive MCP Server open source?
The official Pipedrive-maintained MCP server is proprietary and hosted; Pipedrive has not published its source code or its full tool schema. However, several community-built alternatives are fully open source under the MIT license, including ckalima/pipedrive-mcp-server with 155 tools and over 1,700 contract tests, comma-compliance/pipedrive-mcp with 88 tools, and Nubiia's mcp-pipedrive with over 300 tools. These are free to inspect, fork and self-host, and each publishes its full list of exposed tools and parameters on GitHub. A separate GarethWright community build is released under a non-commercial Creative Commons license, so it cannot be used in a paid product. Anyone who wants full transparency into exactly what an agent can call should choose one of the MIT-licensed open source servers over the official beta.
What are the best alternatives to Pipedrive MCP Server?
If your team already runs on HubSpot or Salesforce, those CRMs have their own emerging MCP connectors worth checking directly with the vendor, since data cannot move between CRMs through Pipedrive's server. For teams that want a hosted, no-code option similar to Pipedrive's official connector but through an automation platform, Zapier's MCP for Pipedrive and Pipedream's hosted Pipedrive MCP both work without any local install. For teams that want maximum tool coverage and full control, Nubiia's mcp-pipedrive (307 tools) or ckalima's pipedrive-mcp-server (155 tools, contract-tested) are the strongest open source picks. Pick the official server if you want zero setup and don't need heavy customization; pick an open source server if you need more tools, want to audit the code, or need to run fully offline behind a firewall.
Who is Pipedrive MCP Server best for?
It is best for sales teams and RevOps functions already using Pipedrive who want an AI agent to handle repetitive CRM tasks: logging notes, updating deal stages, scheduling follow-up activities, or summarizing a pipeline in plain language. Developers building custom internal agents also benefit from the open source servers' fully documented tool schemas and safe-write guardrails like dry-run mode. It is a poor fit for teams not already on a paid Pipedrive plan, since there is no free tier to test against, and for teams needing a fully audited, enterprise-certified integration, since the official connector is still in Beta and its internal tool list is not published. It's also not the right tool if you need cross-CRM data movement, since it only reads and writes within Pipedrive itself.
How does Pipedrive MCP Server compare to Salesforce MCP integrations in 2026?
Pipedrive's official MCP server ships as a first-party, OAuth-only hosted connector directly from the vendor, launched June 30, 2026, with no published tool count but full permission inheritance from the logged-in user. Salesforce, as of 2026, primarily relies on third-party and community MCP servers rather than a single first-party hosted endpoint, so Salesforce users more often authenticate with an API token or connected app rather than a simple OAuth popup. Pipedrive's rate limits are token-budget based (30,000 base tokens times plan multiplier times seats), while Salesforce's API governor limits are org-wide and often stricter for smaller editions. For a small or mid-market sales team wanting the fastest path from zero to a working AI-CRM connection, Pipedrive's official server is simpler to set up; Salesforce integrations currently demand more configuration but offer deeper enterprise governance controls.