pipedriver
MCP server for Pipedrive API v2, enabling management of deals, persons, organizations, products, activities, and pipelines through natural language in MCP clients like Cursor and Claude Desktop.
README
pipedriver
MCP server for the Pipedrive API v2. Expose Pipedrive (deals, persons, organizations, products, activities, pipelines, and more) as tools to any Model Context Protocol client—Cursor, Claude Desktop, and others.
Built with the official Pipedrive JavaScript SDK and the MCP TypeScript SDK.
Quick start (npx)
No install. Run the server with your Pipedrive API token:
PIPEDRIVE_API_KEY=your_api_token npx pipedriver
Then point your MCP client at this command. Example for Cursor (Settings → MCP → Edit config):
{
"mcpServers": {
"pipedriver": {
"command": "npx",
"args": ["-y", "pipedriver"],
"env": {
"PIPEDRIVE_API_KEY": "your_api_token"
}
}
}
}
Get an API token in Pipedrive → Settings → API.
Usage
How it runs
The server uses stdio transport: your MCP client starts it as a subprocess and talks over stdin/stdout. No HTTP server or port.
Option A: npx (recommended for trying it out)
npx -y pipedriver
Set PIPEDRIVE_API_KEY in the environment (or in your MCP config env, as in the example above).
Option B: Install and run
npm install -g pipedriver
# or: yarn global add pipedriver
export PIPEDRIVE_API_KEY=your_api_token
pipedriver
Option C: From a local clone (development)
git clone https://github.com/vaibhavpandeyvpz/pipedriver.git
cd pipedriver
yarn install
export PIPEDRIVE_API_KEY=your_api_token
yarn dev
In your MCP config, use the path to the repo:
{
"mcpServers": {
"pipedriver": {
"command": "node",
"args": ["/path/to/pipedriver/dist/index.js"],
"env": { "PIPEDRIVE_API_KEY": "your_api_token" }
}
}
}
Or without building (runs TypeScript with tsx):
{
"mcpServers": {
"pipedriver": {
"command": "npx",
"args": ["tsx", "/path/to/pipedriver/src/index.ts"],
"env": { "PIPEDRIVE_API_KEY": "your_api_token" }
}
}
}
Tool naming
Tools follow pipedrive_<domain>_<action>, e.g. pipedrive_deals_list, pipedrive_persons_add. Arguments and request bodies match the Pipedrive API v2 (filters, sort, pagination, and JSON bodies where applicable).
Tools overview
| Domain | Examples |
|---|---|
| Activities | add, delete, list, get, update |
| Activity fields | get, list (metadata) |
| Deals | add, delete, list, get, update, search; products (add/delete/update/many); followers; convert to lead; additional discounts; installments |
| Deal fields | get, list (metadata) |
| Item search | search, search by field |
| Leads | search, convert to deal, get conversion status |
| Organizations | add, delete, list, get, update, search; followers |
| Organization fields | get, list (metadata) |
| Persons | add, delete, list, get, update, search; picture; followers |
| Person fields | get, list (metadata) |
| Pipelines | add, delete, list, get, update |
| Products | add, delete, list, get, update, search; followers; duplicate; variations; image |
| Product fields | get, list (metadata) |
| Stages | add, delete, list, get, update |
| Users | get followers |
Each tool’s input schema in your MCP client describes parameters and optional fields.
Development
Prerequisites
- Node.js 18+
- Yarn (or npm)
Setup
git clone https://github.com/vaibhavpandeyvpz/pipedriver.git
cd pipedriver
yarn install
Create a .env or export your token:
export PIPEDRIVE_API_KEY=your_api_token
Commands
| Command | Description |
|---|---|
yarn dev |
Run server from source (no build) via tsx |
yarn build |
Compile TypeScript to dist/ |
yarn start |
Run compiled server (node dist/index.js) |
yarn test |
Run Jest tests (start server, connect, list tools) |
Project layout
src/– Server entry, MCP server setup, Pipedrive client wrappersrc/tools/– Tool handlers per domain (deals, persons, products, etc.)src/schemas/– Zod schemas for request bodiestests/– Integration tests (Jest)
Deployment
This server is not a long-lived HTTP service. It is started by your MCP client when needed and communicates over stdio.
- Production use = your MCP client (e.g. Cursor, Claude Desktop) runs
npx pipedriverorpipedriverwithPIPEDRIVE_API_KEYset. No extra deployment step. - Publishing: The package is published to npm via GitHub Actions on version tags (
v*). See .github/workflows/publish-npm.yml.
License
MIT © Vaibhav Pandey
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.