Merge Unified's Zendesk Sell integration Merge Agent Handler's Zendesk Sell MCP server

Connect your AI Agents to Zendesk Sell in minutes

Merge lets you securely connect your agents to Zendesk Sell and thousands of tools instantly

Start building for free

Read docs

Zendesk Sell

Learn more about Merge Agent Handler

Available tools

get_contact

Retrieve a single contact by ID from Zendesk Sell. Returns full contact details including addresses, status, and custom fields.

list_contacts

List contacts with optional filtering and pagination. Filter by owner, type (org/individual), name. Returns up to 100 per page.

create_contact

Create a new contact in Zendesk Sell. Set is_organization=True for company, False for person. For orgs: name required. For individuals: last_name required.

update_contact

Update an existing contact in Zendesk Sell. Note: is_organization cannot be changed after creation. Tags are replaced entirely.

delete_contact

Delete a contact from Zendesk Sell by ID. This action is permanent and cannot be undone.

upsert_contact

Create or update a contact based on matching criteria. Returns 409 if multiple matches. Use email as filter for uniqueness.

search_contacts

Search contacts using filters like email, name, status, owner, type. Supports pagination and sorting.

get_deal

Retrieve a single deal by ID from Zendesk Sell. Returns full deal details including value, stage, contact, and custom fields.

list_deals

List deals with optional filtering and pagination. Filter by owner, contact, stage, hot status. Returns up to 100 deals per page.

create_deal

Create a new deal in Zendesk Sell. Requires name and contact_id. Optionally set value, stage, owner, and custom fields.

update_deal

Update an existing deal in Zendesk Sell. Specify deal_id and fields to update. Tags are replaced entirely on update.

delete_deal

Delete a deal from Zendesk Sell by ID. This action is permanent and cannot be undone.

upsert_deal

Create or update a deal based on matching criteria. Returns 409 if multiple matches. Use name and contact_id as filters.

search_deals

Search deals using filters like name, owner, contact, stage, hot status. Supports pagination and sorting.

get_lead

Retrieve a single lead by ID from Zendesk Sell. Returns full lead details including contact info, status, and custom fields.

list_leads

List leads with optional filtering and pagination. Filter by owner, status, source. Returns up to 100 leads per page.

create_lead

Create a new lead in Zendesk Sell. Requires either last_name or organization_name. Optionally set owner, status, contact info.

update_lead

Update an existing lead in Zendesk Sell. Specify lead_id and fields to update. Tags are replaced entirely on update.

delete_lead

Delete a lead from Zendesk Sell by ID. This action is permanent and cannot be undone.

upsert_lead

Create or update a lead based on matching criteria. Returns 409 if multiple matches. Use email as filter for uniqueness.

search_leads

Search leads using filters like email, name, organization, status, owner. Supports pagination and sorting.

get_note

Retrieve a single note by ID from Zendesk Sell. Returns full note details including content and associated resource.

list_notes

List notes with optional filtering and pagination. Filter by resource type/ID to get notes for specific lead/contact/deal.

create_note

Create a new note in Zendesk Sell. Requires resource_type (lead/contact/deal), resource_id, and content.

update_note

Update an existing note in Zendesk Sell. Specify note_id and fields to update. Tags are replaced entirely.

delete_note

Delete a note from Zendesk Sell by ID. This action is permanent and cannot be undone.

list_pipelines

List all sales pipelines in Zendesk Sell. Pipelines organize deals through stages. Read-only endpoint.

list_stages

List all stages in Zendesk Sell pipelines. Filter by pipeline_id to get stages for a specific pipeline. Read-only endpoint.

get_task

Retrieve a single task by ID from Zendesk Sell. Returns full task details including content, due date, and completion status.

list_tasks

List tasks with optional filtering and pagination. Filter by owner, resource type, completion status. Returns up to 100 per page.

create_task

Create a new task in Zendesk Sell. Requires content. Optionally link to lead/contact/deal via resource_type and resource_id.

update_task

Update an existing task in Zendesk Sell. Specify task_id and fields to update. Note: remind_at must be before due_date.

delete_task

Delete a task from Zendesk Sell by ID. This action is permanent and cannot be undone.

get_user

Retrieve a single user by ID from Zendesk Sell. Returns user details including name, email, role, and team info.

list_users

List users in Zendesk Sell with optional filtering. Filter by status, role, or confirmation. Use to find owners for assignment.

validate_credential

Validate Zendesk Sell credentials. Verifies credentials during setup.

View all tools by creating a free account See more tools

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}
11

Copy Code

Open 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}

Copy Code

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  }

Copy Code

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}

Copy Code

FAQs on using Merge's Zendesk Sell MCP server

What is a Zendesk Sell MCP?

It's an MCP server that lets your agents access data and functionality from Zendesk Sell via tools. Your agents can invoke these tools to create and qualify leads, advance deals through pipeline stages, log calls and notes, assign follow-up tasks, and more.

Zendesk doesn't offer an MCP server purpose built for Zendesk Sell, but you can use one from a third-party platform, like Merge Agent Handler.

How can I use the Zendesk Sell MCP server?

The use cases naturally depend on the agent you've built, but here are a few common ones:

Lead capture from inbound channels: When a prospect submits a form in a marketing tool like Marketo, an agent creates a lead in Zendesk Sell, assigns it to the right rep based on territory rules, and creates a follow-up task with a due date

Stalled deal monitoring: An agent checks for deals that haven't moved pipeline stages in over 14 days, pulls the contact details and deal value, and posts a message to the deal owner in Slack with a summary and suggested next step

Closed-won handoff: When a deal is marked closed-won in Zendesk Sell, an agent creates a corresponding onboarding project in Asana and notifies the customer success team in Slack with the deal details

Weekly pipeline digest: An agent pulls all open deals grouped by stage and owner, then sends a formatted summary to sales leadership every Monday morning via email or a Slack channel

What are popular tools for Zendesk Sell's MCP server?

Here are some of the most commonly used tools:

list_deals: retrieves open deals filtered by stage, owner, or status. Good for agents that need a current snapshot of the pipeline before deciding what action to take

create_deal: adds a new deal linked to a contact or company record. Call this when an agent detects a qualifying signal in another system, like a completed demo or signed NDA

update_deal: modifies deal fields including stage, value, and expected close date. Use this when an agent needs to advance a deal through the pipeline in response to activity logged in an external tool

create_lead: adds a new lead record with contact details and rep assignment. Useful for agents ingesting lead data from marketing platforms or web form submissions

upsert_lead: creates a new lead or updates an existing one based on matching criteria. Helpful when an agent needs to avoid duplicate records from repeated signals in a source system

create_note: logs a note against a deal, lead, or contact. Call this when an agent needs to record a call summary, email exchange, or outcome from an external event.

What makes Merge Agent Handler's Zendesk Sell MCP server better than alternative Zendesk Sell MCP servers?

There are several reasons to use Merge Agent Handler's Zendesk Sell MCP server over building or using an alternative:

Enterprise-grade security and DLP: Merge Agent Handler includes built-in data loss prevention controls that let you block or redact sensitive fields before they reach an agent. For Zendesk Sell, this means you can prevent deal values, lead contact details, and rep assignment data from being exposed even when the agent has broad read access

Managed authentication and credentials: Merge stores and refreshes Zendesk Sell credentials on your behalf. You never expose raw API keys or OAuth tokens to an agent or manage token rotation manually

Real-time observability and audit trail: Every tool call made against Zendesk Sell is logged with timestamp, tool name, input parameters, and response metadata. You can audit exactly what an agent read or wrote without instrumenting anything yourself

Tool Packs and controlled access: Tool Packs let you bundle specific Zendesk Sell tools with tools from other connectors into a single MCP endpoint, scoped to a specific use case. An agent gets exactly the tools it needs, nothing more

How can I start using Merge Agent Handler's Zendesk Sell MCP server?

You can take the following steps:

1. Create or log into your Merge Agent Handler account.

2. Install the Merge CLI by running pipx install merge-api, then run merge configure to link the CLI to your Merge account and merge login to authenticate your session.

3. Register the Agent Handler MCP server with Claude Code by running claude mcp add --transport http agent-handler https://ah-api.merge.dev/mcp, then open Claude Code and run /mcp to confirm agent-handler appears with a connected status.

4. Select agent-handler from the MCP list. This opens a browser window where you select which integrations to authenticate. Choose Zendesk Sell and complete the auth flow. Merge stores and manages the credentials going forward.

5. Open a Claude Code session and start querying Zendesk Sell data directly. The first time you use a Zendesk Sell tool, a Magic Link may appear to complete connector authentication.

If you want to connect Merge Agent Handler's Zendesk Sell MCP with internal or customer-facing agentic products, you can follow the steps in our docs.

Explore other MCP servers built and managed by Merge

FreshBooks

Freshdesk

Freshservice

Front

Gamma

GitHub

GitLab

Gmail

Gong

Google BigQuery

Google Calendar

Google Docs

Google Drive

Google Maps

Google Meet

Google Sheets

Google Slides

Google Tasks

Grafana

Greenhouse

Guru

Hex

HiBob

HubSpot

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