Zendesk MCP by usefulapi

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Other

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://zendesk.usefulapi.io/mcp

claude mcp add --transport http zendesk https://zendesk.usefulapi.io/mcp

{
  "mcpServers": {
    "zendesk": {
      "url": "https://zendesk.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "zendesk": {
      "type": "http",
      "url": "https://zendesk.usefulapi.io/mcp"
    }
  }
}

https://zendesk.usefulapi.io/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

• zendesk_search

  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.

• zendesk_list_tickets

  List recent tickets (offset pagination). Zendesk REST: GET /tickets.json.

• zendesk_get_ticket

  Fetch a single ticket by id. Zendesk REST: GET /tickets/{id}.json.

• zendesk_list_ticket_comments

  List the comments (public replies and internal notes) on a ticket, oldest first. Zendesk REST: GET /tickets/{id}/comments.json.

• zendesk_current_user

  Return the currently authenticated user — a quick way to verify credentials and subdomain. Zendesk REST: GET /users/me.json.

• zendesk_get_user

  Fetch a single user by id. Zendesk REST: GET /users/{id}.json.

• zendesk_search_users

  Find users by name, email, phone, or other attributes. Zendesk REST: GET /users/search.json.

• zendesk_list_organizations

  List organizations (offset pagination). Zendesk REST: GET /organizations.json.

• zendesk_get_organization

  Fetch a single organization by id. Zendesk REST: GET /organizations/{id}.json.

• zendesk_list_groups

  List agent groups. Zendesk REST: GET /groups.json.

• zendesk_list_views

  List saved ticket views (curated ticket lists). Use zendesk_execute_view to run one. Zendesk REST: GET /views.json.

• zendesk_execute_view

  Run a saved view by id and return the matching tickets. Zendesk REST: GET /views/{id}/execute.json.

• zendesk_list_macros

  List macros (reusable sets of ticket actions/replies agents apply). Zendesk REST: GET /macros.json.

• 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.

• zendesk_get_ticket_metrics

  Fetch SLA / response / resolution time metrics for a ticket. Zendesk REST: GET /tickets/{id}/metrics.json.

• zendesk_list_satisfaction_ratings

  List customer satisfaction (CSAT) ratings, optionally filtered by score. Zendesk REST: GET /satisfaction_ratings.json.

• 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.

• 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: PUT /tickets/{id}.json.

• 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.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 37 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 19 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

• More stars than 0% of the other 32484 servers in this category
• Published to the registry more recently than 99% of the other 32484 servers in this category
• Basic checks equal to or better than 100% of the other 32484 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

{