Summary
A full-featured Zendesk integration that brings ticket management into Claude's tool loop. Exposes read and write operations over the Zendesk API: search, list, fetch, create and update tickets, post public replies or internal notes, assign agents, set status, manage tags, and apply macros. Also surfaces views, organizations, groups, custom statuses, time tracking, and attachment handling. Includes optional Help Center article resources and Git-Zen integration for reading linked GitLab issues. Ships with two prompts for ticket analysis and response drafting. Useful when you need Claude to triage support queues, draft responses, or sync ticket state with external trackers without leaving your workflow.
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →
Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →
On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
Tools
Public tool metadata for what this MCP can expose to an agent.
16 tools
ZENDESK_COUNT_ZENDESK_ORGANIZATIONSCount the number of organizations in Zendesk.
Count the number of organizations in Zendesk.
No parameter schema in public metadata yet.
ZENDESK_CREATE_ZENDESK_ORGANIZATIONTool to create a Zendesk organization. Use when you need to group end users under a shared company profile. Use after confirming the organization name is unique.2 params
Tool to create a Zendesk organization. Use when you need to group end users under a shared company profile. Use after confirming the organization name is unique.
Parameters* required
namestringUnique organization name. Leading/trailing whitespace is trimmed by Zendesk.
external_idstringOptional unique external identifier for this organization. Comparison is case-insensitive; use to sync with external systems.
ZENDESK_CREATE_ZENDESK_TICKETCreate a ticket in Zendesk.5 params
Create a ticket in Zendesk.
Parameters* required
subjectstringShort summary of the issue. Keep it concise (e.g. 'Cannot log in').
prioritystringZendesk priority. Must be one of: 'urgent', 'high', 'normal', 'low'.one of
urgent · high · normal · lowdefault: normaldescriptionstringLong-form description / steps to reproduce.
requester_namestringName of the requester. If you supply this, you MUST also supply `requester_email`. Leave both blank to default to the authenticated user.
requester_emailstringEmail of the requester. Must accompany `requester_name`.
ZENDESK_CREATE_ZENDESK_USERTool to create a new user in Zendesk. Use when you need to onboard a user with specific details.2 params
Tool to create a new user in Zendesk. Use when you need to onboard a user with specific details.
Parameters* required
userobjectUser object containing all attributes to create
skip_verify_emailbooleanIf true, do not send a verification email upon creationdefault: false
ZENDESK_DELETE_ZENDESK_ORGANIZATIONDelete an organization in Zendesk.1 params
Delete an organization in Zendesk.
Parameters* required
organization_idstringID of the organization to delete
ZENDESK_DELETE_ZENDESK_TICKETDelete a ticket in Zendesk.1 params
Delete a ticket in Zendesk.
Parameters* required
ticket_idintegerID of the ticket to delete
ZENDESK_DESTROY_MANY_ORGANIZATIONSTool to bulk delete Zendesk organizations. Use when cleaning up test data or removing obsolete organizations in one call. Returns a job_status payload to track progress.2 params
Tool to bulk delete Zendesk organizations. Use when cleaning up test data or removing obsolete organizations in one call. Returns a job_status payload to track progress.
Parameters* required
idsstringComma-separated list of Zendesk organization IDs to delete (max 100). Required if external_ids is not provided.
external_idsstringComma-separated list of Zendesk external organization IDs to delete (max 100). Required if ids is not provided.
ZENDESK_GET_ABOUT_MEGet information about the owner account in Zendesk.
Get information about the owner account in Zendesk.
No parameter schema in public metadata yet.
ZENDESK_GET_ALL_ZENDESK_ORGANIZATIONSGet all organizations in Zendesk.
Get all organizations in Zendesk.
No parameter schema in public metadata yet.
ZENDESK_GET_ZENDESK_ORGANIZATIONGet information about a specific organization in Zendesk.1 params
Get information about a specific organization in Zendesk.
Parameters* required
organization_idintegerNumeric ID of the organization to retrieve (e.g. 123456).
ZENDESK_GET_ZENDESK_TICKET_BY_IDGet ticket details from Zendesk.1 params
Get ticket details from Zendesk.
Parameters* required
ticket_idintegerID of the ticket to get details for.
ZENDESK_LIST_ZENDESK_TICKETSList Zendesk tickets with pagination and filtering.5 params
List Zendesk tickets with pagination and filtering.
Parameters* required
pageintegerPage number for offset pagination (starts at 1)
sort_bystringField to sort by: 'assignee', 'assignee.name', 'created_at', 'group', 'id', 'requester', 'requester.name', 'status', 'subject', 'updated_at'
per_pageintegerNumber of tickets per page (max 100)
sort_orderstringSort order: 'asc' or 'desc'one of
asc · descexternal_idstringFilter tickets by external ID
ZENDESK_REPLY_ZENDESK_TICKETAction to reply to a Zendesk ticket by adding a comment.3 params
Action to reply to a Zendesk ticket by adding a comment.
Parameters* required
bodystringComment contentdefault:
publicbooleanWhether the comment is public or internaldefault: true
ticket_idintegerID of the ticket to reply to
ZENDESK_SEARCH_ZENDESK_USERSTool to search Zendesk users by email or name. Use after confirming user identity before ticket creation.4 params
Tool to search Zendesk users by email or name. Use after confirming user identity before ticket creation.
Parameters* required
namestringFull or partial name to search for. For phrase searches, enclose in quotes.
pageintegerPage number for offset pagination (starts at 1).
emailstringEmail address to search for. Exact match (e.g., 'jdoe@example.com').
per_pageintegerNumber of users per page (max 100).
ZENDESK_UPDATE_ZENDESK_ORGANIZATIONUpdate an organization in Zendesk.2 params
Update an organization in Zendesk.
Parameters* required
dataobjectNew data for the organization
organization_idintegerID of the organization to update
ZENDESK_UPDATE_ZENDESK_TICKETTool to update a ticket in Zendesk. Use when you need to modify ticket fields like status, priority, or subject after confirming the ticket ID.21 params
Tool to update a ticket in Zendesk. Use when you need to modify ticket fields like status, priority, or subject after confirming the ticket ID.
Parameters* required
dataobjectOptional raw ticket update object. Provide this to send fields under the 'ticket' wrapper directly. Alternatively, use the un-nested fields above.
tagsarrayTags to set on the ticket. Using tags here replaces all existing tags.
due_atstringDue date/time for task-type tickets (ISO 8601).
statusstringTicket status to set. If your account uses custom statuses, use custom_status_id via other endpoints.
subjectstringTicket subject/title to set during update.
metadataobjectCustom metadata to attach to this update's audit (approximately up to 1 KB).
prioritystringTicket priority. Allowed values: urgent, high, normal, low.one of
urgent · high · normal · lowemail_ccsarrayEmail CCs to add/remove. Each object includes user_id or user_email, optional user_name, and action ('put'|'delete').
followersarrayFollowers to add/remove. Each object should include user_id or user_email, with optional action ('put'|'delete').
ticket_idintegerID of the ticket to update.
safe_updatebooleanEnable optimistic locking to prevent overwrites during collisions.
comment_bodystringText body of the comment to add.
collaboratorsarrayCollaborators to set (replaces existing). Accepts user IDs, emails, or {name, email} objects.
custom_fieldsarrayList of custom field values. Each item: {id: number, value: any}.
updated_stampstringLast-known updated_at timestamp (ISO 8601) used together with safe_update.
comment_publicbooleanWhether the added comment is public (visible to requester) or internal.
comment_uploadsarrayUpload tokens to attach files to the comment.
collaborator_idsarrayCollaborator user IDs to set (replaces existing).
comment_author_idintegerAuthor ID for the comment, if different from the authenticated user.
comment_html_bodystringHTML body of the comment to add.
additional_collaboratorsarrayAdd collaborators without removing existing ones.
zendesk-mcp
A Model Context Protocol server that exposes Zendesk ticket read and write tools to Claude Code and other MCP clients.
What it does
- Search, list (paginated), and fetch Zendesk tickets, comments, and attachments
- Create new tickets and update existing ticket fields (including group, custom status, and tags)
- Post public replies and internal notes
- Set ticket status and assign tickets to agents
- Browse and apply views and macros
- Look up users, groups, organizations, and custom statuses
- Read and write time-tracking entries
- Format a ticket as a Markdown issue draft for handoff to a tracker (GitLab, GitHub, Jira)
- Two MCP prompts (
analyze-ticket,draft-ticket-response) for ticket analysis and response drafting - (Optional) Expose Zendesk Help Center articles as an MCP resource
- (Optional) Read linked GitLab issues / MRs / commits via the Git-Zen Zendesk app
Prerequisites
- Python 3.10 or newer
- A Zendesk OAuth client. A Zendesk admin can create one at:
https://<your-subdomain>.zendesk.com/admin/apps-integrations/apis/zendesk-api/oauth_clientsSet the redirect URL tohttp://localhost:8787/callbackand request scopesread write.
Install
Install into a project-local virtualenv. Using a venv keeps zendesk-mcp and its dependencies isolated from your system Python and from other projects, and is the recommended path for everything below.
From a clone of this repository:
python3 -m venv .venv
.venv/bin/pip install --upgrade pip
.venv/bin/pip install -e .
For development (also installs pytest):
.venv/bin/pip install -e ".[dev]"
Throughout this README, commands use the venv's binaries via
.venv/bin/.... You can insteadsource .venv/bin/activateonce per shell and drop the prefix — the result is the same.
OAuth setup
Run the interactive setup using the venv's Python:
.venv/bin/python -m zendesk_mcp setup
You will be prompted for:
- Your Zendesk subdomain (e.g.
acmeforacme.zendesk.com) - The OAuth client ID created by your admin
- The OAuth client secret
- (Optional) A Git-Zen integration field ID — see Optional: Git-Zen integration
- (Optional) Whether to enable the Help Center knowledge base resource — see Optional: Help Center knowledge base
The setup opens a browser for the OAuth authorization step, then writes a token to ~/.config/zendesk-mcp/config.json (mode 0600).
If you have no browser, the URL is printed to the terminal — open it on any device, click Allow, and paste the resulting redirect URL back into the prompt.
Register with Claude Code
Register the MCP server using the venv's Python by absolute path. Claude Code launches the server in a fresh shell that does not inherit your activated venv, so the absolute path is required — pointing at a bare python here will fail to import zendesk_mcp.
ZENDESK_MCP_DIR="$(pwd)" # run this from the repo root, after install
claude mcp add --scope user zendesk -- "$ZENDESK_MCP_DIR/.venv/bin/python" -m zendesk_mcp
Or just inline the absolute path you want:
claude mcp add --scope user zendesk -- /absolute/path/to/zendesk-mcp/.venv/bin/python -m zendesk_mcp
Then add the read tools to permissions.allow in ~/.claude/settings.json to avoid per-call prompts:
{
"permissions": {
"allow": [
"mcp__zendesk__zendesk_get_ticket",
"mcp__zendesk__zendesk_get_tickets",
"mcp__zendesk__zendesk_get_comments",
"mcp__zendesk__zendesk_list_attachments",
"mcp__zendesk__zendesk_download_attachment",
"mcp__zendesk__zendesk_search_tickets",
"mcp__zendesk__zendesk_ticket_to_gitlab_context",
"mcp__zendesk__zendesk_list_views",
"mcp__zendesk__zendesk_get_view",
"mcp__zendesk__zendesk_get_view_tickets",
"mcp__zendesk__zendesk_list_macros",
"mcp__zendesk__zendesk_preview_macro",
"mcp__zendesk__zendesk_search_users",
"mcp__zendesk__zendesk_get_groups",
"mcp__zendesk__zendesk_get_group_users",
"mcp__zendesk__zendesk_get_organization",
"mcp__zendesk__zendesk_list_custom_statuses"
]
}
}
Write tools (zendesk_post_comment, zendesk_post_internal_note, zendesk_set_ticket_status, zendesk_assign_ticket, zendesk_create_ticket, zendesk_update_ticket, zendesk_log_time, zendesk_add_tag, zendesk_remove_tag, zendesk_apply_macro) are intentionally not in the default allow-list — Claude will prompt you per call.
Tools
Tickets
| Tool | What it does |
|---|---|
zendesk_search_tickets | Search tickets by status, priority, type, assignee, requester, tags, or keyword |
zendesk_get_tickets | List tickets with pagination and sorting (page, per_page, sort_by, sort_order) |
zendesk_get_ticket | Get one ticket's metadata |
zendesk_create_ticket | Create a new ticket (subject, description, optional priority/type/assignee_id/requester_id/tags/custom_fields) |
zendesk_update_ticket | Update one or more fields on an existing ticket (status, priority, subject, type, assignee_id, requester_id, group_id, custom_status_id, tags, custom_fields, due_at) |
zendesk_get_comments | Get the conversation thread on a ticket |
zendesk_list_attachments | List attachments on a ticket |
zendesk_download_attachment | Download an attachment to a local cache directory |
zendesk_ticket_to_gitlab_context | Format a ticket and its conversation as a Markdown issue draft |
zendesk_post_comment | Post a public reply on a ticket |
zendesk_post_internal_note | Post an agent-only internal note on a ticket |
zendesk_set_ticket_status | Set ticket status (new, open, pending, hold, solved, closed) |
zendesk_assign_ticket | Assign a ticket to an agent by email or me |
Tags
| Tool | What it does |
|---|---|
zendesk_add_tag | Add a tag to a ticket (idempotent) |
zendesk_remove_tag | Remove a tag from a ticket (idempotent) |
Views & Macros
| Tool | What it does |
|---|---|
zendesk_list_views | List all active views |
zendesk_get_view | Get a view's filter conditions and execution settings |
zendesk_get_view_tickets | Fetch tickets currently matching a view |
zendesk_list_macros | List active macros with their actions |
zendesk_preview_macro | Preview what changes a macro would make |
zendesk_apply_macro | Apply a macro to a ticket (applies field changes and posts any comment) |
Users, Groups & Organizations
| Tool | What it does |
|---|---|
zendesk_search_users | Find users by name or email |
zendesk_get_groups | List all active groups |
zendesk_get_group_users | List the members of a group |
zendesk_get_organization | Fetch an organization including custom fields |
zendesk_list_custom_statuses | List all custom ticket statuses and their IDs |
Time tracking
| Tool | What it does |
|---|---|
zendesk_get_time_tracking | Read time-tracking entries for a ticket |
zendesk_log_time | Log a time entry against a ticket |
Git-Zen integration
| Tool | What it does |
|---|---|
zendesk_get_git_zen_links | (Git-Zen only) Get linked GitLab issues / MRs / commits for a ticket |
Prompts
The server exposes two MCP prompts that some clients (e.g. Claude Desktop) surface as slash commands:
| Prompt | Argument | What it does |
|---|---|---|
analyze-ticket | ticket_id | Asks the model to fetch the ticket and produce a summary, status/timeline, and key interaction points |
draft-ticket-response | ticket_id | Asks the model to fetch the ticket and draft a customer-facing response (with a confirmation step before posting) |
Optional: Git-Zen integration
If your Zendesk instance uses the Git-Zen app, the zendesk_get_git_zen_links tool can read its custom-field payload. Find your instance's Git-Zen custom field ID under Admin → Tickets → Fields (it is a numeric ID), then either set it during .venv/bin/python -m zendesk_mcp setup or edit ~/.config/zendesk-mcp/config.json to add:
{
"git_zen_field_id": 12345678901234
}
Without this configured, zendesk_get_git_zen_links returns a "not configured" message.
Optional: Help Center knowledge base
If your Zendesk instance has a published Help Center, you can expose its sections and articles as the zendesk://knowledge-base MCP resource. The resource returns a single JSON document covering all sections and articles, cached for one hour.
This is opt-in. Enable it by either answering "y" to the prompt during .venv/bin/python -m zendesk_mcp setup, or by adding the following to ~/.config/zendesk-mcp/config.json:
{
"knowledge_base_enabled": true
}
When the flag is absent or false, the resource is not registered, keeping the server's resource list empty for instances without a Help Center.
Development
python3 -m venv .venv
.venv/bin/pip install -e ".[dev]"
.venv/bin/pytest
Tests run on Python 3.10, 3.11, and 3.12 in CI (see .github/workflows/test.yml).
License
Featured
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →