Pipedrive MCP Server

Created By
WillDenta year ago
Overview

what is Pipedrive MCP Server?

Pipedrive MCP Server is a Model Context Protocol (MCP) server that connects to Pipedrive CRM using the official Pipedrive API v2 Node.js client, allowing AI assistants to interact with Pipedrive data.

how to use Pipedrive MCP Server?

To use the server, clone the repository, install dependencies, configure environment variables with your Pipedrive API token, and start the server. You can connect various MCP-compatible clients to interact with your Pipedrive data.

key features of Pipedrive MCP Server?

  • Full integration with Pipedrive API v2
  • MCP-compatible tools for managing deals, persons, organizations, activities, pipelines, notes, and users
  • Comprehensive error handling and logging

use cases of Pipedrive MCP Server?

  1. Automating CRM tasks with AI assistants.
  2. Fetching and managing Pipedrive data programmatically.
  3. Integrating Pipedrive with other applications via MCP protocol.

FAQ from Pipedrive MCP Server?

  • What is required to run the server?

You need Node.js 16.x or higher, npm or yarn, and a Pipedrive account with an API token.

  • Can I use this server with any MCP-compatible client?

Yes! The server is designed to work with any MCP-compatible client, including Claude and Cursor.

  • Is there a way to test the server?

Yes! You can use the MCP Inspector tool for testing your server's tools and resources.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
WillDent
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

2 days ago
Payai X402 Tools

16 hours ago
Payai X402 Tools

16 hours ago
Payai X402 Tools

16 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago