Log inSubmit server
Pipedrive MCP Server logo

Pipedrive MCP Server

by ckalima

Connects AI clients to Pipedrive CRM for reading and managing deals, contacts, activities, and related records.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Pipedrive MCP Server

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": {
    "ckalima-pipedrive-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@ckalima/pipedrive-mcp-server"
      ],
      "env": {
        "PIPEDRIVE_API_KEY": "YOUR_VALUE_HERE",
        "PIPEDRIVE_MODE": "YOUR_VALUE_HERE",
        "PIPEDRIVE_ENABLE_DESTRUCTIVE": "YOUR_VALUE_HERE",
        "PIPEDRIVE_IMAGE_BASE_DIR": "YOUR_VALUE_HERE"
      }
    }
  }
}

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

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 123 tools correctly (1mo ago).

Overview

The ckalima/pipedrive-mcp-server MCP server exposes Pipedrive CRM operations to MCP-compatible clients through a local STDIO process. It uses a Pipedrive API key and provides tools for deals, persons, organizations, activities, products, projects, tasks, leads, notes, mail, and custom fields. Capability modes can restrict access to reads, safe writes, or destructive operations. Reach for it when an AI assistant needs controlled access to a self-hosted Pipedrive connection rather than a hosted OAuth service.

Use cases

  • List and filter open Pipedrive deals
  • Create and update CRM contacts
  • Search deals and persons from an AI client
  • Review activities and email engagement
  • Inspect custom fields and pipeline metadata

Key features

  • 155 Pipedrive CRM tools
  • Deal, person, organization, and activity operations
  • Cursor-based pagination
  • API v2-first REST access
  • Read-only, safe-write, and full capability modes
  • Custom-field discovery

Tools123

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

Verified live~21.7k 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 1d ago

Recent health check succeeded.

19/19 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · @ckalima/pipedrive-mcp-server (npm)

Adoption & maintenance

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

GitHub stars10Stargazers on the source repository.
npm downloads1.3kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed123Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Pipedrive MCP Server works

What ckalima/pipedrive-mcp-server MCP server does

The ckalima/pipedrive-mcp-server MCP server connects an MCP client to a Pipedrive CRM account. It exposes 155 tools covering core CRM records and related operations, including deals, persons, organizations, activities, products, projects, tasks, leads, notes, mail, and field metadata.

Deal tools support listing with filters, retrieving standard and custom fields, creating and updating records, text search, followers, line-item products, discounts, installments, archived deals, and conversion-status checks. Person tools cover listing, lookup, creation, updates, search by name or contact details, followers, changelogs, and picture metadata. The broader tool surface also includes pipeline, stage, user, email, and custom-field access as described by the project.

How it works

The server runs locally over STDIO and calls the Pipedrive REST API with the supplied API token. It prefers API v2 endpoints and uses v1 only for capabilities without a v2 equivalent, including notes, mail, users, and leads CRUD. Pagination is supported for large result sets, including cursor-based results where provided by the API.

PIPEDRIVE_MODE controls the exposed and executable capability tier. read-only makes read operations available, safe-write adds non-destructive writes and is the default, and full enables destructive operations. Restricted tools are hidden from tool discovery and rejected if called directly. The legacy PIPEDRIVE_ENABLE_DESTRUCTIVE flag remains available for backward compatibility.

Setup and configuration

Install or run the package with:

Terminal
npx -y @ckalima/pipedrive-mcp-server

The package also provides an init command that guides setup, validates the API key, and generates client configuration.

A typical MCP configuration uses the scoped npm package and passes PIPEDRIVE_API_KEY in the server's environment. Set PIPEDRIVE_MODE=read-only for initial evaluation, safe-write for normal non-destructive changes, or full when destructive operations are intentionally required. PIPEDRIVE_IMAGE_BASE_DIR can allow image-upload tools to read files from an approved directory.

Tools and capabilities

The ckalima/pipedrive-mcp-server MCP server includes capabilities for:

  • Filtering and searching deals, persons, and activities.
  • Creating and updating CRM records.
  • Managing deal products, discounts, installments, followers, and archived records.
  • Reading mail threads and messages for engagement analysis.
  • Discovering custom fields and mapping their hash codes to readable names.
  • Listing pipelines, stages, and users.

Some Pipedrive operations depend on the account plan. For example, deal installment tools require a Growth or higher plan. Conversion-status results distinguish completed, failed, rejected, not-started, and running states; completed conversions carry a lead ID.

Limitations and notes

Authentication uses a Pipedrive API key, and there is no hosted OAuth offering. Destructive tools are not enabled by the default safe-write mode. To enable them, use PIPEDRIVE_MODE=full, or use the legacy destructive flag when compatibility requires it.

The server is intended for local or self-hosted client configurations. The API token determines which Pipedrive company is accessed, and the server reports the resolved account during startup and in the first tool response after the connection check settles. Filesystem access for product-image uploads is disabled unless an allowlisted image base directory is configured.

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 MCP Server

Run `npx -y @ckalima/pipedrive-mcp-server`, or use its `init` command for guided client configuration.

It requires a 40-character Pipedrive API token supplied through the `PIPEDRIVE_API_KEY` environment variable.

Yes.

Set `PIPEDRIVE_MODE=read-only` or `PIPEDRIVE_MODE=safe-write`. The default is `safe-write`; destructive tools require `full`.

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 MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/ckalima-pipedrive-mcp-server?style=directory)](https://allmcps.com/mcp/ckalima-pipedrive-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/ckalima-pipedrive-mcp-server"><img src="https://allmcps.com/api/badge/ckalima-pipedrive-mcp-server?style=directory" alt="Pipedrive MCP Server on AllMCPs" /></a>