SkillFoxx

Zendesk MCP Server

A Zendesk MCP server that reads and edits tickets and comments, serves Help Center articles and signs in as the operator.

  • 126 ★ on the repository
  • Last commit
  • Apache-2.0
MCP server

Broad access

Why this level

  • Creates and updates tickets and posts comments that customers see.
  • Reads tickets with customer personal data and passes them to the model.
All reasons and checks

reminia/zendesk-mcp-serverAuthor:reminia

Install

Manual install

uv venv && uv pip install -e .

The first Setup command in the README builds the server from a cloned repository.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Creates and updates tickets and posts comments that customers see.
  • Reads tickets with customer personal data and passes them to the model.

This is third-party code. Review the repository files before installing.

What it does

The server gives an agent Zendesk access: ticket lists and details, comments, ticket creation and updates, attachments. The Help Center knowledge base is exposed as the `zendesk://knowledge-base` resource, and the prompts `analyze-ticket` and `draft-ticket-response` help analyze a ticket and draft a reply. Sign-in uses OAuth with PKCE: each operator authorizes with their own Zendesk account, so API calls carry their role, groups and ticket access, and comments are authored by them. Tokens refresh automatically and live in `~/.config/zendesk-mcp/tokens.json` with 0600 permissions. The server runs through `uv` or in Docker.

Who it is for. Support teams and developers who work through a Zendesk ticket queue and draft replies together with an agent.

Good fit when

  • An agent reads a ticket with its comments and proposes a reply draft.
  • Help Center articles provide reference material for a customer answer.
  • A ticket must be created or updated: status, priority, assignee, tags.
  • Each operator must act under their own account so audit logs and comment authorship stay separate.

Not a fit when

  • The organization cannot register a public OAuth client in Admin Center.
  • Tickets hold data that must not go to an external model.
  • An agent only needs to read Help Center articles without ticket access.

Example request

Show the latest tickets with status open, read the comments on ticket 4812 and draft a reply without sending it.

MCP

Transport
stdio
Authentication
OAuth

Environment variables

ZENDESK_SUBDOMAIN required
Zendesk subdomain, for example acme for https://acme.zendesk.com.
ZENDESK_CLIENT_ID required
Identifier of the public OAuth client from Admin Center.
ZENDESK_OAUTH_REDIRECT_URI
Callback address, http://localhost:4567/callback by default.
ZENDESK_OAUTH_SCOPES
Scope list that caps token permissions.
ZENDESK_TOKEN_FILE
Path to the token file instead of the default.
ZENDESK_API_KEY secret
Deprecated API token sign-in, used together with ZENDESK_EMAIL.

Limitations

You need a Zendesk account that can register a public OAuth client in Admin Center (Redirect URL `http://localhost:4567/callback`) and a one-time authorization with `uv run zendesk-auth` on the operator's machine. API token sign-in still works but is deprecated: new tokens cannot be created from 27 October 2026, and all tokens stop working on 30 April 2027. In Docker authorize on the host and mount the token directory writable, otherwise the server stalls on an expired token after refresh-token rotation. Tools that create and change tickets write to the live support queue; `tickets:read users:read hc:read` scopes are enough for reading. Customer ticket text goes to the model provider.

How to disable. Remove the `zendesk` entry from the client's MCP configuration, delete `~/.config/zendesk-mcp/tokens.json` and revoke the OAuth client in Admin Center.

FAQ

How do I authorize Zendesk MCP Server?

Create a public OAuth client in Admin Center, set `ZENDESK_SUBDOMAIN` and `ZENDESK_CLIENT_ID` in `.env` and run `uv run zendesk-auth`. A browser opens a consent page and tokens are saved locally.

Which tools does the server have?

`get_tickets`, `get_ticket`, `get_ticket_comments`, `create_ticket_comment`, `create_ticket`, `update_ticket` and `get_ticket_attachment`. Help Center articles come through the `zendesk://knowledge-base` resource.

Can I grant read-only access?

Yes. Set `ZENDESK_OAUTH_SCOPES` to `tickets:read users:read hc:read`: the token then cannot create or change tickets.

Does API token sign-in still work?

For now yes, but it is deprecated. New tokens cannot be created from 27 October 2026, and all tokens stop working on 30 April 2027.

How do I run the server in Docker?

Build the image with `docker build -t zendesk-mcp-server .`, authorize on the host with `uv run zendesk-auth` and run the container with `--env-file` and the token directory mounted.

Discussion

No questions or reviews yet.

MCP servers

Bitrix24 portal MCP server

MCP-сервер портала Битрикс24

Official

Bitrix24's official per-portal MCP: an external agent uses OAuth or a token to read and change tasks, deals, meetings and mail

MCP serverBroad access

MCP server for Odoo: the agent reads, creates and updates ERP records, searches data and calls business operations within Odoo permissions

MCP serverBroad access415
Official

Official Chatway MCP server: the agent triages live chat conversations, replies to customers and searches the knowledge base

MCP serverBroad access34

Bitrix24 MCP server: tasks, CRM and lists

Bitrix24 Tasks, CRM & Lists MCP Server

Russian stack

A modular Bitrix24 MCP server with 46 tools for tasks and kanban, CRM deals and contacts, and universal lists, running in Docker with no third-party cache

MCP serverBroad access1
Official

The Churnkey MCP server: an agent reads subscription cancel data, edits retention flows and runs A/B tests

MCP serverBroad access24

README in short

Covers build and run through `uv` and Docker, OAuth client registration, token rotation, scope choice, migration from API tokens and a tool list with arguments.

README badge

Report a problem