npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@iflow-mcp/willdent-pipedrive-mcp-server

v1.0.4

Published

Model Context Protocol server for Pipedrive API integration

Readme

Pipedrive MCP Server

This is a Model Context Protocol (MCP) server that connects to the Pipedrive API v2. It allows you to expose Pipedrive data and functionality to LLM applications like Claude.

Features

  • Read-only access to Pipedrive data
  • Exposes deals, persons, organizations, and pipelines
  • Includes all fields including custom fields
  • Predefined prompts for common operations
  • Docker support with multi-stage builds
  • JWT authentication support
  • Built-in rate limiting for API requests
  • Advanced deal filtering (by owner, status, date range, value, etc.)

Setup

Standard Setup

  1. Clone this repository
  2. Install dependencies:
    npm install
  3. Create a .env file in the root directory with your configuration:
    PIPEDRIVE_API_TOKEN=your_api_token_here
    PIPEDRIVE_DOMAIN=your-company.pipedrive.com
  4. Build the project:
    npm run build
  5. Start the server:
    npm start

Docker Setup

Option 1: Using Docker Compose (standalone)

  1. Copy .env.example to .env and configure your settings:
    PIPEDRIVE_API_TOKEN=your_api_token_here
    PIPEDRIVE_DOMAIN=your-company.pipedrive.com
    MCP_TRANSPORT=sse  # Use SSE transport for Docker
    MCP_PORT=3000
  2. Build and run with Docker Compose:
    docker-compose up -d
  3. The server will be available at http://localhost:3000
    • SSE endpoint: http://localhost:3000/sse
    • Health check: http://localhost:3000/health

Option 2: Using Pre-built Docker Image

Pull and run the pre-built image from GitHub Container Registry:

For SSE transport (HTTP access):

docker run -d \
  -p 3000:3000 \
  -e PIPEDRIVE_API_TOKEN=your_api_token_here \
  -e PIPEDRIVE_DOMAIN=your-company.pipedrive.com \
  -e MCP_TRANSPORT=sse \
  -e MCP_PORT=3000 \
  ghcr.io/juhokoskela/pipedrive-mcp-server:main

For stdio transport (local use):

docker run -i \
  -e PIPEDRIVE_API_TOKEN=your_api_token_here \
  -e PIPEDRIVE_DOMAIN=your-company.pipedrive.com \
  ghcr.io/juhokoskela/pipedrive-mcp-server:main

Option 3: Integrating into Existing Project

Add the MCP server to your existing application's docker-compose.yml:

services:
  # Your existing services...

  pipedrive-mcp-server:
    image: ghcr.io/juhokoskela/pipedrive-mcp-server:main
    container_name: pipedrive-mcp-server
    restart: unless-stopped
    ports:
      - "3000:3000"
    environment:
      - PIPEDRIVE_API_TOKEN=${PIPEDRIVE_API_TOKEN}
      - PIPEDRIVE_DOMAIN=${PIPEDRIVE_DOMAIN}
      - MCP_TRANSPORT=sse
      - MCP_PORT=3000
      - PIPEDRIVE_RATE_LIMIT_MIN_TIME_MS=${PIPEDRIVE_RATE_LIMIT_MIN_TIME_MS:-250}
      - PIPEDRIVE_RATE_LIMIT_MAX_CONCURRENT=${PIPEDRIVE_RATE_LIMIT_MAX_CONCURRENT:-2}
    healthcheck:
      test: ["CMD", "wget", "--no-verbose", "--tries=1", "--spider", "http://localhost:3000/health", "||", "exit", "1"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 10s
    logging:
      driver: "json-file"
      options:
        max-size: "10m"
        max-file: "3"

Then add the required environment variables to your .env file.

Environment Variables

Required:

  • PIPEDRIVE_API_TOKEN - Your Pipedrive API token
  • PIPEDRIVE_DOMAIN - Your Pipedrive domain (e.g., your-company.pipedrive.com)

Optional (JWT Authentication):

  • MCP_JWT_SECRET - JWT secret for authentication
  • MCP_JWT_TOKEN - JWT token for authentication
  • MCP_JWT_ALGORITHM - JWT algorithm (default: HS256)
  • MCP_JWT_AUDIENCE - JWT audience
  • MCP_JWT_ISSUER - JWT issuer

When JWT authentication is enabled, all SSE requests (/sse and the message endpoint) must include an Authorization: Bearer <token> header signed with the configured secret.

Optional (Rate Limiting):

  • PIPEDRIVE_RATE_LIMIT_MIN_TIME_MS - Minimum time between requests in milliseconds (default: 250)
  • PIPEDRIVE_RATE_LIMIT_MAX_CONCURRENT - Maximum concurrent requests (default: 2)

Optional (Transport Configuration):

  • MCP_TRANSPORT - Transport type: stdio (default, for local use) or sse (for Docker/HTTP access)
  • MCP_PORT - Port for SSE transport (default: 3000, only used when MCP_TRANSPORT=sse)
  • MCP_ENDPOINT - Message endpoint path for SSE (default: /message, only used when MCP_TRANSPORT=sse)

Using with Claude

To use this server with Claude for Desktop:

  1. Configure Claude for Desktop by editing your claude_desktop_config.json:
{
  "mcpServers": {
    "pipedrive": {
      "command": "node",
      "args": ["/path/to/pipedrive-mcp-server/build/index.js"],
      "env": {
        "PIPEDRIVE_API_TOKEN": "your_api_token_here",
        "PIPEDRIVE_DOMAIN": "your-company.pipedrive.com"
      }
    }
  }
}
  1. Restart Claude for Desktop
  2. In the Claude application, you should now see the Pipedrive tools available

Available Tools

  • get-users: Get all users/owners from Pipedrive to identify owner IDs for filtering
  • get-deals: Get deals with flexible filtering options (search by title, date range, owner, stage, status, value range, etc.)
  • get-deal: Get a specific deal by ID (including custom fields)
  • get-deal-notes: Get detailed notes and custom booking details for a specific deal
  • search-deals: Search deals by term
  • get-persons: Get all persons from Pipedrive (including custom fields)
  • get-person: Get a specific person by ID (including custom fields)
  • search-persons: Search persons by term
  • get-organizations: Get all organizations from Pipedrive (including custom fields)
  • get-organization: Get a specific organization by ID (including custom fields)
  • search-organizations: Search organizations by term
  • get-pipelines: Get all pipelines from Pipedrive
  • get-pipeline: Get a specific pipeline by ID
  • get-stages: Get all stages from all pipelines
  • search-leads: Search leads by term
  • search-all: Search across all item types (deals, persons, organizations, etc.)

Available Prompts

  • list-all-deals: List all deals in Pipedrive
  • list-all-persons: List all persons in Pipedrive
  • list-all-pipelines: List all pipelines in Pipedrive
  • analyze-deals: Analyze deals by stage
  • analyze-contacts: Analyze contacts by organization
  • analyze-leads: Analyze leads by status
  • compare-pipelines: Compare different pipelines and their stages
  • find-high-value-deals: Find high-value deals

License

MIT