Zendesk MCP Server

Zendesk is a customer service platform that provides ticketing, messaging, live chat, and help center solutions for customer support teams.

Tools

Last Updated

May 2, 2026

What is the Zendesk MCP Server?

The Zendesk MCP server gives AI agents structured, permission-aware access to Zendesk through the Model Context Protocol. With 27 pre-built actions, agents can read, create, and update Zendesk data on behalf of authorized users.

Willow ships the Zendesk MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how Zendesk is being used by every AI agent in your stack.

Tools

List Tickets

Get a paginated list of all tickets in Zendesk. Returns tickets with their status, priority, subject, requester, assignee, and other core fields. Use cursor-based pagination for large result sets. Note: For incremental exports of all tickets, consider using the Incremental Export API instead.

Search Tickets

Search for tickets using Zendesk's powerful search query syntax. You can search by keywords, filter by status, priority, tags, dates, and more. Examples: 'printer' finds tickets with 'printer', 'status:open priority:high' finds open high-priority tickets, 'created>2024-01-01' finds recent tickets. Returns up to 1,000 results with pagination. Use this when you need to find specific tickets based on criteria.

Get Ticket

Retrieve detailed information about a specific ticket by its ID. Returns complete ticket data including status, priority, subject, description, requester, assignee, collaborators, tags, custom fields, and timestamps. Use this when you need full details about a known ticket.

Create Ticket

Create a new support ticket in Zendesk. You must provide a subject and description (as a comment). Optionally specify priority (urgent, high, normal, low), status (new, open, pending, hold, solved, closed), type (problem, incident, question, task), tags, assignee, and custom fields. The requester is typically the customer requesting support. Use this to create new support requests programmatically.

Update Ticket

Update an existing ticket's properties and optionally add a comment. You can modify status, priority, subject, assignee, tags, custom fields, and more. To add a comment to the ticket, include the comment_body parameter. Comments can be public (visible to end users) or private (agent-only). Use this to change ticket properties or add follow-up messages.

Delete Ticket

Permanently delete a ticket from Zendesk. This action cannot be undone. Use with caution. Tickets are typically solved or closed rather than deleted. Only use this for test tickets or spam. Requires appropriate permissions.

List Ticket Comments

Retrieve all comments (conversation history) for a specific ticket. Comments include messages from the requester, agents, and collaborators. Each comment shows the author, timestamp, body text, and whether it's public or private. Comments are ordered chronologically. Use this to review the full conversation history of a ticket.

Add Ticket Comment

Add a new comment to an existing ticket. This is an alternative to using Update Ticket for adding comments. You can specify whether the comment is public (visible to the requester) or private (agent-only internal note). Use this to respond to tickets or add internal notes.

List Users

Get a paginated list of all users in Zendesk. Users can be end users (customers), agents, or administrators. Filter by role to get specific user types. Returns user details including name, email, role, organization, and activity status. Use cursor-based pagination for large user lists.

Search Users

Search for users by query string. Searches across user name, email, phone, and other fields. Returns matching users with their details. Use this when you need to find specific users but don't have their ID. Example queries: email address, phone number, or partial name.

1 2 3

1–10 of 27 tools

Customize Tools

Edit descriptions, modify arguments, select tools, or add new ones

Set Up Your Zendesk MCP Server in Minutes

Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.

Claude Desktop

claude_desktop_config.json

{
  "mcpServers": {
    "willow-zendesk": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/zendesk"
    }
  }
}

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "willow-zendesk": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/zendesk"
    }
  }
}

Claude Code

CLI

claude mcp add willow-zendesk --transport http https://<org>.mcp-s.com/mcp/mcp/zendesk

n8n

HTTP Request Node

{
  "url": "https://<org>.mcp-s.com/mcp/mcp/zendesk",
  "method": "POST"
}

Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.

Enterprise Governance for Zendesk

Willow adds the layer Zendesk and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.

Zendesk MCP Server FAQ

What is the Zendesk MCP server?

The Zendesk MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write Zendesk data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.

How is Willow's Zendesk MCP server different from the official one?

The official Zendesk MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.

Which AI clients work with the Zendesk MCP server?

Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.

Is the Zendesk MCP server secure? How does Willow handle authentication?

Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in Zendesk, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which Zendesk actions agents can take?

Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.

How do I detect shadow Zendesk MCP servers in my org?

Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved Zendesk MCP locally, you'll see it.

What does the Zendesk MCP server cost?

Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.

How do I install the Zendesk MCP server with Willow?

Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.