Zendesk logo zendesk.com

Live

Zendesk API and MCP server

Zendesk's API covers tickets, replies and macros, but it takes an OAuth client and code you write and host. Sign in to Zendesk once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.

Sign up free View as Markdown

Not affiliated with Zendesk.

Zendesk has no API for this. So we run one for you.

Zendesk's own API, a GitHub MCP server and Cotlet compared
What you need Zendesk's APIGitHub MCP serverCotlet
Use without an API key or code No Partly Yes, 12 tools
Acts as you, signed in 24/7 No No Yes, Cloud Browser
Fixed for you when Zendesk changes N/A No Yes, tested every 6h
Runs with your laptop off N/A No Yes, hosted

Checked Oct 16, 2026. Sources: Zendesk Help: Announcing the removal of API tokens as an authentication method · Zendesk developers: Migrating from API tokens to OAuth access tokens · Zendesk Help: Connecting to MCP servers and using MCP tools in action flows · Zendesk developers: Support API rate limits

Your own Cloud Browser, on 24/7. Sign in once. We keep it connected.

  1. 01Sign in to Zendesk in your own Cloud Browser

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect Zendesk to Claude, ChatGPT or my code?

AI agents connect over MCP, scripts call the REST API. Both reach the same 12 tools with one API key.

For AI agents: MCP

Add Cotlet to your agent once. Zendesk and every other app you connect show up as its tools.

  • Claude
  • ChatGPT
  • OpenClaw
  • Hermes
  • GrokBot
  • Cursor
  • n8n
  • Any MCP client
  1. 1

    Add Cotlet to your agent

    Claude Code
    claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
    Cursor
    {
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
    Codex
    # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

For scripts: REST API

Every tool is an endpoint under /api/v1/zendesk with its own method and path, such as POST /api/v1/zendesk/tickets/{ticket_id}/replies, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the Zendesk API and MCP server do?

12 tools on your own Zendesk account. Agents call them as operations of the MCP tools zendesk_read and zendesk_write; scripts call each one at its own REST endpoint, with the same inputs and answers.

API reference
Zendesk tools in Cotlet's MCP server and REST API
Tool What it does Access
search_tickets Tickets that match a Zendesk search query, with status, priority, requester and assignee. read
get_ticket One ticket with its fields, tags and every comment, public and internal. read
list_views Ticket views you can open: shared views and your personal ones. read
list_view_tickets Tickets in one view, in the view's own order. read
list_macros Active macros with ID, title and description. read
list_groups Support groups with ID and name. read
list_agents Agents and admins who can be assigned tickets, with role. read
reply_to_ticket Add a public reply to a ticket and optionally set its status in the same call. writeasks first
add_internal_note Add a private note only agents can see. writeasks first
update_ticket Change status, priority, assignee, group, subject or tags of one ticket. writeasks first
apply_macro Apply a macro to one ticket and save the result. writeasks first
merge_tickets Merge one ticket into another and close the source ticket. writeasks first

Scroll the table for all 12 tools.

Ask in plain words. Your agent does the rest.

All Zendesk use cases

Is it safe to connect Zendesk?

You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.

Security overview

How much do the Zendesk API and MCP server cost?

One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Most calls use 25 credits, and your Cloud Browser uses 50 credits a day while Zendesk is enabled for agents, so 20 calls a day come to 550 credits.

See full pricing
Cotlet credit packs: price, credits and calls at 25 credits each
Credits Price, one time Calls at 25 credits Per 1,000 credits
5,000 $29 200 $5.80
15,000 $79 600 $5.27
32,000 $149 1,280 $4.66
60,000 $249 2,400 $4.15

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.

Questions

Does Zendesk have an API?

Zendesk has a full REST API, the Support API (also called the Ticketing API), but no documented Zendesk-hosted MCP server for working tickets (checked 16 Oct 2026). Zendesk's MCP documentation covers the MCP client, where Zendesk calls other servers. API tokens are being removed: no new ones from 27 Oct 2026, all remaining ones stop on 30 Apr 2027, and OAuth takes over.

How do I get access?

Sign up free, open Zendesk under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.

Is the MCP server different from the API?

No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 12 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.

What is the Cloud Browser?

Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to Zendesk yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so Zendesk sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.

Can my agent act without asking me?

Not on anything that reaches other people: reply_to_ticket, add_internal_note, update_ticket, apply_macro, merge_tickets wait for your OK by default. You can switch that off per tool for scheduled runs.

Will my agent send replies to customers without asking?

Only if you switch confirmation off. By default every reply, note, update, macro and merge waits for your OK. A public reply emails the requester and a comment cannot be removed from a ticket afterwards (Zendesk Help: Adding comments to tickets).

Should I use a Zendesk MCP server from GitHub instead?

Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when Zendesk changes. Pick Cotlet if you want it hosted and kept working for you.

Can I use it in n8n, Make or Zapier?

Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.

Who runs Cotlet?

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

Is Cotlet affiliated with Zendesk?

No. Cotlet is independent and not affiliated with Zendesk.

Give your agent access to Zendesk.

Free 7-day trial with 2,000 credits, no card needed.

Sign up free