Helpdesk
Zendesk MCP connector
The Zendesk connector brings tickets, comments, requesters, attachments and audit logs into Claude, ChatGPT, Cursor and the Elaichi Agent, so each agent works their queue as themselves with every action recorded.
-
How it connects. OAuth or API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Zendesk to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Zendesk once
-
Open Connections, choose Add connection, and pick Zendesk.
-
Optionally set Share with to give a team access, then press Connect.
-
Supply your own Zendesk app, then approve. Zendesk needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Zendesk to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Zendesk to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Zendesk to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Zendesk to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Zendesk through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Support
Catch a ticket up after a call
Tell the agent what the customer said on the phone and it adds the internal note, changes the status and sets the priority on the Zendesk ticket for you.
-
Support
Find every ticket about one issue
Ask for all open Zendesk tickets mentioning a login error this week and get a short read of what customers are reporting and how many are waiting.
-
Support leadership
Reassign a backlog in one pass
Move every unassigned ticket tagged billing to the billing group and mark them pending, then check the count to confirm the queue is clear.
-
Customer success
Brief yourself before a renewal call
Pull a customer's recent Zendesk tickets and the comment history, and get a plain summary of what went wrong, what was fixed and what is still open.
-
Sales
Check a prospect's support history first
Before a follow-up, see whether anyone at the account has an open or recently escalated ticket so the conversation does not start on the wrong foot.
-
IT and admin
See who changed what in Zendesk
Ask which admin edited a ticket field, custom status or account setting last month and get the answer from the Zendesk audit log without clicking through it.
Try asking
- “Summarize open Zendesk tickets for the escalations queue.”
- “How many tickets did each agent close this week?”
- “Find tickets with comments still waiting on a reply.”
AI tools
Zendesk tools for your AI agents
373 tools are ready to call through Elaichi's MCP endpoint the moment you connect Zendesk, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Zendesk gets you
6 screens from the product, each doing one job for your Zendesk account.
The agent
Ask about tickets, read the answer.
Plain language questions answered from live Zendesk tickets, users and comments.
- tickets
- users
- comments
- audit logs
Ask Elaichi to work across your apps.
Summarize open Zendesk tickets for the escalations queue.
How many tickets did each agent close this week?
Find tickets with comments still waiting on a reply.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One Zendesk endpoint for every MCP client.
Claude, ChatGPT and Cursor connect over OAuth, no SDK, no shared API key.
Copy the endpoint
Tool catalog
373 Zendesk tools, no custom code.
Tickets, users, comments, search and audit logs, each with methods listed.
- List all Zendesk users
- Get single Zendesk user by ID
- Delete a Zendesk user by ID
- Update a Zendesk user by ID
Toolboxes
Every team gets its own Zendesk toolbox.
Support, escalations and reporting each see a curated set of Zendesk tools.
- Support
- Escalations
- Customer Success
- Quality
Shared connections
Teammates use Zendesk without seeing credentials.
Each connection shows who connected it and which teams and members share it.
- Support EMEA
- Support Americas
- Escalations
- Customer Success
Audit log
Every Zendesk call is on the record.
When, who, what happened, type and resource for each ticket and user action.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, the ticket digest ships.
Zendesk tickets are fetched, grouped, drafted by an agent, approved, then posted back.
Zendesk digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch tickets
Zendesk
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Zendesk
Queued
Collections and dashboards
Zendesk ticket numbers, computed not asked.
Four metrics, 14 days of tickets created and a team breakdown, refreshed on schedule.
Zendesk health
Refreshed 4 minutes ago · every 15 minutes · from the tickets collection
Tickets
1,284 ↓ 12%
Users
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Tickets created
Last 14 days
By team
Share of activity
Support EMEA 34%
Support Americas 27%
Escalations 21%
Customer Success 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Zendesk to Claude?
Connect Zendesk in Elaichi first. Zendesk asks for an OAuth application registered inside your own Zendesk admin center, so a Zendesk admin creates it once and brings its client ID and secret to Elaichi; after that, each person simply signs in to Zendesk with their own account, or an API token can be used instead. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is nothing else to generate on the Claude side.
Does Zendesk work with ChatGPT and Cursor as well as Claude?
Yes. Once Zendesk is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Zendesk once and every client sees it.
What can an AI agent actually do with my Zendesk data?
It can find tickets by keyword, requester or status, read the comment thread, create a new ticket, update the status, priority or assignee on one ticket or many at once, count how many are waiting, look up and edit users, download or attach files, and read the audit log and account settings. Zendesk exposes a lot through this connector, so short concrete asks such as "reassign the open billing tickets to Dana" work better than long paragraphs.
Does connecting Zendesk give the AI everything in my help center?
No. Every request runs as the person who signed in to Zendesk, so an agent who cannot see another group's tickets or edit account settings in Zendesk cannot do it through Claude either. Elaichi can narrow that access further, for example to read-only, but it can never grant more than the person already has in Zendesk.
Can I stop an agent from deleting or changing things in Zendesk?
Yes. Restrictions in Elaichi apply per action, so you can allow reading and commenting on Zendesk tickets while blocking deleting tickets or users, or blocking bulk updates entirely. A blocked action is never shown to Claude, ChatGPT or Cursor in the first place, so no prompt, however worded, can reach it.
What happens to a Zendesk connection when someone leaves?
When you offboard a person in Elaichi their access to Zendesk through every AI client ends at once. A Zendesk connection they shared with the team keeps working for everyone else. If you want Zendesk gone altogether, disconnect it once in Elaichi and it disappears from Claude, ChatGPT, Cursor and every other client at the same time.
Put Zendesk in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.