Home / MCP / Zendesk MCP Server
Provides Zendesk ticket management, prompts for analysis and drafting, plus access to Help Center articles via MCP.
Configuration
View docs{
"mcpServers": {
"zendesk": {
"command": "uv",
"args": [
"--directory",
"/path/to/zendesk-mcp-server",
"run",
"zendesk"
]
}
}
}You are configuring and using a Zendesk MCP Server to access Zendesk tickets, comments, and knowledge base content through an MCP client. This server provides prompts for ticket analysis and response drafting, plus tools to manage tickets and navigate the Zendesk knowledge base.
Connect to the Zendesk MCP Server from your MCP client and use the provided prompts and tools to work with Zendesk data. You can analyze tickets with the analyze-ticket prompt, draft responses with the draft-ticket-response prompt, fetch tickets with get_tickets, retrieve a single ticket with get_ticket, fetch comments with get_ticket_comments, add comments with create_ticket_comment, create new tickets with create_ticket, and update existing tickets with update_ticket. The server can also grant access to Zendesk Help Center articles as knowledge base material for informed ticket handling.
When you start the server in a Claude-based environment or via a local MCP client, ensure the server is running before issuing any MCP commands. If you use Docker, start the container with the appropriate environment file loaded so credentials are available to the server at runtime.
Prerequisites you need before installation: Node-style tooling and a Python environment provided by the MCP runtime ecosystem. You will also need access to a Zendesk account and the credentials to authenticate API requests.
1) Build the MCP server components locally or prepare the Docker image as described in the setup flow.
2) Prepare credentials by creating a .env file from the example and filling in your Zendesk credentials. Ensure this file is secured and excluded from version control.
3) If you are wiring into Claude or another MCP client, use the provided JSON configuration to register the MCP server with the client.
Configuration and runtime notes: The server relies on an environment file for credentials when run in Docker. When using containerized execution, you pass your credentials via an environment file and reference it from the container. You should also ensure the runtime can locate the server directory for MCP execution.
Security: Keep credentials secure and avoid committing the .env file to version control. Use a dedicated production environment file and apply standard access controls to the container or host running the MCP server.
Troubleshooting tips: If the server fails to start, verify that the environment file is present and that the command and args from the MCP client configuration match the runtime expectations. Confirm that the MCP client can reach the server and that any required ports or IPC channels are open as dictated by your deployment model.
Fetch the latest Zendesk tickets with pagination support. Returns essential fields such as id, subject, status, priority, description, timestamps, and assignee information.
Retrieve a Zendesk ticket by its ID.
Retrieve all comments for a Zendesk ticket by its ID.
Create a new comment on an existing Zendesk ticket, with an option to mark the comment public.
Create a new Zendesk ticket with subject, description, and optional fields like requester, assignee, priority, type, tags, and custom_fields.
Update fields on an existing Zendesk ticket such as status, priority, type, assignee, tags, custom_fields, and due date.