HODORPipedrive × Hodor
Pipedrive MCP, through Hodor
Pipedrive doesn't have an official MCP server. Hodor exposes the full Pipedrive API as Model Context Protocol tools — with identity, policy, audit, and a kill switch — so your AI agents can safely create deals, update contacts, and move pipeline.
Pipedrive is a sales-focused CRM used by SMBs and revenue teams to manage pipelines, deals, and outreach.
The gap
Why Pipedrive doesn't have an MCP — yet
Pipedrive has a full REST API, but no official Model Context Protocol server — community MCPs vary wildly in security and coverage.
Handing a raw Pipedrive API token to an agent means an over-scoped credential with read-write access to every deal, contact, and pipeline.
Without policy enforcement, a hallucinating sales copilot can update the wrong deal stage, mass-email prospects, or delete contacts — with no audit trail to trace it.
How it works
Pipedrive as MCP, in three steps
- STEP 01
Connect Pipedrive to Hodor
Authenticate once with your Pipedrive account. Hodor stores the credential securely and never exposes it to agents.
- STEP 02
Hodor exposes the API as MCP tools
Every Pipedrive endpoint becomes a typed MCP tool. Scope per agent, set policy, and define rate limits at the gateway.
- STEP 03
Agents call MCP through Hodor
Any MCP-compatible agent — Claude, Cursor, Dust, n8n, custom — connects to Hodor. Every call is checked, logged, and attributed.
Tool catalog
What your agents can do
A subset of the Pipedrive tools Hodor exposes as MCP. Enable, disable, or constrain each one per agent identity.
- pipedrive_search_deals
- pipedrive_create_deal
- pipedrive_update_deal_stage
- pipedrive_add_activity
- pipedrive_get_contact
- pipedrive_create_note
- pipedrive_list_pipelines
- pipedrive_get_organization
- pipedrive_update_contact
- pipedrive_list_activities
Built for production
Identity, policy, audit — by default
The same controls Hodor applies to every integration apply to Pipedrive: per-agent identity, scoped tools, real-time policy enforcement, full audit logs, and a global kill switch.
Agent identity
Every agent gets a unique, revocable identity. Every call is attributed.
Scoped policy
Fine-grained tool access, rate limits, and field-level restrictions enforced at the gateway.
Full audit trail
Every call logged with payload, identity, and policy outcome — SOC 2 / ISO 27001 ready.
Kill switch
Revoke any agent in one click. Hodor blocks all downstream calls instantly.
Common patterns
What teams build with Pipedrive + Hodor
Sales copilot that updates the pipeline
After a call, the agent reads the transcript, updates deal stage, logs an activity, and creates follow-up tasks — only on deals owned by the rep it represents.
Outbound enrichment agent
Pull contacts from a data provider, dedupe against Pipedrive, and create new leads — with a hard cap of 50 inserts per hour and no delete permission.
Forecast & hygiene bot
Nightly agent scans stale deals, flags missing close dates, and posts a Slack summary — read-only on the Pipedrive side, no write access at all.
Closed-won automation
When a deal flips to Won, trigger downstream agents in your stack. Hodor attributes every onward action back to the originating agent identity.
FAQ
Pipedrive MCP, answered
Does Pipedrive have an official MCP server?
+
Not as of 2026. Pipedrive ships a REST API and a Marketplace, but no native Model Context Protocol server. Hodor bridges the gap by exposing the Pipedrive API as MCP tools that any MCP-compatible client (Claude, Cursor, Dust, n8n, custom agents) can call.
Is the Pipedrive MCP gateway secure?
+
Yes. Hodor sits as a proxy between every agent and the Pipedrive API. Each agent has a unique identity, scoped tool access, and rate limits. Every call is logged with full payload context, and you can revoke any agent in one click.
Which Pipedrive endpoints are exposed?
+
Deals, contacts, organizations, activities, notes, pipelines, products, and users — both reads and writes. You decide per-agent which tools are available, with optional policy constraints on each (e.g. read-only, owner-scoped, rate-limited).
Can I restrict an agent to certain pipelines or users?
+
Yes. Hodor policies let you scope an agent's Pipedrive access by pipeline, owner, deal stage, or any custom field — enforced at the gateway before the call ever reaches Pipedrive.
How do I get started?
+
Book a 20-minute demo. We'll set up your Pipedrive connection, scope the tools your agents need, and walk through audit logs and policy controls live.
Ship your Pipedrive agents — safely.
Identity, policy, and audit for every Pipedrive call your agents make. Set up in under an hour with a Hodor engineer on the call.
- 20-minute demo
- No credit card
- SOC 2-ready logs