Zendesk MCP Server

io.usefulapi/zendesk

answering

Zendesk is answering right now. Last checked 3 min ago. It exposes 19 tools. Last commit 1 Aug 2026.

Read tickets, users, orgs, macros and satisfaction ratings; create, update and comment on tickets.

Uptime history 46 hours of history · worst hour 0%

46 hours agonow

21.7%

Uptime 24h

20 of 92 checks

Tools

read from the server

181 ms

Response time

average over 24h

Stars

last commit 1 Aug 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

[mcp_servers.zendesk]
url = "https://zendesk.usefulapi.io/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 19

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

zendesk

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.

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_current_user

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

zendesk_execute_view

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

zendesk_get_organization

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

zendesk_get_ticket

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

zendesk_get_ticket_metrics

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

zendesk_get_user

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

zendesk_list_groups

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

zendesk_list_macros

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

zendesk_list_organizations

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

zendesk_list_satisfaction_ratings

List customer satisfaction (CSAT) ratings, optionally filtered by score. Zendesk REST: GET /satisfaction_ratings.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_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_list_tickets

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

zendesk_list_views

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

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 name:acme`. Zendesk REST: GET /search.json.

zendesk_search_users

Find users by name, email, phone, or other attributes. Zendesk REST: GET /users/search.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.

Endpoints

URL	Transport	State	Latency	Checked
https://zendesk.usefulapi.io/mcp	streamable-http	answering	168 ms	3 min ago

Zendesk — questions

Answers built from our own checks of this server.

What can Zendesk do?

It exposes 19 tools, read directly from the server on our last check. Among them: zendesk_add_ticket_comment, zendesk_create_ticket, zendesk_current_user, zendesk_execute_view, zendesk_get_organization, zendesk_get_ticket and 13 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Zendesk working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 20 of 92 checks got a reply (21.7%), average response time 181 ms. The bar chart above shows every period we have measured.

How do I connect Zendesk?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Zendesk need an API key?

No. Zendesk completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 19 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Zendesk?

It answers our handshake in 181 ms on average, which is faster than 67% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Zendesk open source?

Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.