How to use Pipedrive from Cursor

Yes: add Pipedrive's official MCP server (https://mcp.pipedrive.ai/mcp) to Cursor's mcp.json and sign in to Pipedrive when Cursor asks. Pipedrive mentions Cursor on its MCP page but publishes no Cursor guide, and Pipedrive isn't in the Cursor Marketplace, so there's no one-click install. We haven't tested the sign-in from Cursor (checked October 30, 2026). The tools are the same 51 that Claude and ChatGPT get: read, create and update one record at a time, with no delete, merge or bulk edit.

Quick answer: what to do in your situation

What you need before you start

• Pipedrive: any plan. The MCP is included at no extra cost (Pipedrive MCP page). You need permission to install apps in your Pipedrive company, and an admin can switch MCP access off for the whole company in Company settings (product updates, September 2026).
• Cursor: the desktop app. Cursor's MCP docs don't mention a plan requirement for MCP servers.
• Ten minutes and a test record you don't mind changing.

How to add Pipedrive to Cursor, step by step

1. Open your MCP config. For every project, use ~/.cursor/mcp.json in your home folder. For one project only, create .cursor/mcp.json in it.

2. Add the server.

   {
     "mcpServers": {
       "pipedrive": {
         "url": "https://mcp.pipedrive.ai/mcp"
       }
     }
   }
   

   No API key and no headers: the server signs you in with OAuth.

3. Find it in Cursor. Open Customize in the sidebar, where Cursor lists your MCP servers. Pipedrive should show as needing sign-in.

4. Sign in to Pipedrive. Cursor opens the browser. Pick your company, read the permissions and click Allow and install.

5. Check the tools. Back in Cursor, the server should list its tools: 51 on October 22, 2026 (Pipedrive MCP tools).

6. Test in the agent chat with a read-only question: "Using Pipedrive, list my open deals worth more than 10,000 with no activity in 14 days." Cursor asks for approval before running MCP tools by default.

If sign-in fails. Pipedrive only accepts sign-in from addresses it has approved. Between October 15 and 28, 2026, at least seven MCP client vendors asked Pipedrive on its developer community to add theirs (for example, Blueticks). If you see "invalid redirect URI" or a token error, check the MCP logs in Cursor's Output panel; only Pipedrive can fix it.

For teams

A team admin can add Pipedrive as a shared Team MCP server under Dashboard > Plugins & MCPs. Cursor's docs don't say whether each person then signs in separately; with OAuth they should, so each person would see only what Pipedrive lets them see. Enterprise admins can also allowlist servers under Team Settings > MCP Configuration and set which tools run without asking: a sensible start is only the tools whose names begin with get and search.

What it's good for in Cursor

If you build on Pipedrive. The most useful tool is getAccountContext: your pipelines, stages, custom fields and users in one call. Ask "what's the field key (the code Pipedrive uses for the field in the API) of the custom field Contract end date on deals, and which values does Lead source accept?" and paste the answer into your code. You can also check that your webhook or sync wrote what you expected: "show me the last three people created today with their emails and phones".

If you run ops from the editor. Some ops people keep notes, scripts and CSVs in Cursor. With Pipedrive connected, you can check a list against the CRM before importing it ("which of these 30 emails already exist as people?") or create follow-ups from meeting notes in a Markdown file.

What it's not for. The official server writes one record at a time with no preview of the whole set. "Update the owner on these 200 deals" becomes 200 calls and 200 approvals, or 200 unreviewed writes if you turn approvals off.

Prompts you can copy

What you can and can't do

The server is the same for every assistant: read, search, create and update deals, people, organizations, leads, products, activities and notes one record at a time, convert leads, read stages and account context, plus linked emails and projects. It can't delete, merge, bulk edit, undo, manage pipelines, custom fields or webhooks, or send email. Full comparison: Does Pipedrive have an MCP server?.

Costs and limits

The MCP is free on every Pipedrive plan, and Pipedrive says usage "is subject to token limits based on your plan". It doesn't say whether that's the same daily API budget your integrations and your own code use. If it is, a prompt that checks 30 emails is 30 searches, and Pipedrive's API docs price one search at 40 tokens on v1 endpoints. When the budget runs out, requests fail until the reset, which we measured at 07:00 UTC on a US-hosted sandbox account on October 16, 2026 (it may move to 08:00 UTC after November 1). More in Why Claude used up your Pipedrive API tokens.

What can go wrong

• Turning approvals off. With approvals off, a 200-record loop runs 200 unreviewed writes. If it stops halfway, some records change and some don't.
• The wrong record gets matched. "Acme" and "Acme Ltd" look alike to a search. Ask for the matches with their owners first.
• No undo. Restore data has nothing for a one-at-a-time edit; you find the old value in the change log and type it back.

Before you let Cursor write

• Keep approvals on and read the tool arguments before each write.
• Keep each request to 20 records or fewer and check them in Pipedrive.
• Try anything new against a Pipedrive sandbox first.

Community servers and the API

The Cursor Marketplace lists HubSpot, Salesforce, Attio, Zoho CRM and HighLevel plugins, but not Pipedrive (Cursor's plugins repository, October 30, 2026). Community MCP servers such as ckalima/pipedrive-mcp-server run locally with a personal API token and often include delete and bulk tools. They act with the token owner's permissions, spend the same company budget and have no undo. Point them at a sandbox first.

What we couldn't verify

• Whether Pipedrive accepts Cursor's sign-in. Cursor uses fixed callbacks (http://localhost:8787/callback on desktop) and registers as a public client with no secret, while Pipedrive's public metadata, read October 30, 2026, lists only client-secret methods at its token endpoint. We didn't connect an account to see whether that matters.
• Whether each teammate signs in separately on a shared Team MCP server.
• Whether Cursor's Cloud Agents can use the same connection; Cursor says their sign-ins are separate.

Where Pipehand fits

Pipehand is planned to launch in April 2027 as a replacement for Pipedrive's MCP that works from Cursor, Claude, ChatGPT, Gemini and other MCP clients, plus a CLI. It is designed to add what the official server can't do: merge duplicates and run bulk edits that first show how many records will change, with approval for large changes and undo afterwards. For a developer, that would be the difference between a loop of 200 single writes and one reviewed change you could roll back.

If you want to change Pipedrive from Cursor with an undo button, join the waitlist on pipehand.com.

FAQ

Is there a Pipedrive MCP for Cursor?

Yes, Pipedrive's official server at https://mcp.pipedrive.ai/mcp works with MCP clients that support remote servers and OAuth. Add it to mcp.json and sign in. There's no Pipedrive plugin in the Cursor Marketplace.

Do I need a Pipedrive API key for Cursor?

Not for the official server: it uses OAuth with your Pipedrive login. Community servers use a personal API token.

Why does Pipedrive sign-in fail in Cursor?

Most likely Pipedrive hasn't approved Cursor's sign-in address yet. Check the MCP logs in the Output panel; only Pipedrive can add it. The same can happen in Gemini.

Can Cursor bulk edit or merge records in Pipedrive?

Not with the official server. It updates one record per call and has no merge or delete tools.

Does it work with Grok Bot?

Adding Pipedrive to Cursor's mcp.json doesn't add it to Grok Bot. See How to use Pipedrive from Grok.