pipedrive
MCP server from WillDent/pipedrive-mcp-server
claude mcp add --transport stdio willdent-pipedrive-mcp-server node /path/to/pipedrive-mcp-server/build/index.js \ --env PIPEDRIVE_DOMAIN="<your-company.pipedrive.com>" \ --env PIPEDRIVE_API_TOKEN="<your_pipedrive_api_token>"
How to use
This MCP server provides read-only access to Pipedrive data via the MCP (Model Context Protocol) interface. It exposes entities such as deals, persons, organizations, and pipelines, including custom fields, and offers predefined prompts and tools to query and filter Pipedrive records. The server supports optional JWT authentication and rate limiting, and can be consumed over SSE (HTTP) or local stdio transports depending on deployment.
To use it with Claude or other LLM tools, configure your client to point at the MCP server and supply the required connection details (token, domain, transport as needed). The available tools let you fetch lists of users/owners, retrieve deals with rich filtering, obtain specific deals or related notes, search across deals and people, and retrieve pipelines and stages. This enables structured queries like filtering deals by owner, stage, date range, or value, and retrieving related notes and custom fields for precise context.
How to install
Prerequisites:
- Node.js and npm installed
- Git to clone the repository
- Pipedrive API token and domain to access the API
-
Clone the repository: git clone https://github.com/your-org/w dent-pipedrive-mcp-server.git cd willdent-pipedrive-mcp-server
-
Install dependencies: npm install
-
Create a .env file (or configure environment variables) with your Pipedrive credentials: PIPEDRIVE_API_TOKEN=your_api_token_here PIPEDRIVE_DOMAIN=your-company.pipedrive.com
-
Build the project (if required by the project setup): npm run build
-
Start the server (development/local): npm start
-
Verify the server is running (example): curl http://localhost:3000/health
Docker deployment (optional):
- Use the Docker instructions in the README to run via a container, ensuring MCP_TRANSPORT and port configuration are set as needed.
Additional notes
Notes:
- Ensure the PIPEDRIVE_API_TOKEN has read-only access sufficient for the tools you plan to use.
- If enabling JWT authentication, set MCP_JWT_SECRET and related env vars; all SSE requests must include a Bearer token when enabled.
- When using Docker, MCP_TRANSPORT should be set to sse for HTTP access; MCP_PORT controls the SSE endpoint port.
- Rate limiting can help prevent hitting Pipedrive API limits; tune PIPEDRIVE_RATE_LIMIT_MIN_TIME_MS and PIPEDRIVE_RATE_LIMIT_MAX_CONCURRENT as appropriate.
- The available tools and prompts cover typical operations like listing and filtering deals, persons, organizations, and pipelines, as well as analyzing and comparing data across items.
- If integrating with Claude Desktop, point Claude’s mcpServers configuration to this server and restart Claude to load the tools.
Related MCP Servers
iterm
A Model Context Protocol server that executes commands in the current iTerm session - useful for REPL and CLI assistance
mcp
Octopus Deploy Official MCP Server
furi
CLI & API for MCP management
editor
MCP Server for Phaser Editor
DoorDash
MCP server from JordanDalton/DoorDash-MCP-Server
mcp
MCP сервер для автоматического создания и развертывания приложений в Timeweb Cloud