Zendesk MCP Server (Coatsworth)
Zendesk ticket, user, and organization data management through the Zendesk API.
Data last scanned today · Reviewed yesterday
Overview
This server provides a comprehensive interface for the Zendesk API, enabling AI models to interact with Support, Talk, Chat, and Guide products. Users can programmatically list, create, update, and delete tickets, users, organizations, groups, macros, views, triggers, and automations. The server requires a Zendesk subdomain, email, and API token configured via environment variables to establish the connection. It includes a built-in testing utility through the MCP Inspector to verify tool functionality before full integration.
Our verdict
This server carries a high-risk rating with a security score of 0/100, primarily due to the lack of an authentication method and the absence of read-only mode, which grants full write access to your Zendesk instance. Additionally, the project is community-maintained rather than vendor-supported and has not received updates for over 470 days. It should be avoided in production environments or systems handling sensitive customer data.
- Supports a wide range of Zendesk API functions
- Contains only four direct dependencies
- Provides documented tools for ticket and user management
- No authentication method implemented for the server
- Lacks a read-only mode for restricted access
- Last code commit occurred 470 days ago
- No open-source license detected for the repository
Setup
{
"mcpServers": {
"mattcoatsworth-zendesk-mcp-server": {
"args": [
"-y",
"zendesk-mcp-server"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
- No built-in authentication — anyone with access to this config can invoke every tool it exposes.
Tools
| Tool | Description | Risk |
|---|---|---|
| list_tickets | List tickets in Zendesk | low |
| get_ticket | Get a specific ticket by ID | low |
| create_ticket | Create a new ticket | medium |
| update_ticket | Update an existing ticket | medium |
| delete_ticket | Delete a ticket | high |
| list_users | List users in Zendesk | low |
| get_user | Get a specific user by ID | low |
| create_user | Create a new user | medium |
| update_user | Update an existing user | medium |
| delete_user | Delete a user | high |
| list_organizations | List organizations in Zendesk | low |
| get_organization | Get a specific organization by ID | low |
| create_organization | Create a new organization | medium |
| update_organization | Update an existing organization | medium |
| delete_organization | Delete an organization | high |
| list_groups | List agent groups in Zendesk | low |
| get_group | Get a specific group by ID | low |
| create_group | Create a new agent group | medium |
| update_group | Update an existing agent group | medium |
| delete_group | Delete a group | high |
| list_macros | List macros in Zendesk | low |
| get_macro | Get a specific macro by ID | low |
| create_macro | Create a new macro | medium |
| update_macro | Update an existing macro | medium |
| delete_macro | Delete a macro | high |
| list_views | List views in Zendesk | low |
| get_view | Get a specific view by ID | low |
| create_view | Create a new view | medium |
| update_view | Update an existing view | medium |
| delete_view | Delete a view | high |
| list_triggers | List triggers in Zendesk | low |
| get_trigger | Get a specific trigger by ID | low |
| create_trigger | Create a new trigger | medium |
| update_trigger | Update an existing trigger | medium |
| delete_trigger | Delete a trigger | high |
| list_automations | List automations in Zendesk | low |
| get_automation | Get a specific automation by ID | low |
| create_automation | Create a new automation | medium |
| update_automation | Update an existing automation | medium |
| delete_automation | Delete an automation | high |
| search | Search across Zendesk data | low |
| list_articles | List Help Center articles | low |
| get_article | Get a specific Help Center article by ID | low |
| create_article | Create a new Help Center article | medium |
| update_article | Update an existing Help Center article | medium |
| delete_article | Delete a Help Center article | high |
| get_talk_stats | Get Zendesk Talk statistics | low |
| list_chats | List Zendesk Chat conversations | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›What are the software prerequisites for running this server?
You must have Node.js version 14 or higher installed and a Zendesk account enabled with API access.
›How do I configure my Zendesk credentials for the server?
You must create a .env file in the repository root containing your ZENDESK_SUBDOMAIN, ZENDESK_EMAIL, and ZENDESK_API_TOKEN.
›How can I verify the server is working correctly during development?
You can use the provided command npm run inspect to test the server functionality with the MCP Inspector.
›Does this server support Help Center and Talk functionality?
Yes, it includes tools for managing Help Center articles and retrieving Zendesk Talk statistics.
›Can I access Zendesk API documentation through the server?
Yes, the server provides resources via the zendesk://docs/{section} URI pattern to access documentation for specific API sections.
Alternatives
Badge
Maintain this server? Add the live badge to your README.