Log inSubmit server
Zendesk MCP Server logo

Zendesk MCP Server

Connects AI assistants to Zendesk for ticket management, Help Center editing, search, translation, and customer requests.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Zendesk MCP Server

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-server": {
      "command": "npx",
      "args": [
        "-y",
        "@fruggr/zendesk-mcp-server"
      ]
    }
  }
}

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

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

zendesk-mcp-server connects MCP clients to Zendesk Support and Help Center APIs for ticket work, knowledge-base maintenance, and customer requests. It uses per-user OAuth 2.1 with PKCE, so actions follow each user's Zendesk permissions rather than a shared administrator credential. Reach for it when an assistant needs to search or triage tickets, edit articles, inspect image attachments, or submit and track requests. It runs locally over stdio or can be deployed as a private HTTP MCP server.

Use cases

  • Search Help Center content for answers
  • Triage and update support tickets
  • Draft and translate knowledge-base articles
  • Inspect ticket screenshots and image attachments
  • Submit and track customer requests

Key features

  • Per-user OAuth 2.1 PKCE authentication
  • Ticket creation, updates, comments, triage, and summaries
  • Section-based Help Center article editing
  • Native MCP image content for ticket attachments
  • Customer-facing request submission and tracking
  • Configurable tool and read-only surfaces

Tools4

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

Self-reported~6 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 Today

Recent health check succeeded.

7/7 checks healthy over the last 41d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

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

Adoption & maintenance

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

GitHub stars14Stargazers on the source repository.
npm downloads6.7kPackage downloads in the last 30 days.
Last commitTodayMost recent push to the default branch.
Tools exposed4Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Zendesk MCP Server works

What zendesk-mcp-server does

zendesk-mcp-server brings Zendesk Support and Help Center operations into MCP-compatible AI clients. It supports both internal agent workflows and end-user request flows. Agents can search for relevant Help Center content, create and manage tickets, add public replies or internal notes, adjust priority and assignment, and mark tickets solved. They can also summarize ticket histories and inspect images attached to tickets.

For knowledge management, the server can draft new Help Center articles, revise existing content, and translate articles while keeping language versions aligned. Large articles can be edited by section rather than sending the complete HTML body through the model.

The end-user mode follows Zendesk's requester path: a customer selects a request type, answers the questions presented by the form, attaches a screenshot when needed, and follows the resulting ticket. They can read replies, respond, and close a resolved request.

How it works

Authentication is based on OAuth 2.1 with PKCE. Each person signs in with their own Zendesk account, and the assistant operates within that account's permissions. Static API tokens and shared service-account credentials are not supported.

The local deployment uses stdio and starts the browser-based sign-in flow when the first tool call is made. After authentication, the OAuth token is stored in an owner-only file and reused across restarts. A remote deployment can use HTTP while retaining a separate Zendesk session for each request and the requesting user's token.

Tool exposure can be adjusted to suit the client context. Operations may be exposed individually, grouped behind namespace proxies, or presented through one unified tool. The surface can also be limited by namespace or restricted to read-only operations.

Ticket images are returned as native MCP image content for the connected model to process. Other attachment types are returned as text references. Image limits can be configured.

Setup and configuration

The local server requires Node.js 22 or newer and a Zendesk Support or Suite instance. Run it without a global installation with:

Terminal
npx -y @fruggr/zendesk-mcp-server <your-subdomain>

Alternatively, install the package globally and invoke zendesk-mcp-server <your-subdomain>.

Before signing in, create a public OAuth client in Zendesk Admin Center under Apps and integrations, APIs, and OAuth Clients. Use http://localhost:27439/callback as the redirect URL unless changing the callback port with the server option or its corresponding configuration. The client needs the read scope, plus write for normal read-write operation. A read-only deployment requests only read.

The OAuth client identifier can be based on the Zendesk subdomain or supplied through ZENDESK_OAUTH_CLIENT_ID. The callback port and token-file location can also be overridden through their documented configuration options. Multiple instances can run with separate token files, such as one read-write process and one read-only process.

Tools and capabilities

  • Find Help Center answers using meaning-based search.
  • Create, retrieve, update, summarize, and triage Zendesk tickets.
  • Add public comments or internal notes, change priority and assignment, and solve tickets.
  • Read ticket image attachments as MCP image content.
  • Draft, translate, and update Help Center articles by section.
  • Submit and track requests through the customer-facing workflow.
  • Choose individual tools, namespace groups, a unified tool, or a read-only surface.

Limitations and notes

Coverage is limited to Zendesk Support and Help Center, also known as Guide. Zendesk Talk, Explore analytics, and Sell endpoints are outside the server's scope.

The authentication model intentionally excludes API-token authentication, including email-plus-token Basic authentication. This makes the server unsuitable for headless workflows that require a shared service account or static credential. Write operations also require the OAuth client to allow the write scope; read-only mode is available when only retrieval is needed.

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 Server

zendesk-mcp-server is an MCP server that connects AI assistants to Zendesk Support and Help Center. Its main tools help search Help Center content, manage and summarize tickets, edit and translate articles, inspect image attachments, and submit or track customer requests using each user's Zendesk permissions.

Install it by running `npx -y @fruggr/zendesk-mcp-server <your-subdomain>`, or install the package globally with npm and run `zendesk-mcp-server <your-subdomain>`. Node.js 22 or newer and a Zendesk Support or Suite instance are required.

Authenticate it with a public Zendesk OAuth client using OAuth 2.1 PKCE. Create the client in Zendesk Admin Center, configure the localhost callback URL, and complete the browser sign-in flow on the first tool call. API-token authentication is not supported.

Yes, zendesk-mcp-server is intended to work with Cursor and other MCP clients. The server can run locally over stdio, and its README names Cursor alongside Claude Desktop, Claude Code, and VS Code.

No, zendesk-mcp-server does not support shared API tokens or service-account authentication. Each user signs in through OAuth 2.1 PKCE, allowing Zendesk permissions and actions to remain tied to that user.

Related MCP servers

All in Communication 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 Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/zendesk-mcp-server?style=directory)](https://allmcps.com/mcp/zendesk-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/zendesk-mcp-server"><img src="https://allmcps.com/api/badge/zendesk-mcp-server?style=directory" alt="Zendesk MCP Server on AllMCPs" /></a>