Log inSubmit server
Pipedrive logo

Pipedrive

Pipedrive MCP Pack — wraps the Pipedrive REST API v1

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Pipedrive

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "pipedrive": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-pipedrive"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y @pipeworx/mcp-pipedrive

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 2d ago.

Overview

Tools5

What Pipedrive lets your agent do. Expand a tool for its parameters.

Self-reported~181 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

8/8 checks healthy over the last 51d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 3d ago via OSV.dev · @pipeworx/mcp-pipedrive (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads467Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.
Tools exposed5Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

From the project README

mcp-pipedrive

Pipedrive MCP Pack — wraps the Pipedrive REST API v1

Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.

Tools

ToolDescription
pipedrive_list_dealsView all deals in your pipeline. Returns deal IDs, titles, values, stages, and owners. Use pipedrive_get_deal for full details on a specific deal.
pipedrive_get_dealGet complete details for a specific deal (by ID). Returns title, value, stage, probability, owner, associated contacts, and timeline.
pipedrive_list_personsView all contacts in your CRM. Returns names, email addresses, phone numbers, and associated organizations and deals.
pipedrive_get_personGet full contact details by ID. Returns name, emails, phones, organization, associated deals, and custom fields.
pipedrive_searchSearch deals, contacts, organizations, products, or files by keyword. Returns matching records with IDs and basic info.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

config.json
{
  "mcpServers": {
    "pipedrive": {
      "url": "https://gateway.pipeworx.io/pipedrive/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/pipedrive/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

config.json
{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1683+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/pipedrive_list_deals. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

config.json
{
  "mcpServers": {
    "pipedrive": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-pipedrive"]
    }
  }
}

Or run it directly to confirm it starts:

Terminal
npx -y @pipeworx/mcp-pipedrive

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

Code
ask_pipeworx({ question: "your question about Pipedrive data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Pipedrive

Pipedrive is an MCP server that wraps the Pipedrive REST API v1, letting MCP-compatible clients access deal and contact data through tools for listing and retrieving records. It can also search deals, contacts, organizations, products, and files by keyword, using either a Pipeworx gateway connection or standalone stdio package.

Connect an MCP client to https://gateway.pipeworx.io/pipedrive/mcp for the Pipeworx gateway, or run npx -y @pipeworx/mcp-pipedrive as a local stdio server without a gateway account.

The server provides tools to list and retrieve deals, list and retrieve people, and search Pipedrive records. Its tools include pipedrive_list_deals, pipedrive_get_deal, pipedrive_list_persons, pipedrive_get_person, and pipedrive_search.

Use pipedrive_search to find deals, contacts, organizations, products, or files by keyword. The tool returns matching records with their IDs and basic information.

Related MCP servers

All in Customer Data Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPipedrive AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/pipedrive?style=directory)](https://allmcps.com/mcp/pipedrive)
HTML Embed
<a href="https://allmcps.com/mcp/pipedrive"><img src="https://allmcps.com/api/badge/pipedrive?style=directory" alt="Pipedrive on AllMCPs" /></a>