Zendesk MCP Server
Zendesk tickets, comments, and help center articles for AI drafting and analysis.
Data last scanned yesterday · Reviewed 2 months ago
Overview
The Zendesk MCP Server enables AI agents to interface directly with your support environment. It provides granular control over ticket management, allowing users to fetch and view support requests alongside their associated comments. The server also exposes help center articles as a resource, acting as a knowledge base for LLMs to query. Beyond basic retrieval, the server includes pre-configured prompts specifically designed to assist with ticket analysis and automated response drafting. Deployment options are flexible, supporting standard local Python installations or containerized execution via Docker to isolate the environment.
Our verdict
With a security score of 50/100, this server is classified as high-risk and is not recommended for production environments where strict access controls are required. The lack of OAuth support means credentials must be handled manually, and the absence of a read-only mode grants the server full write access to your Zendesk account by default, increasing the blast radius of any potential misconfiguration.
- Includes specialized prompts for ticket drafting and analysis
- Supports help center article access as a knowledge base
- Zero direct dependencies reduce supply-chain surface area
- Supports containerized execution with non-root user privileges
- No read-only mode limits, granting full write access
- Missing OAuth support requires manual credential management
- Community-maintained project without official Zendesk support
- No verified homepage link provided
Tools
| Tool | Description | Risk |
|---|---|---|
| get_tickets | Fetch the latest tickets with pagination support | low |
| get_ticket | Retrieve a Zendesk ticket by its ID | low |
| get_ticket_comments | Retrieve all comments for a Zendesk ticket by its ID | low |
| create_ticket_comment | Create a new comment on an existing Zendesk ticket | medium |
| create_ticket | Create a new Zendesk ticket | medium |
| update_ticket | Update fields on an existing Zendesk ticket (e.g., status, priority, assignee) | medium |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›How do I configure my Zendesk credentials?
You must define your credentials in a .env file, following the format provided in the .env.example file.
›Can I run this server inside a Docker container?
Yes, you can build a Docker image using the provided Dockerfile and run it by providing your .env file via the --env-file flag.
›What are the limitations for fetching tickets?
The get_tickets tool supports pagination and sorting, with a maximum of 100 tickets allowed per page.
›Does the server provide access to Help Center articles?
Yes, you can access Help Center articles as a knowledge base using the zendesk://knowledge-base resource.
›Can I specify if a ticket comment should be private?
Yes, the create_ticket_comment tool includes a public boolean argument which defaults to true but can be set to false for private comments.
›How do I ensure the Dockerized server works with Claude Code?
When using Docker with Claude Code, you must include the -i flag in your command arguments to allow communication over STDIN/STDOUT.
Alternatives
Badge
Maintain this server? Add the live badge to your README.