Zendesk MCP by usefulapi
io.usefulapi/zendesk · v1.11.1
Read tickets, users, orgs, macros and satisfaction ratings; create, update and comment on tickets.
MCPremoteno credentials
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 19 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 88/100
What it does: 19 tools · 16 read, 3 write (incl. delete/pay)
Test call zendesk_list_tickets: needs a key: HTTP 401 (996 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: +5
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://zendesk.usefulapi.io/mcpTools
19 tools listed at last check
zendesk_searchUnified search across tickets, users, organizations and groups using Zendesk search syntax. Examples: `type:ticket status:open`, `type:user email:[email protected]`, `type:organization name:acme`. Zendesk REST: GET /search.json.zendesk_list_ticketsList recent tickets (offset pagination). Zendesk REST: GET /tickets.json.zendesk_get_ticketFetch a single ticket by id. Zendesk REST: GET /tickets/{id}.json.zendesk_list_ticket_commentsList the comments (public replies and internal notes) on a ticket, oldest first. Zendesk REST: GET /tickets/{id}/comments.json.zendesk_current_userReturn the currently authenticated user — a quick way to verify credentials and subdomain. Zendesk REST: GET /users/me.json.zendesk_get_userFetch a single user by id. Zendesk REST: GET /users/{id}.json.zendesk_search_usersFind users by name, email, phone, or other attributes. Zendesk REST: GET /users/search.json.zendesk_list_organizationsList organizations (offset pagination). Zendesk REST: GET /organizations.json.zendesk_get_organizationFetch a single organization by id. Zendesk REST: GET /organizations/{id}.json.zendesk_list_groupsList agent groups. Zendesk REST: GET /groups.json.zendesk_list_viewsList saved ticket views (curated ticket lists). Use zendesk_execute_view to run one. Zendesk REST: GET /views.json.zendesk_execute_viewRun a saved view by id and return the matching tickets. Zendesk REST: GET /views/{id}/execute.json.zendesk_list_macrosList macros (reusable sets of ticket actions/replies agents apply). Zendesk REST: GET /macros.json.zendesk_list_ticket_fieldsList all standard and custom ticket fields — useful for discovering field ids/values before creating or updating tickets. Zendesk REST: GET /ticket_fields.json.zendesk_get_ticket_metricsFetch SLA / response / resolution time metrics for a ticket. Zendesk REST: GET /tickets/{id}/metrics.json.zendesk_list_satisfaction_ratingsList customer satisfaction (CSAT) ratings, optionally filtered by score. Zendesk REST: GET /satisfaction_ratings.json.zendesk_create_ticketMUTATING: create a new support ticket. `subject` and `comment_body` are required; the comment becomes the ticket's first message. Zendesk REST: POST /tickets.json.zendesk_update_ticketMUTATING: update an existing ticket. Provide the ticket `id` plus at least one field to change (status, priority, assignee_id, group_id, type, tags, or a comment). Zendesk REST: PUT /tickets/{id}.json.zendesk_add_ticket_commentMUTATING: add a comment to a ticket. `public` defaults to true (a reply visible to the requester); set it false for an internal agent note. Convenience over PUT /tickets/{id}.json.
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.usefulapi/zendesk)