Log inSubmit server
Zendesk MCP logo

Zendesk MCP

Connects AI agents to Zendesk Support for ticket creation, search, assignment, comments, metrics, and status changes.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Zendesk MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "zendesk-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@markusvankempen/zendesk-mcp-server"
      ],
      "env": {
        "ZENDESK_SUBDOMAIN": "YOUR_VALUE_HERE",
        "ZENDESK_EMAIL": "YOUR_VALUE_HERE",
        "ZENDESK_API_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 14 tools correctly (4d ago).

Overview

Zendesk MCP MCP server exposes Zendesk Support ticket operations through the Model Context Protocol. It provides TypeScript/npm and Python/FastMCP implementations that connect to the Zendesk REST API v2 over stdio or SSE. Reach for it when an agent needs to create, inspect, update, route, or close support tickets while preserving the real requester’s identity.

Use cases

  • Create support tickets for identified customers
  • Search and review Zendesk ticket conversations
  • Assign tickets to agents or groups
  • Add public replies or internal notes
  • Track SLA and ticket timing metrics

Key features

  • 14 Zendesk ticket tools
  • Requester-aware ticket creation
  • Zendesk query search
  • Public replies and internal notes
  • TypeScript and Python implementations
  • stdio and SSE operation

Tools14

What Zendesk MCP lets your agent do. Expand a tool for its parameters.

Verified live~1.1k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

5/5 checks healthy over the last 35d

What it can do

From the 14 tools this server returned when we ran it.

Read-only tools · 14
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age133 days
Maintainers1

Observed 2026-10-19 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · @markusvankempen/zendesk-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads428Package downloads in the last 30 days.
Last commit4mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed14Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Zendesk MCP works

What Zendesk MCP does

The Zendesk MCP MCP server gives MCP-compatible agents access to 14 Zendesk Support ticket operations. It covers the ticket lifecycle from creation and retrieval through assignment, commenting, reopening, and solving. Agents can also search tickets, list recent or administrator-visible tickets, find tickets by requester email, read conversations, inspect ticket metrics, and look up Zendesk users by email.

A notable behavior is requester attribution during ticket creation. The server is designed to create a ticket for the actual customer rather than the API service account, allowing Zendesk email replies to route to the intended requester.

The repository includes separate TypeScript and Python implementations. The TypeScript version is distributed as an npm package, while the Python version uses FastMCP and is distributed through PyPI.

How it works

MCP clients invoke the server’s tools, and the server makes requests to Zendesk’s REST API v2. Local configurations use stdio, which fits desktop and editor clients. The project also documents SSE operation for remote deployments, including IBM Code Engine. The same repository describes usage with Cursor, VS Code, Claude Desktop, watsonx Orchestrate, and IBM Code Engine.

The available actions are split between read and write operations. Read tools retrieve tickets, comments, users, lists, searches, and timing metrics. Write tools create or update tickets, add public replies or internal notes, assign tickets to agents or groups, close solved work, and reopen tickets.

Setup and configuration

Install the TypeScript implementation with:

Terminal
npx @markusvankempen/zendesk-mcp-server

The Python package is installed with:

Terminal
pip install zendesk-mcp-server-py

The Zendesk MCP MCP server requires three environment variables: ZENDESK_SUBDOMAIN, ZENDESK_EMAIL, and ZENDESK_API_TOKEN. Set them in the MCP client configuration or the process environment. The repository provides configuration examples for local IDE use and deployment scenarios.

For local usage, configure the client to launch the npm or Python server over stdio. Remote deployments can expose the server through SSE; the repository includes Code Engine documentation and client configuration examples for that arrangement.

Tools and capabilities

The ticket tools provide these operations:

  • Create tickets with requester attribution.
  • Retrieve tickets by ID.
  • Search using Zendesk query syntax.
  • List recently updated, administrator-wide, or requester-specific tickets.
  • Read ticket comments and conversation history.
  • Add a public response or an internal note.
  • Update status, priority, tags, or comments.
  • Assign tickets to a group or agent.
  • Mark tickets solved or reopen solved and closed tickets.
  • Retrieve SLA and timing metrics.
  • Find Zendesk users by email address.

These capabilities suit agents that need to answer support questions with ticket context, make controlled ticket changes, or automate routine routing and follow-up actions.

Limitations and notes

Write operations can change ticket state, comments, assignment, and metadata, so client-side instructions and Zendesk permissions should be configured carefully. The repository documents both local stdio and remote SSE topologies, but the exact deployment steps depend on the selected implementation and hosting environment.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Zendesk MCP

Zendesk MCP is an MCP server that connects AI agents to Zendesk Support through the Zendesk REST API v2. Its main tools create, search, retrieve, update, assign, comment on, close, and reopen tickets, while also providing requester lookup and SLA or timing metrics.

Install the TypeScript version with `npx @markusvankempen/zendesk-mcp-server` or install the Python package with `pip install zendesk-mcp-server-py`. Configure the server with `ZENDESK_SUBDOMAIN`, `ZENDESK_EMAIL`, and `ZENDESK_API_TOKEN`.

Yes, Zendesk MCP works with Cursor over a local stdio configuration. The repository provides a Cursor installation link and an example that launches the npm package with the required Zendesk environment variables.

Yes, Zendesk MCP can add either a public reply or an internal note through its ticket comment tool. It also provides a separate operation for reading the ticket conversation.

Related MCP servers

All in Support & Service Management All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewZendesk MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/zendesk-mcp?style=directory)](https://allmcps.com/mcp/zendesk-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/zendesk-mcp"><img src="https://allmcps.com/api/badge/zendesk-mcp?style=directory" alt="Zendesk MCP on AllMCPs" /></a>