by Pipedrive
Connect Claude, ChatGPT and Cursor to your Pipedrive CRM with no code
Pipedrive MCP Server replaces manual CRM data entry: sales reps and RevOps teams can let an agent draft follow-ups, update deal stages, or summarize a pipeline instead of clicking through Pipedrive's UI. Teams wanting full code visibility should pick an open source server like ckalima's, contract-tested with over 1,700 automated tests, rather than the still-Beta official connector.
Zero-setup OAuth connection to a real, permission-scoped CRM account with no API key management.
Pipedrive owns the official OAuth connector and the underlying CRM data, but the MCP layer itself is trivially replicable, as three separate open source teams have already proven by building equivalent or larger tool sets.
Main trade-off
The official server's tool schema is undocumented and it remains labeled Beta, while more mature open source servers already publish complete, tested schemas.
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.
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
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.
The permissions this connector asks for, as its own documentation states them.
14 actions an agent can call. Open one for its parameters and an example.
Example call
npx -y @ckalima/pipedrive-mcp-server
# then call tool: pipedrive_list_deals { "status": "open", "limit": 25 }Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| status | stringdefault open | Optional | Filter by deal status: open, won, lost or deleted. |
| limit | numberdefault 25 | Optional | Number of results per page. |
| cursor | string | Optional | Pagination cursor from a previous response. |
Returns
| Field | Type | Description |
|---|---|---|
| deals | array | Array of deal objects with id, title, value, stage_id and owner. |
| next_cursor | string | Cursor for the next page, or null if no more results. |
Example call
pipedrive_create_deal { "title": "Acme Corp - Annual Plan", "value": 12000, "currency": "USD", "person_id": 42 }Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| title | string | Required | Deal title. |
| value | number | Optional | Deal monetary value. |
| currency | string | Optional | ISO currency code. |
| person_id | number | Optional | Linked contact person id. |
| custom_fields_by_name | object | Optional | Custom field values keyed by human-readable field name instead of internal hash key. |
Returns
| Field | Type | Description |
|---|---|---|
| id | number | The id of the created deal. |
Example call
pipedrive_update_deal { "id": 501, "stage_id": 3, "value": 15000 }Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| id | number | Required | Deal id to update. |
| stage_id | number | Optional | New pipeline stage id. |
| value | number | Optional | Updated deal value. |
| dry_run | booleandefault false | Optional | Preview the change without applying it. |
Returns
| Field | Type | Description |
|---|---|---|
| success | boolean | Whether the update was applied. |
Example call
pipedrive_search_deals { "term": "Acme renewal" }Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| term | string | Required | Search query text. |
| limit | numberdefault 10 | Optional | Max results to return. |
Returns
| Field | Type | Description |
|---|---|---|
| results | array | Matching deals ranked by relevance. |
Example call
pipedrive_delete_deal { "id": 501, "confirm": "DELETE" }Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| id | number | Required | Deal id to delete. |
| confirm | string | Required | Must be the literal string DELETE to proceed. |
Returns
| Field | Type | Description |
|---|---|---|
| success | boolean | Whether the deal was deleted. |
Example call
pipedrive_list_persons { "limit": 50 }Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| limit | numberdefault 25 | Optional | Results per page. |
| offset | numberdefault 0 | Optional | Pagination offset. |
Returns
| Field | Type | Description |
|---|---|---|
| persons | array | Array of contact objects with id, name, email and org_id. |
Example call
pipedrive_create_person { "name": "Jane Lee", "email": "jane@acme.com", "org_id": 88 }Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| name | string | Required | Contact's full name. |
| string | Optional | Contact's email address. | |
| org_id | number | Optional | Linked organization id. |
Returns
| Field | Type | Description |
|---|---|---|
| id | number | The id of the created person. |
Example call
pipedrive_list_organizations { "limit": 25 }Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| limit | numberdefault 25 | Optional | Results per page. |
Returns
| Field | Type | Description |
|---|---|---|
| organizations | array | Array of organization objects with id, name and address. |
Example call
pipedrive_create_activity { "subject": "Follow-up call", "type": "call", "deal_id": 501, "due_date": "2026-07-10" }Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| subject | string | Required | Activity title. |
| type | stringdefault task | Optional | Activity type: call, meeting, task, email or deadline. |
| deal_id | number | Optional | Linked deal id. |
| due_date | string | Optional | Due date in YYYY-MM-DD format. |
Returns
| Field | Type | Description |
|---|---|---|
| id | number | The id of the created activity. |
Example call
pipedrive_create_note { "content": "Customer wants a Q3 renewal quote.", "deal_id": 501 }Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| content | string | Required | Note text. |
| deal_id | number | Optional | Deal to attach the note to. |
| person_id | number | Optional | Person to attach the note to. |
Returns
| Field | Type | Description |
|---|---|---|
| id | number | The id of the created note. |
Example call
pipedrive_list_leads { "limit": 25 }Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| limit | numberdefault 25 | Optional | Results per page. |
Returns
| Field | Type | Description |
|---|---|---|
| leads | array | Array of lead objects with id, title and owner. |
Example call
pipedrive_convert_lead_to_deal { "lead_id": 217, "pipeline_id": 1 }Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| lead_id | string | Required | Id of the lead to convert. |
| pipeline_id | number | Optional | Target pipeline for the new deal. |
Returns
| Field | Type | Description |
|---|---|---|
| deal_id | number | The id of the newly created deal. |
Example call
pipedrive_list_pipelines {}Returns
| Field | Type | Description |
|---|---|---|
| pipelines | array | Array of pipeline objects, each with an ordered list of stages. |
Example call
pipedrive_get_current_user {}Returns
| Field | Type | Description |
|---|---|---|
| user | object | User id, name, email and role/permission set. |
Pipedrive MCP Server is the official Model Context Protocol connector for Pipedrive, the CRM used by more than 100,000 companies. It authenticates via OAuth, giving agents like Claude, ChatGPT and Cursor read and write access to deals, contacts and pipelines with no API key. Open source alternatives add many more callable tools built on the same REST API.
Official OAuth connector
Pipedrive's own hosted MCP server at mcp.pipedrive.ai launched in 2026, needs no API key and authorizes through a standard OAuth 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.
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.
| Skill | Works with | Connects by | Checked |
|---|---|---|---|
| Claude · ChatGPT · Cursor · Windsurf | MCP | 19 Aug | |
| Claude · Cursor | MCP | 26 Oct | |
| Claude · Codex · Cursor · Windsurf +1 | MCP | 19 Aug | |
| Claude · ChatGPT · Codex · Cursor +2 | MCP | 22 Nov |
The official MCP server has no separate fee: it's bundled with any paid Pipedrive plan, from Essential at $14 per seat per month up to Enterprise at $79 per seat per month, billed annually. There's no standalone Pipedrive free tier, so a paid seat is required before you can use the connector at all. Open source servers like ckalima/pipedrive-mcp-server and Nubiia's mcp-pipedrive are MIT-licensed and free to self-host, provided you already have a Pipedrive account and API token.
There's no free tier for Pipedrive itself, so the MCP connector needs an active paid subscription before it does anything. Within that constraint, the connector layer costs nothing extra: the official server ships free with every plan, and the open source community servers are MIT-licensed with no usage fees beyond a Pipedrive account and API token. The only ongoing cost is API rate limits, which scale with seat count and plan tier rather than a separate MCP fee.
For a hosted, no-code option similar to the official connector, Zapier's MCP for Pipedrive and Pipedream's hosted Pipedrive MCP both work without a local install. For maximum tool coverage and full code visibility, Nubiia's mcp-pipedrive, which exposes more than 300 tools, and ckalima's pipedrive-mcp-server are the strongest open source picks, each publishing its complete tool list on GitHub. If your team runs on a different CRM entirely, Salesforce and HubSpot each have their own emerging MCP connectors worth checking with the vendor directly.
Pipedrive ships a first-party, OAuth-only hosted connector directly from the vendor, with permissions inherited automatically from the logged-in user. Salesforce, as of 2026, leans mostly on third-party and community MCP servers rather than one official hosted endpoint, so Salesforce users more often authenticate with an API token or connected app instead of a simple OAuth popup. For a small or mid-market sales team, Pipedrive's official server is the faster path from zero to a working AI-CRM connection; Salesforce integrations demand more setup but offer deeper enterprise governance controls.
For the official server, no installation is required: in Claude, add a custom connector with the URL https://mcp.pipedrive.ai/mcp under Settings, then Connectors, then authorize through the OAuth popup with your Pipedrive login. For open source options such as ckalima/pipedrive-mcp-server, install Node.js 18 or newer, set PIPEDRIVE_API_TOKEN and PIPEDRIVE_COMPANY_DOMAIN as environment variables, then run npx -y @ckalima/pipedrive-mcp-server. Either route needs an active paid Pipedrive plan first, since the CRM itself is the actual data source.
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, open source community servers built on the same Pipedrive REST API already existed, with 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. Community servers work differently: they run as a local Node.js or Python process launched with a single command, authenticating with a personal Pipedrive API token set as an environment variable, and expose their tools over STDIO to any MCP-compatible client.
Since both flavors speak the same MCP protocol, they work in any compatible client without extra code. The most actively maintained open source pick is ckalima/pipedrive-mcp-server, which wraps deal, contact, organization, activity, lead, note, product and pipeline endpoints into one package and is tested directly against Pipedrive's own OpenAPI spec. That 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 clicking through Pipedrive's UI for each task.
The official server itself costs nothing beyond your existing Pipedrive plan, and the MIT-licensed community servers are free to run 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.
Pipedrive's API is also mid-migration from v1 to v2, with v1 endpoints scheduled to sunset July 31, 2026, so any integration still relying purely on v1 will need an update soon. Open source servers publish transparent, versioned schemas on GitHub, unlike the official connector's unpublished tool list.
Protocol, authentication, permissions and the call contracts on this page are read from Pipedrive's own documentation. The verdict is Hokai's reading of them, not the maintainer's claim.