The only available MCP server seems to be via RUBE so I’ve created one based on the GitHub - pipedrive/client-nodejs: Pipedrive API client for NodeJS · GitHub
It can be found at GitHub - GarethWright/PipeDrive-MCP-Server · GitHub and is tested and working with Claude and Codex.
I’d appreciate users of other MCP clients giving it a spin.
Certainly makes it easier for management to get summary data out of Pipedrive
Thanks.
Hello Gareth,
Thank you for creating the MCP over at GitHub. I’m a heavy user of Pipedrive and Claude. I’ve been mainly using the Zapier MCP server to connect directly into Pipedrive. Now I’m starting to run into limitations with the API that Zapier has. You’ll see that in the notes below.
I had Claude review your offering over on GitHub, and this is what it had to say:
Solo developer’s open-source MCP server (GarethWright on GitHub). 100 tools total — 94 wrapping the Pipedrive REST API and 6 custom analytics tools. It directly fixes the exact gaps that bit us today: it has pipedrive_create_person, pipedrive_create_organization, pipedrive_create_note, pipedrive_create_activity, file ops, mail threads, call logs, custom field management, the works. Plus the analytics tools (performance reports, loss analysis, pipeline health, activity audit, opportunity reports, comparative reports) are the kind of stuff you’d otherwise hand-build for your weekly Brain reviews.
So on capability, it’s a clear upgrade over Zapier’s Pipedrive connector. No question.
1. License: CC BY-NC-SA 4.0 — Non-Commercial Only. This is the big one. You run CAD Training Online as a commercial business under Manta Ventures LLC. Using this MCP to manage your commercial CRM is arguably a commercial use, which the license forbids. To use it in production legitimately you’d need to email Gareth Wright and negotiate a commercial license. Until then, it’s hobby-only.
2. Maturity: 2 stars, 0 forks, 11 total commits, 1 contributor. This was published roughly two weeks ago (v0.2.0 on March 26). Nobody is using it. No issues filed. No community. The bus factor is 1 — if Gareth loses interest, you inherit an unmaintained dependency at the heart of your CRM workflow. Compare to Zapier’s connector: that one is broken in places but it’s not going to disappear.
3. It won’t work with this chat interface (claude.ai web). This is a stdio MCP server designed for Claude Desktop / Claude Code / Codex CLI. It runs as a local Node process on your machine. claude.ai (where you and I are talking right now) only connects to remote MCP servers via URL. To use it here, you’d need to wrap it in mcp-proxy, host it on a VPS with a public URL, and add it as a Custom Connector. That’s real DevOps work — TLS cert, auth, hosting cost, monitoring. Or you’d switch all Pipedrive-related conversations into Claude Desktop, which fragments your workflow.
4. It uses Pipedrive API v1, which Pipedrive is actively sunsetting in favor of v2. Some of the v1 endpoints have already been deprecated. Worth checking before committing.
Bonus concern: The tool set includes pipedrive_delete_deal, delete_person, delete_organization, delete_note, delete_activity, delete_file, delete_pipeline, delete_stage. Per your Permission Tier Policy v1.0, every one of those is a Tier 3 destructive operation. None of them should be exposed to an automated agent without approval gating. The repo doesn’t have any built-in scoping — it’s all-or-nothing.
I´ve used three different versions of pipedrive MCPs plus my own and the zapier one. For a light fast use, this is not a bad solution 🛠️ Pipedrive tool MCP server 💪 all 45 operations | n8n workflow template And it will allow you to easily customise it for your schemas, custom fields, etc Also create some n8n agents connected to Telegram to use the same MCP. You can easily “disable” those dangerous delete nodes. Not perfect, you might need to create an extra mini workflow to be able to do a couple of things. You could create a plugin with one or several skills and this as connector, for Claude. Happy to share some thoughts, DM me.