# Zendesk API MCP Server A comprehensive Model Context Protocol (MCP) server for interacting with the Zendesk API. This server provides tools and
Connect Zendesk API to Claude, Cursor or any other MCP client and it stops being a tab you switch to. # Zendesk API MCP Server A comprehensive Model Context Protocol (MCP) server for interacting with the Zendesk API. This server provides tools and resources for managing Zendesk Support, Talk, Chat, and Guide products. ## Features -. The zendesk api mcp server is what makes that connection.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
list_tickets — List tickets in Zendeskget_ticket — Get a specific ticket by IDcreate_ticket — Create a new ticketupdate_ticket — Update an existing ticketdelete_ticket — Delete a ticketlist_users — List users in Zendeskget_user — Get a specific user by IDcreate_user — Create a new userupdate_user — Update an existing userdelete_user — Delete a userlist_organizations — List organizations in Zendeskget_organization — Get a specific organization by IDConfiguration is passed through the environment: ZENDESK_API_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Zendesk API's toolset — list_tickets, get_ticket, create_ticket and 11 more — is a fair guide to whether it matches your workflow. It is maintained by mattcoatsworth; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| list_tickets | List tickets in Zendesk |
| get_ticket | Get a specific ticket by ID |
| create_ticket | Create a new ticket |
| update_ticket | Update an existing ticket |
| delete_ticket | Delete a ticket |
| list_users | List users in Zendesk |
| get_user | Get a specific user by ID |
| create_user | Create a new user |
| update_user | Update an existing user |
| delete_user | Delete a user |
| list_organizations | List organizations in Zendesk |
| get_organization | Get a specific organization by ID |
| create_organization | Create a new organization |
| update_organization | Update an existing organization |
| Variable | Description | Required |
|---|---|---|
| ZENDESK_API_TOKEN | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.