zendesk

MCP server from mattcoatsworth/zendesk-mcp-server

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

Command

claude mcp add --transport stdio mattcoatsworth-zendesk-mcp-server node path/to/server.js \
  --env ZENDESK_EMAIL="your-email@example.com" \
  --env ZENDESK_API_TOKEN="your-api-token" \
  --env ZENDESK_SUBDOMAIN="your-subdomain"

How to use

This MCP server provides a Zendesk API integration within the MCP framework. It exposes a suite of tools to interact with Zendesk products such as Support (tickets, users, organizations, groups, macros, views, triggers, automations), Talk, Chat, and Guide, enabling you to programmatically manage Zendesk resources via MCP commands. You can query lists, fetch specific records, and perform create/update/delete operations using the prepared tool commands. The server authenticates with Zendesk using API tokens, so initialize it with your Zendesk credentials and then use the available MCP tools to perform operations in a controlled, auditable way. The included documentation endpoint and resource references help you discover sections of the Zendesk API as you integrate more features.

How to install

Prerequisites:

Node.js 14 or higher
Access to a Zendesk account with API permissions

Installation steps:

Clone the repository: git clone <repository-url>
Navigate to the project directory: cd <project-directory>
Install dependencies:
```
npm install
```

Create a .env file with Zendesk credentials:

ZENDESK_SUBDOMAIN=your-subdomain
ZENDESK_EMAIL=your-email@example.com
ZENDESK_API_TOKEN=your-api-token

Start the server:
```
npm start
```
(Optional for development) Enable auto-restart:
```
npm run dev
```
(Optional) Run MCP Inspector to test endpoints:
```
npm run inspect
```

Additional notes

Tips and considerations:

Ensure your Zendesk API token has the necessary scopes for the desired resources (tickets, users, organizations, etc.).
Keep your .env file secure and exclude it from version control.
The server uses environment variables for Zendesk authentication; if you rotate tokens, update the .env file and restart the server.
If you encounter authentication issues, double-check the subdomain and token format (token@example.com:token is a common pattern in Zendesk API integrations).
Use the MCP Inspector tool to validate command availability and responses during integration development.
Review Zendesk API rate limits and implement appropriate retry logic if building production workflows.

Related MCP Servers

zen

1.1k

Selfhosted notes app. Single golang binary, notes stored as markdown within SQLite, full-text search, very low resource usage

MCP -Deepseek_R1

A Model Context Protocol (MCP) server implementation connecting Claude Desktop with DeepSeek's language models (R1/V3)

mcp-fhir

A Model Context Protocol implementation for FHIR

mcp

Inkdrop Model Context Protocol Server

mcp-appium-gestures

This is a Model Context Protocol (MCP) server providing resources and tools for Appium mobile gestures using Actions API..

dubco -npm

The (Unofficial) dubco-mcp-server enables AI assistants to manage Dub.co short links via the Model Context Protocol. It provides three MCP tools: create_link for generating new short URLs, update_link for modifying existing links, and delete_link for removing short links.