Connect your AI Agents to Pipedrive in minutes
Available tools
list_activities
Retrieve activities from your Pipedrive CRM with advanced filtering and pagination. Filter by owner, type (call/meeting/task), completion status, or date range. Supports sorting and pagination for large activity lists. Returns complete activity objects with subjects, due dates, associated deals/contacts, and completion status. Use this to view scheduled tasks, track team activities, 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 from your Pipedrive CRM with advanced filtering and pagination. Filter by owner, pipeline stage, status (open/won/lost), or custom filters. Supports sorting and pagination for large datasets. Returns complete deal objects with associated contacts, organizations, values, and custom fields. Use this to analyze pipeline health, find deals matching specific criteria, or export deal data for reporting.
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.
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
Explore other MCP servers built and managed by Merge
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
