Pipedrive MCP Server

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:

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 Pipedrive API token is required; the README describes obtaining it from Pipedrive under Settings, Personal preferences, and API.

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

Transport is STDIO only; the README notes that Streamable HTTP is planned. 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.