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.