Read tickets, users, orgs, macros and satisfaction ratings; create, update and comment on tickets. For support agents and support managers who handle tickets in Zendesk. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"zendesk": {
"url": "https://zendesk.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"zendesk": {
"type": "http",
"url": "https://zendesk.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The AI searches tickets, users and organizations with Zendesk search syntax, such as open tickets of one organization. You can also run a saved view.
zendesk_search zendesk_list_views zendesk_execute_view
The AI opens a ticket and lists its public replies and internal notes, oldest first. It can sum up the conversation.
zendesk_get_ticket zendesk_list_ticket_comments
The AI reads SLA, response and resolution time metrics for a ticket. You see whether it met its targets.
zendesk_get_ticket_metrics zendesk_get_ticket
The AI lists satisfaction (CSAT) ratings, filtered by score, with the tickets behind them. You see where customers were unhappy.
zendesk_list_satisfaction_ratings zendesk_get_ticket
The AI creates a ticket, adds a public reply or an internal note, or changes the status, priority, assignee, group or tags of a ticket.
Changes data · zendesk_create_ticket zendesk_add_ticket_comment zendesk_update_ticket
The login page asks for your Zendesk subdomain, Agent email and Zendesk API token.
Create a token in Zendesk → Admin Center → Apps and integrations → APIs → Zendesk API. Your credentials are used only to call the API on your behalf and to derive a private account id; they are never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Zendesk subdomain, Agent email and Zendesk API token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Zendesk connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
zendesk_search | read | 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_list_tickets | read | List tickets List recent tickets (offset pagination). Zendesk REST: GET /tickets.json. |
zendesk_get_ticket | read | Get ticket Fetch a single ticket by id. Zendesk REST: GET /tickets/{id}.json. |
zendesk_list_ticket_comments | read | 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 | read | Current user (whoami) Return the currently authenticated user — a quick way to verify credentials and subdomain. Zendesk REST: GET /users/me.json. |
zendesk_get_user | read | Get user Fetch a single user by id. Zendesk REST: GET /users/{id}.json. |
zendesk_search_users | read | Search users Find users by name, email, phone, or other attributes. Zendesk REST: GET /users/search.json. |
zendesk_list_organizations | read | List organizations List organizations (offset pagination). Zendesk REST: GET /organizations.json. |
zendesk_get_organization | read | Get organization Fetch a single organization by id. Zendesk REST: GET /organizations/{id}.json. |
zendesk_list_groups | read | List groups List agent groups. Zendesk REST: GET /groups.json. |
zendesk_list_views | read | List views List saved ticket views (curated ticket lists). Use zendesk_execute_view to run one. Zendesk REST: GET /views.json. |
zendesk_execute_view | read | Execute view Run a saved view by id and return the matching tickets. Zendesk REST: GET /views/{id}/execute.json. |
zendesk_list_macros | read | List macros List macros (reusable sets of ticket actions/replies agents apply). Zendesk REST: GET /macros.json. |
zendesk_list_ticket_fields | read | 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 | read | Get ticket metrics Fetch SLA / response / resolution time metrics for a ticket. Zendesk REST: GET /tickets/{id}/metrics.json. |
zendesk_list_satisfaction_ratings | read | List satisfaction ratings List customer satisfaction (CSAT) ratings, optionally filtered by score. Zendesk REST: GET /satisfaction_ratings.json. |
zendesk_create_ticket | write | 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 | write | 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 | write | 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_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
zendesk_request_feature | Request a missing feature Tell usefulapi that the user needs something the Zendesk tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
zendesk_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Zendesk (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
zendesk_cancel_subscription | Cancel the Pro subscription Cancel the caller's Zendesk Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run zendesk_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Zendesk server only. Subscribe with zendesk_upgrade (it returns a Stripe Checkout link). Cancel any time with zendesk_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running zendesk_upgrade before then undoes the cancel. Or write to [email protected].
Find tickets with Zendesk search. Read a ticket with its comments. Check response and resolution times of a ticket. Find customers who gave a low satisfaction rating. Create a ticket, reply or update a ticket. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Zendesk. The server calls the Zendesk API with your own Zendesk access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Zendesk subdomain, Agent email and Zendesk API token. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Zendesk subdomain, Agent email and Zendesk API token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Zendesk API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Zendesk.
Yes, if you approve it. 3 of the 19 Zendesk tools can create or change data. The other 16 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Zendesk server only. Cancel any time: Pro then runs to the end of the paid period. Run zendesk_usage_status to see how many calls you used.
Ask the AI to run zendesk_upgrade: it returns a Stripe Checkout link. To cancel, run zendesk_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with zendesk_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.