Federated messaging with your fmsg hosting provider. Connect with OAuth or an API key.
Nothing to run from here
Zendesk is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
19
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read tickets, users, orgs, macros and satisfaction ratings; create, update and comment on tickets.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http usefulapi-zendesk-mcp https://zendesk.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# zendesk_search, zendesk_list_tickets, zendesk_get_ticket and 16 more
Zendesk costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http usefulapi-zendesk-mcp https://zendesk.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
19 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Unified search across tickets, users, organizations and groups using Zendesk search syntax. Examples: type:ticket status:open, type:user email:jane@acme.com, type:organization name:acme. Zendesk REST: GET /search.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Zendesk search query, e.g. 'type:ticket status:open priority:high' (required). |
| sort_by | string | no | Field to sort by. |
| sort_order | string | no | Sort direction: asc or desc (default desc). |
| page | integer | no | Page number for offset pagination. |
List recent tickets (offset pagination). Zendesk REST: GET /tickets.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sort_by | string | no | Field to sort by. |
| sort_order | string | no | Sort direction: asc or desc (default asc). |
| page | integer | no | Page number for offset pagination. |
| per_page | integer | no | Records per page (max 100). |
Fetch a single ticket by id. Zendesk REST: GET /tickets/{id}.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Numeric ticket id (required). |
List the comments (public replies and internal notes) on a ticket, oldest first. Zendesk REST: GET /tickets/{id}/comments.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Numeric ticket id (required). |
| page | integer | no | Page number for offset pagination. |
| per_page | integer | no | Records per page (max 100). |
Return the currently authenticated user — a quick way to verify credentials and subdomain. Zendesk REST: GET /users/me.json.
No parameter schema on file.
Fetch a single user by id. Zendesk REST: GET /users/{id}.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Numeric user id (required). |
Find users by name, email, phone, or other attributes. Zendesk REST: GET /users/search.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search string — a name, email, phone, or external id, e.g. 'jane@acme.com' (required). |
| page | integer | no | Page number for offset pagination. |
| per_page | integer | no | Records per page (max 100). |
List organizations (offset pagination). Zendesk REST: GET /organizations.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number for offset pagination. |
| per_page | integer | no | Records per page (max 100). |
Fetch a single organization by id. Zendesk REST: GET /organizations/{id}.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Numeric organization id (required). |
List agent groups. Zendesk REST: GET /groups.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number for offset pagination. |
| per_page | integer | no | Records per page (max 100). |
List saved ticket views (curated ticket lists). Use zendesk_execute_view to run one. Zendesk REST: GET /views.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| access | string | no | Filter by access: 'personal' or 'shared'. |
| active | boolean | no | If true, only active views. |
Run a saved view by id and return the matching tickets. Zendesk REST: GET /views/{id}/execute.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Numeric view id (required; from zendesk_list_views). |
| sort_by | string | no | Field to sort the resulting tickets by. |
| sort_order | string | no | Sort direction: asc or desc. |
| page | integer | no | Page number for offset pagination. |
| per_page | integer | no | Records per page (max 100). |
List macros (reusable sets of ticket actions/replies agents apply). Zendesk REST: GET /macros.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| access | string | no | Filter by access, e.g. 'personal' or 'shared'. |
| active | boolean | no | If true, only active macros. |
List all standard and custom ticket fields — useful for discovering field ids/values before creating or updating tickets. Zendesk REST: GET /ticket_fields.json.
No parameter schema on file.
Fetch SLA / response / resolution time metrics for a ticket. Zendesk REST: GET /tickets/{id}/metrics.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Numeric ticket id (required). |
List customer satisfaction (CSAT) ratings, optionally filtered by score. Zendesk REST: GET /satisfaction_ratings.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| score | string | no | Filter by rating state, e.g. 'good', 'bad', or 'received'. |
| page | integer | no | Page number for offset pagination. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subject | string | yes | Ticket subject/title (required). |
| comment_body | string | yes | Body of the ticket's first comment (required). |
| comment_public | boolean | no | Whether the first comment is public (default true). |
| requester_id | integer | no | User id of the ticket requester. |
| assignee_id | integer | no | Agent id to assign the ticket to. |
| group_id | integer | no | Group id to assign the ticket to. |
| priority | string | no | Priority: urgent | high | normal | low. |
| type | string | no | Type: problem | incident | question | task. |
| status | string | no | Status: new | open | pending | hold | solved | closed. |
| tags | array | no | Tags to set on the 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: PUT /tickets/{id}.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Numeric ticket id (required). |
| status | string | no | New status: new | open | pending | hold | solved | closed. |
| priority | string | no | New priority: urgent | high | normal | low. |
| assignee_id | integer | no | Agent id to (re)assign to. |
| group_id | integer | no | Group id to (re)assign to. |
| type | string | no | New type: problem | incident | question | task. |
| tags | array | no | Tags to set on the ticket (replaces existing). |
| comment_body | string | no | Body of a comment to add as part of this update. |
| comment_public | boolean | no | Whether the added comment is public (default true; set false for an internal note). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Numeric ticket id (required). |
| body | string | yes | Comment text (required). |
| public | boolean | no | Public reply (true, default) or internal note (false). |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Zendesk or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.11.1 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestd0b9629034345cd336793869331776a6619ce7215021e864f96407a48db79fa7
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| zendesk_search | no tags | |
| zendesk_list_tickets | no tags | |
| zendesk_get_ticket | untrusted-input | untrusted-input: keyword "fetch" |
| zendesk_list_ticket_comments | no tags | |
| zendesk_current_user | no tags | |
| zendesk_get_user | untrusted-input | untrusted-input: keyword "fetch" |
| zendesk_search_users | no tags | |
| zendesk_list_organizations | no tags | |
| zendesk_get_organization | untrusted-input | untrusted-input: keyword "fetch" |
| zendesk_list_groups | no tags | |
| zendesk_list_views | no tags | |
| zendesk_execute_view | no tags | |
| zendesk_list_macros | no tags | |
| zendesk_list_ticket_fields | no tags | |
| zendesk_get_ticket_metrics | untrusted-input | untrusted-input: keyword "fetch" |
| zendesk_list_satisfaction_ratings | no tags | |
| zendesk_create_ticket | state-write | state-write: declares destructiveHint: true |
| zendesk_update_ticket | state-write | state-write: declares destructiveHint: true |
| zendesk_add_ticket_comment | state-write | state-write: declares destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestd0b9629034345cd3
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.1.
1.11.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Zendesk can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.