Pipedrive MCP Server
An MCP (Model Context Protocol) server for Pipedrive CRM integration with Claude Code and Claude Desktop. Query, create, and update CRM data directly from your AI assistant.
Why this server
- API v2-first. Every entity uses Pipedrive's v2 REST API where it exists; v1 is used only for the capabilities that have no v2 equivalent (notes, mail, users, and leads CRUD). See API Versioning.
- Contract-tested against the real OpenAPI spec. Request params, request bodies, and response shapes are checked against the vendored Pipedrive OpenAPI v2 definition (
docs/api/openapi-v2.yaml) intests/contract/, so the v2 tools can't silently drift from the documented API. - Live-smoke verified. The tool surface is broadly exercised against a real Pipedrive account (
scripts/smoke-coverage.ts), with only API-unseedable surfaces (e.g. mail threads, project templates) left to manual checks. Coverage includes plan-gated endpoints such as Growth+ deal installments (scripts/smoke-installments.ts). Key write smokes (e.g. the taskis_doneflag) assert the field value actually changed on the wire, not just a 200. - Server-enforced capability modes.
PIPEDRIVE_MODEpicks a safety tier —read-only,safe-write(the default: reads + non-destructive writes), orfull— and out-of-mode tools are both hidden fromtools/listand refused if called directly. Deletes, conversions, and other irreversible writes (🔒 in the tool table) requirefull, so the server is read-and-create only out of the box. Every tool also carries MCP annotations (readOnlyHint/destructiveHint/idempotentHint) so policy-aware clients can tell reads from writes from deletes. See Capability modes. - MIT licensed, published with npm build provenance.






