MCP serverio.usefulapi/zendesk
Read tickets, users, orgs, macros and satisfaction ratings; create, update and comment on tickets.
Overview
Score?
UNRATED 0.093
of what a free look can see, on 17 looks
Looks
35
last 15 hr ago
Tools
19
More info
URL
zendesk.usefulapi.io/mcp
streamable-http
Says it is
zendesk-mcp 1.0.0
protocol 2025-06-18
In the record since
32 days ago
Among servers18,413 with a card
0median 0.606 · this server 0.093 · highest on record 0.8561
Toolsfrom sha256:9db6c69436…85bf6a
| Tool | Schema |
|---|---|
| zendesk_add_ticket_comment MUTATING: 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. |
input · no output |
| zendesk_create_ticket MUTATING: create a new support ticket. `subject` and `comment_body` are required; the comment becomes the ticket's first message. Zendesk REST: POST /tickets.json. |
input · no output |
| zendesk_current_user Return the currently authenticated user — a quick way to verify credentials and subdomain. Zendesk REST: GET /users/me.json. |
input · no output |
| zendesk_execute_view Run a saved view by id and return the matching tickets. Zendesk REST: GET /views/{id}/execute.json. |
input · no output |
| zendesk_get_organization Fetch a single organization by id. Zendesk REST: GET /organizations/{id}.json. |
input · no output |
| zendesk_get_ticket Fetch a single ticket by id. Zendesk REST: GET /tickets/{id}.json. |
input · no output |
| zendesk_get_ticket_metrics Fetch SLA / response / resolution time metrics for a ticket. Zendesk REST: GET /tickets/{id}/metrics.json. |
input · no output |
| zendesk_get_user Fetch a single user by id. Zendesk REST: GET /users/{id}.json. |
input · no output |
| zendesk_list_groups List agent groups. Zendesk REST: GET /groups.json. |
input · no output |
| zendesk_list_macros List macros (reusable sets of ticket actions/replies agents apply). Zendesk REST: GET /macros.json. |
input · no output |
| zendesk_list_organizations List organizations (offset pagination). Zendesk REST: GET /organizations.json. |
input · no output |
| zendesk_list_satisfaction_ratings List customer satisfaction (CSAT) ratings, optionally filtered by score. Zendesk REST: GET /satisfaction_ratings.json. |
input · no output |
| zendesk_list_ticket_comments List the comments (public replies and internal notes) on a ticket, oldest first. Zendesk REST: GET /tickets/{id}/comments.json. |
input · no output |
| zendesk_list_ticket_fields List all standard and custom ticket fields — useful for discovering field ids/values before creating or updating tickets. Zendesk REST: GET /ticket_fields.json. |
input · no output |
| zendesk_list_tickets List recent tickets (offset pagination). Zendesk REST: GET /tickets.json. |
input · no output |
| zendesk_list_views List saved ticket views (curated ticket lists). Use zendesk_execute_view to run one. Zendesk REST: GET /views.json. |
input · no output |
| zendesk_search Unified search across tickets, users, organizations and groups using Zendesk search syntax. Examples: `type:ticket status:open`, `type:user email:[email protected]`, `type:organization |
input · no output |
| zendesk_search_users Find users by name, email, phone, or other attributes. Zendesk REST: GET /users/search.json. |
input · no output |
| zendesk_update_ticket MUTATING: 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: PU |
input · no output |
Verify it yourself
npx teppi-check https://zendesk.usefulapi.io/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M1FZ2PNPNH6MNWZRA6YNXH43