topmcps
Browse MCPs
Pipedrive

Pipedrive

Pipedrive MCP — search deals, contacts, organizations, and activities across the Pipedrive REST API.

Score 56(?)Community (multiple maintained forks — Pipeworx, lukehinds, WillDent)MIT56Verified Top MCPs for CRM →
InstallView on GitHub

Quick answer

What it does

Wraps the Pipedrive REST API as MCP tools — search/read/create/update for deals, persons, organizations, activities, notes, and pipelines via API-token auth.

Best for

  • Deal stage updates from chat
  • Activity logging without leaving the IDE
  • Pipeline reporting queries
  • Person/organization research and updates

Not for

  • Compliance-only-vendor-MCP environments
  • Bulk data migration (use the REST API directly)

Setup recipe

Pick your client, then follow the three steps.

  1. 1

    Install

    claude_desktop_config.json
    {
  "mcpServers": {
    "pipedrive": {
      "command": "npx",
      "args": [
        "-y",
        "pipedrive-mcp-server"
      ],
      "env": {
        "PIPEDRIVE_API_TOKEN": "${PIPEDRIVE_API_TOKEN}"
      }
    }
  }
}

    Paste under mcpServers. Fully quit and reopen Claude after editing.

    CLI or .mcp.json
    # export PIPEDRIVE_API_TOKEN=your_pipedrive_api_token
claude mcp add pipedrive -- npx -y pipedrive-mcp-server

    Run from your repo. Commit .mcp.json to share with your team.

    .cursor/mcp.json
    {
  "mcpServers": {
    "pipedrive": {
      "command": "npx",
      "args": [
        "-y",
        "pipedrive-mcp-server"
      ],
      "env": {
        "PIPEDRIVE_API_TOKEN": "${PIPEDRIVE_API_TOKEN}"
      }
    }
  }
}

    Global path: ~/.cursor/mcp.json. Reload window after editing.

    .vscode/mcp.json
    {
  "servers": {
    "pipedrive": {
      "command": "npx",
      "args": [
        "-y",
        "pipedrive-mcp-server"
      ],
      "env": {
        "PIPEDRIVE_API_TOKEN": "${PIPEDRIVE_API_TOKEN}"
      }
    }
  }
}

    VS Code uses the "servers" key (not "mcpServers").

    ~/.codeium/windsurf/mcp_config.json
    {
  "mcpServers": {
    "pipedrive": {
      "command": "npx",
      "args": [
        "-y",
        "pipedrive-mcp-server"
      ],
      "env": {
        "PIPEDRIVE_API_TOKEN": "${PIPEDRIVE_API_TOKEN}"
      }
    }
  }
}

    Open via Cascade → hammer icon → Configure.

    cline_mcp_settings.json
    {
  "mcpServers": {
    "pipedrive": {
      "command": "npx",
      "args": [
        "-y",
        "pipedrive-mcp-server"
      ],
      "env": {
        "PIPEDRIVE_API_TOKEN": "${PIPEDRIVE_API_TOKEN}"
      }
    }
  }
}

    Open via the Cline sidebar → MCP Servers → Edit.

    ~/.continue/config.json
    {
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "pipedrive-mcp-server"
          ],
          "env": {
            "PIPEDRIVE_API_TOKEN": "${PIPEDRIVE_API_TOKEN}"
          }
        }
      }
    ]
  }
}

    Continue uses modelContextProtocolServers with a transport block.

    ~/.codex/config.toml
    # ~/.codex/config.toml
[mcp_servers.pipedrive]
command = "npx"
args = [
  "-y",
  "pipedrive-mcp-server",
]
env = { PIPEDRIVE_API_TOKEN = "${PIPEDRIVE_API_TOKEN}" }

    Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

    ~/.config/zed/settings.json
    {
  "context_servers": {
    "pipedrive": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "pipedrive-mcp-server"
        ]
      },
      "env": {
        "PIPEDRIVE_API_TOKEN": "${PIPEDRIVE_API_TOKEN}"
      }
    }
  }
}

    Zed calls them "context_servers". Settings live-reload on save.

    ChatGPT → Apps directory

    Pipedrive doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

  2. 2

    Set required secrets

    Set PIPEDRIVE_API_TOKEN in your shell environment before launching your MCP client.

  3. 3

    Try a minimum working prompt

    Surface stuck deals across the pipeline

    Using the Pipedrive MCP, find every deal in stage "Proposal Sent" that has had no activity in the last 14 days. Return deal title, owner, value, and last activity date.

    Tested with: Claude Desktop, Cursor.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

Security & scope

Access scope
Read + write
Sandbox
Authenticates with a Pipedrive API token. Access scope matches the token-owner's permissions in Pipedrive.
Gotchas
  • Personal API tokens inherit all of the user's permissions — create a dedicated automation user with minimum scope rather than reusing a salesperson's token.
  • Pipedrive enforces per-token rate limits; high-volume agents should batch reads via the unified search endpoint.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.
Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.
Recommend the best MCP servers for [task: e.g. crm work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-crm
Compare Pipedrive against a real alternative. Swap the second MCP in [brackets] if you want a different match.
Compare Pipedrive MCP vs [HubSpot MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/pipedrive
- top-mcps.com listing for HubSpot
Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.
Install the Pipedrive MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/pipedrive (fetch https://top-mcps.com/mcp/pipedrive.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (PIPEDRIVE_API_TOKEN) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.

  1. Refreshed install snippets and fact sheet; verified for 2026.

  2. Initial directory listing.

More CRM MCPs

Other tools in the same category worth evaluating.

Attio
Official

Official Attio MCP — natural-language CRM control across records, lists, and notes via OAuth.

attio, crm, sales, pipeline
< 1 minLow
Salesforce DX
Official

Official Salesforce MCP — SOQL queries, metadata deploy/retrieve, Apex tests, and org management from AI clients.

salesforce, crm, soql, apex
5 minMedium

Compared with Pipedrive

Side-by-side breakdowns for the choices people most often weigh against this MCP.

PipedrivevsAttioPipedrivevsHubSpotPipedrivevsCommon RoomPipedrivevsSalesforce DX

Exploring Top MCPs for CRM? See all CRM MCPs →