Connect your AI Agents to Pipedrive in minutes
Available tools
list_activities
Retrieve activities with filtering and pagination. Filter by owner, type (call/meeting/task), completion status, or date range. Returns activity objects with subjects, due dates, and linked deals/contacts. Use to view tasks or find overdue items.
get_activity
Retrieve detailed information for a specific activity by its ID. Returns complete activity data including subject, type, due date/time, duration, associated deal/contact/organization, completion status, participants, and notes. Use list_activities to find valid activity IDs. Essential for viewing full activity details or checking activity status before updates.
create_activity
Create a new activity (call, meeting, task, deadline, email, lunch) with due dates/times, assigned users, linked deals/contacts/organizations, duration, and participants. Returns complete activity object with ID. Use list_activity_types to see available types. Essential for task management and scheduling follow-ups.
update_activity
Update activity properties: subject, type, due date/time, completion status, assigned user, associated records, duration, location, notes. Partial updates supported. Returns updated activity object. Commonly used to mark done, reschedule, or update details.
delete_activity
Permanently delete an activity from Pipedrive. Cannot be undone. Removes from all associated deals, contacts, and calendars. Consider marking as done instead to maintain history. Returns success confirmation.
list_activity_types
Retrieve all activity types (call, meeting, task, deadline, email, lunch, custom types) with names, icons, colors, and IDs. Use to discover valid type values before creating/updating activities. Essential for correct type assignment.
list_deal_fields
Retrieve all custom field definitions for deals including field names, types, options, and IDs. Returns metadata about custom fields configured in your Pipedrive account. Use this to discover available custom fields before creating or updating deals, understand field types and valid values, or build dynamic forms.
list_person_fields
Retrieve all custom field definitions for persons/contacts including field names, types, options, and IDs. Returns metadata about custom fields configured for contacts. Use this to discover available custom fields before creating or updating persons, understand field types and valid values, or build dynamic contact forms.
list_organization_fields
Retrieve all custom field definitions for organizations/companies including field names, types, options, and IDs. Returns metadata about custom fields configured for organizations. Use this to discover available custom fields before creating or updating organizations, understand field types and valid values, or build dynamic company forms.
list_activity_fields
Retrieve all custom field definitions for activities including field names, types, options, and IDs. Returns metadata about custom fields configured for activities. Use this to discover available custom fields before creating or updating activities, understand field types and valid values, or build dynamic activity forms.
list_deals
Retrieve deals with filtering and pagination. Filter by owner, stage, status (open/won/lost), or custom filters. Returns deal objects with contacts, organizations, values, and custom fields. Use to analyze pipeline health or find deals by criteria.
get_deal
Retrieve detailed deal information by ID. Returns complete data: title, value, currency, stage, pipeline, associated person/organization, custom fields, activity counts, metadata. Use list_deals to find valid IDs. Essential for viewing details or checking status.
create_deal
Create a new deal with title, value, owner, stage, and associated contacts/organizations. Supports custom fields, pipeline assignment, probability tracking. Returns complete deal object with ID. Use list_users, list_pipelines, list_stages, list_persons, list_organizations for valid IDs.
update_deal
Update deal properties: title, value, stage, status, owner, contacts, custom fields. Partial updates supported. Returns updated deal object. Use get_deal first to see current values. Commonly used to move through stages, update values, or change ownership.
delete_deal
Permanently delete a deal from Pipedrive. Cannot be undone. Removes from all pipelines, reports, and associated records. Consider marking as 'lost' instead to maintain history. Returns success confirmation.
search_deals
Search deals using text queries across titles, notes, custom fields. Supports exact match, filtering by person/organization/status, and pagination. Returns matching deals with relevance scoring. Minimum 2 characters (1 with exact_match).
list_files
Retrieve files from Pipedrive with optional filters. Returns file metadata including name, type, size, and associated deals/contacts. Supports pagination for large file lists.
get_file
Retrieve file metadata by ID including name, URL, size, type, and associations. Use list_files to find valid file IDs. Returns download URL and file details.
delete_file
Permanently delete a file from Pipedrive. Cannot be undone. Returns success confirmation. Use get_file first to verify the file.
list_notes
Retrieve notes with optional filters by person, deal, organization. Returns note content, timestamps, and associations. Supports pagination and date filtering.
get_note
Retrieve a specific note by ID including content, author, timestamps, and linked entities. Use list_notes to find valid note IDs.
create_note
Create a note attached to a deal, person, organization, or lead. Supports HTML content, pinning options, and custom timestamps. Returns created note with ID.
update_note
Update note content, attachments, or pinning status. Partial updates supported. Returns updated note. Use get_note first to see current content.
delete_note
Permanently delete a note from Pipedrive. Cannot be undone. Returns success confirmation.
list_organizations
Retrieve organizations with filtering and pagination. Filter by owner, first letter, or custom filters. Returns company data including name, address, contacts, and deal counts. Use to browse companies or find organizations by owner.
get_organization
Retrieve detailed organization info by ID. Returns company name, address, contacts, deal statistics, custom fields, and metadata. Use list_organizations or search_organizations to find valid IDs.
create_organization
Create a new organization/company with name, address, owner, and custom fields. Returns complete organization object with ID. Use list_users to find valid owner IDs.
update_organization
Update organization properties: name, address, owner, visibility, custom fields. Partial updates supported. Returns updated organization. Use get_organization first for current values.
delete_organization
Permanently delete an organization from Pipedrive. Cannot be undone. Removes from all deals and associated records. Returns success confirmation.
search_organizations
Search organizations using text queries across names, addresses, and notes. Supports exact match mode and pagination. Returns matching companies with relevance scoring. Min 2 chars required.
list_persons
Retrieve contact persons from your Pipedrive CRM with advanced filtering and pagination. Filter by owner, first letter of name, or custom filters. Supports sorting and pagination for large contact databases. Returns complete person objects with emails, phones, organization associations, deal counts, and custom fields. Use this to browse contacts, export contact lists, or find contacts by owner.
get_person
Retrieve detailed contact info by ID. Returns name, emails, phones, job title, organization, deal statistics, activity counts, and custom fields. Use list_persons or search_persons to find valid IDs. Essential for viewing contact details before updates.
create_person
Create a new contact with name, emails, phones, organization, and job title. Supports custom fields, labels, and marketing consent. Returns complete person object with ID. Use list_organizations to find valid org IDs.
update_person
Update an existing contact person's properties including name, emails, phones, job title, organization association, or custom fields. Supports partial updates - only provide fields you want to change. Returns the updated person object with all current data. Use get_person first to see current values, then update specific fields as needed. Commonly used to update contact information, change organization associations, or update job titles when contacts change roles.
delete_person
Permanently delete a contact person from your Pipedrive account. This action cannot be undone. The contact will be removed from all deals, activities, and associated records. Use with caution as this removes all historical data for this contact. Consider marking contacts as inactive instead if you want to maintain historical records. Returns success confirmation upon deletion.
search_persons
Search contacts using text queries across names, emails, phones, and notes. Supports exact match mode, filtering by organization, and pagination. Returns matching contacts with relevance scoring. Min 2 chars required (1 with exact_match).
list_pipelines
Retrieve all sales pipelines configured in your Pipedrive account. Returns pipeline names, IDs, stages, deal probability settings, and order. Use this to discover available pipelines before creating deals or filtering by pipeline. Essential for understanding your sales process structure and pipeline configuration.
get_pipeline
Retrieve detailed information for a specific sales pipeline by its ID. Returns complete pipeline data including name, stages, deal probability settings, and configuration. Use list_pipelines to find valid pipeline IDs. Essential for viewing pipeline structure and stage details.
list_pipeline_deals
Retrieve all deals within a specific sales pipeline with optional filtering by stage, owner, or status. Supports pagination for large deal lists. Returns complete deal objects with values, stages, and associated contacts. Use this to analyze pipeline health, view deals at specific stages, or export pipeline data for reporting.
list_stages
Retrieve all stages across all pipelines or stages within a specific pipeline. Returns stage names, IDs, order, deal probability percentages, and pipeline associations. Use this to discover valid stage IDs before creating or moving deals. Essential for understanding your sales process stages and stage progression.
get_stage
Retrieve detailed information for a specific pipeline stage by its ID. Returns complete stage data including name, order, deal probability, pipeline association, and configuration. Use list_stages to find valid stage IDs. Essential for viewing stage details and understanding stage properties.
list_stage_deals
Retrieve all deals within a specific pipeline stage with optional filtering by owner or status. Supports pagination for large deal lists. Returns complete deal objects with values, contacts, and metadata. Use this to analyze stage performance, view deals at a specific point in your sales process, or identify bottlenecks in your pipeline.
list_users
Retrieve all users in your Pipedrive workspace including active and inactive team members. Returns user names, IDs, emails, roles, and status. Use this to discover valid user IDs for assigning deals, contacts, organizations, or activities. Essential for team management and understanding who can be assigned to records.
get_user
Retrieve detailed information for a specific user by their ID. Returns complete user data including name, email, role, permissions, language, timezone, and activity status. Use list_users to find valid user IDs. Essential for viewing team member details and understanding user permissions.
get_current_user
Retrieve detailed information about the currently authenticated user making API requests. Returns your user profile including name, email, company, role, permissions, preferences, and account settings. Use this to verify authentication, check your permissions, or get your user ID for filtering your own records.
validate_credential
Validate Pipedrive credentials. Verifies credentials during setup.
How to set up Merge Agent Handler
In an mcp.json file, add the configuration below, and restart Cursor.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5 "headers": {
6 "Authorization": "Bearer yMt*****"
7 }
8 }
9 }
10}
11Open your Claude Desktop configuration file and add the server configuration below. You'll also need to restart the application for the changes to take effect.
Make sure Claude is using the Node v20+.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "command": "npx",
5 "args": [
6 "-y",
7 "mcp-remote@latest",
8 "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
9 "--header",
10 "Authorization: Bearer ${AUTH_TOKEN}"
11 ],
12 "env": {
13 "AUTH_TOKEN": "yMt*****"
14 }
15 }
16 }
17}Open your Windsurf MCP configuration file and add the server configuration below.
Click on the refresh button in the top right of the Manage MCP server page or in the top right of the chat box in the box icon.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "command": "npx",
5 "args": [
6 "-y",
7 "mcp-remote@latest",
8 "https://ah-api.merge.dev/api/v1/tool-packs/<tool-pack-id>/registered-users/<registered-user-id>/mcp",
9 "--header",
10 "Authorization: Bearer ${AUTH_TOKEN}"
11 ],
12 "env": {
13 "AUTH_TOKEN": "<ah-production-access-key>"
14 }
15 }
16 }
17 }In Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows), run "MCP: Open User Configuration".
You can then add the configuration below and press "start" right under servers. Enter the auth token when prompted.
Learn more in the official documentation ↗
1{
2 "inputs": [
3 {
4 "type": "promptString",
5 "id": "agent-handler-auth",
6 "description": "Agent Handler AUTH_TOKEN", // "yMt*****" when prompt
7 "password": true
8 }
9 ],
10 "servers": {
11 "agent-handler": {
12 "type": "stdio",
13 "command": "npx",
14 "args": [
15 "-y",
16 "mcp-remote@latest",
17 "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
18 "--header",
19 "Authorization: Bearer ${input:agent-handler-auth}"
20 ]
21 }
22 }
23}FAQs on using Merge's Pipedrive MCP server
FAQs on using Merge's Pipedrive MCP server
What is a Pipedrive MCP server?
It’s an MCP server that lets you access data and functionality from Pipedrive via tools. Your agents can invoke these tools to update activities, create deals, fetch notes, and more.
Pipedrive doesn’t currently support an MCP server, but you could use one from a 3rd-party platform, like Merge Agent Handler.
What are some common tools from a Pipedrive MCP server?
Here are just a few popular tools:
- <code class="blog_inline-code">create_deal</code> to create a new deal with title, value, owner, and stage
- <code class="blog_inline-code">delete_note</code> to permanently delete a note from Pipedrive
- <code class="blog_inline-code">get_organization</code> to retrieve detailed organization info by ID
- <code class="blog_inline-code">search_deals</code> to search deals using text queries across titles, notes, and custom fields
- <code class="blog_inline-code">list_files</code> to retrieve files attached to records in Pipedrive
How can I use a Pipedrive MCP server?
Leverage it in any of the following ways:
- Inbound lead triage and routing: When a new lead appears in Pipedrive, an agent classifies it (e.g., ICP fit, urgency, segment), enriches missing fields, assigns an owner, and moves it into the right pipeline stage
- Daily pipeline health briefing: Each morning, pull “stuck” deals (e.g., no activity in X days, close date slipped, missing next step) and generate a prioritized action list for each rep
- Account research pack for sales calls: Given a company/domain, fetch the org and related people/deals from Pipedrive and produce a one-pager with context like relationship history, open opps, last touch, objections, and next-step recommendations
- Deal desk/approval readiness: Detect when a deal reaches “legal/procurement” stages and automatically compile required details into a checklist for internal approval
- Post-meeting CRM hygiene: After a call, summarize notes into structured updates (such as next step, timeline, and stakeholders) and write them into the relevant Pipedrive deal/person so the CRM stays current
- RevOps data quality monitoring: Continuously scan for CRM hygiene issues (e.g., missing close dates, missing deal value, duplicate orgs, inconsistent stage naming) and produce a weekly “fix list”
What makes Merge Agent Handler’s Pipedrive MCP server better than alternative Pipedrive MCP servers?
Here are just a few factors:
- End-to-end integration lifecycle management: Merge handles authentication, credential storage, rate limiting, and error handling across all third-party systems so developers don’t need to build and maintain this infrastructure
- Enterprise-grade security with DLP: A built-in security gateway scans all tool inputs and outputs for sensitive data and can block, redact, or enforce rules based on your configuration
- Real-time observability and audit logs: Every tool call is logged with full visibility into underlying API requests, with fully searchable logs for debugging, auditing, and optimization
- Prebuilt and customizable connectors: You can use fully managed connectors out of the box or customize them via Connector Studio to fit your agentic workflows
- Evaluation Suite for reliability: Validate tool behavior by testing outputs against expected results to ensure consistent agent performance
Can I set custom security rules for Pipedrive tool calls in Merge Agent Handler?
Yes, Merge Agent Handler includes a security gateway with DLP that allows you to define custom rules for tool inputs and outputs.
- Automate CRM updates without “oops” moments: Allow agents to update stages/next steps, but block writes if the payload contains credentials/secrets (API keys, passwords) that sometimes get pasted from emails/Slack
- Keep reps productive while protecting PII: Let agents summarize calls into Pipedrive notes, but redact personal data (phone numbers, personal emails) so call notes stay useful without oversharing sensitive info
- Prevent pricing/discount strategy from spreading: If an agent drafts or syncs notes that include discount guidance or internal pricing logic, mask/redact those parts before they land in broadly visible Pipedrive fields
- Enforce “right data, right region” policies: Apply region-based handling (e.g., stricter controls for EU personal data) so agents can still help globally while aligning to internal compliance expectations
- Protect sensitive pipelines/stages: Block or limit access to certain pipelines (e.g., Enterprise, Strategic, Security Review) so only the right identities/agents can read or modify those deals
How can I start using Merge Agent Handler's Pipedrive’s MCP server?
Take the following steps:
1. Create (or sign in to) your Merge Agent Handler account and open the dashboard.
2. Create a Tool Pack for the workflow you want (e.g., “Pipedrive lead routing” or “Pipeline reporting”). Tool Packs define which connectors/tools your agent is allowed to call.
3. Add the Pipedrive connector to the Tool Pack and select the specific Pipedrive tools you want exposed (start with read-only tools first, then add write tools if needed).
4. Create (or choose) a Registered User. This is the identity boundary Agent Handler uses for credentials + audit logs.
5. Authenticate Pipedrive for that Registered User (so Agent Handler can call Pipedrive on their behalf).
6. Copy your Agent Handler MCP endpoint URL for that Tool Pack and Registered User. It follows this pattern:
<code class="blog_inline-code">https://…/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp</code>.
7. Add the MCP server to your MCP client / agent runtime (Cursor, Claude Desktop, Windsurf, VS Code, etc.) using that endpoint URL.
8. Configure authentication to the MCP endpoint by sending: <code class="blog_inline-code">Authorization: Bearer <your Agent Handler API key/token></code>
9. Refresh/list tools in your MCP client to confirm the Pipedrive tools are discovered and available (i.e., <code class="blog_inline-code">list_tools</code>).
10. Test with a safe read call first, then check Agent Handler logs to confirm the arguments/response look right before enabling broader access or write actions.
Ready to try it out?
Whether you're an engineer experimenting with agents or a product manager looking to add tools, you can get started for free now
