Two ways to connect
Pipedrive offers both an MCP connection and OAuth. MCP is the preferred path for most workflows.- Pipedrive MCP (recommended). Broad CRM access through Pipedrive’s hosted MCP server, with permission-aware tools. See Connect with MCP.
- Pipedrive OAuth. The original sign-in integration. See Connect with OAuth.
What the agent can do
Read deals
Pull deals and where they sit in the pipeline.
Manage contacts
Work with people and organizations.
Update records
Change deal stage, value, or contact details.
Log activity
Record notes, calls, and follow-ups.
Example agent tasks
Connect with MCP
1
Add the Pipedrive connection
From the agent’s connections, choose Pipedrive. The platform connects you through Pipedrive’s hosted MCP server.
2
Sign in to Pipedrive
A connect card appears. Sign in to your Pipedrive account and approve access. The MCP inherits your Pipedrive user permissions.
3
The agent gets to work
It can now read and update deals, contacts, and activity in your Pipedrive CRM.
Connect with OAuth
What you share
During the connect flow you authorize what the agent can reach. It works only within what you grant. As with every connection, the underlying token is handled securely and never exposed to the model. See Permissioning.1
Authorize Pipedrive for the agent
From the agent’s connections, choose Pipedrive and sign in.
2
Approve the access
Confirm what the agent can reach. You can change this later.
3
The agent gets to work
It works through the secure proxy, within what you granted.
Learn more
Pipedrive API docs
The full reference for what’s possible.
How credentials stay safe
The proxy model that keeps tokens out of the agent’s reach.