MCP connectorsZendesk

Zendesk MCP: connect Zendesk to Claude and ChatGPT

Ask Claude or ChatGPT what ticket 8812 is about, which open tickets are tagged billing, or everything a customer has raised since January. The answer comes straight from Zendesk, with public replies and internal notes kept apart.

With Deployed OS every agent connects their own Zendesk login. The AI sees the tickets that person sees, and the only thing it writes is an internal note. It never replies to a customer.

3 read actions · 1 write action · Works in Claude, ChatGPT and Copilot

In practice

What your team can do with Zendesk in Claude and ChatGPT

Support agent

Catch up before you reply

A long ticket with three handovers: get what the customer asked, what they were told and what’s only in internal notes. Then write your reply with the whole story in front of you.
Team lead

The queue before stand-up

Open and pending tickets tagged billing or marked urgent, newest first, with who owns each one. You know where the team stands before stand-up.
Account manager

The customer’s history before the call

Every ticket a customer has raised this year, with status and a one-line summary each. Ready before the renewal call, without asking support.
Product

What customers actually report

Search tickets for words like export or login over the last quarter and get the common threads, with links to the tickets behind them.
Examples

Ask it like this

  • “Summarise ticket 8812. What has the customer been told, and what’s only in internal notes?”

  • “Which open tickets tagged billing haven’t been updated since Monday?”

  • “Show every ticket from anna@acme.com this year, with status and assignee.”

  • “Find Erik Holm at Nordbyte in Zendesk and list his open tickets.”

  • “Which tickets mention invoice PDF since 1 September? Group them by what went wrong.”

  • “Add an internal note to ticket 9031: ‘Finance approved the refund on 14 October. Waiting for the bank.’”

The connector

What the Zendesk MCP connector does today

  • Readszendesk_search_tickets

    Search the tickets you can see, most recently updated first, by words or Zendesk search terms like requester, tags or created date, with one status if you want.

  • Readszendesk_get_ticket

    Read one ticket by number: status, priority, requester, assignee, organisation, tags and the latest comments in order, each marked public or internal, with attachments by name.

  • Readszendesk_search_users

    Find Zendesk users, customers and agents, by name or email address: name, email, role and organisation.

  • Writeszendesk_add_internal_note

    Add an internal note to a ticket, in your name. The customer is not emailed and nothing else on the ticket changes, though Zendesk’s own triggers may notify the assignee.

Need it to do more? We extend connectors for the companies that use them.

Security

Who sees what

Read, plus internal notes
The connector searches and reads tickets with their comments, and finds users. It can add an internal note to a ticket, in your name. It never replies to the customer and never changes status, assignee or fields.
Each agent’s own rights
Everyone connects their own Zendesk login, so the AI sees the tickets that person can see. An agent limited to their own group’s tickets in Zendesk gets only those through the AI too.
You choose who gets it
Admins decide which groups at the company get the Zendesk connector, and which of them may add notes. Everyone else never sees it.
Every call logged
Who asked, which connector, when. Deployed OS shows reads and writes per connector and per person, and the log can be exported. When someone leaves, their access is revoked centrally that day.
Setup

Set up the Zendesk connector in three steps

01
A Zendesk admin opens Admin Center → Apps and integrations → APIs → OAuth clients and adds a confidential client with the redirect URL from Deployed OS. Your company owns it, not us.
02
The admin adds the client’s Identifier and Secret to Deployed OS, with your Zendesk subdomain, and chooses which groups get Zendesk.
03
Each agent connects with their own Zendesk login. From then on they just ask.
Questions

Zendesk MCP: common questions

Not one you can connect to today, as far as we can verify in October 2026. Zendesk has announced its own, and there are open-source servers a developer can run for one person. Deployed OS gives the whole support team one Zendesk connection, with each agent’s own login, access per group and a log of every call.

No. The only thing it writes is an internal note on a ticket, in your name, after you confirm the text, and your company’s guardrails apply. The customer is not emailed and nothing else on the ticket changes, though Zendesk’s own triggers may notify the assignee. If you want it to do more, for example set a status, we can extend it for you.

Yes. Deployed OS is your company’s own MCP, so the same Zendesk connection works in ChatGPT, Claude and Copilot. Agents keep the assistant they prefer.

Yes. Every comment it reads is marked public, which the customer saw, or internal, which only agents saw. Summaries keep the two apart, so an internal note is never passed off as something the customer was told.

An admin who can add an OAuth client in Admin Center, and your subdomain (acme for acme.zendesk.com). People are asked for read access and ticket write access when they connect, and the Zendesk connector uses the write access for internal notes only.

It depends on the size of your team. Get in touch and we will walk you through it.

More connectorsAll connectors
Let’s talk

See it on your own tools.

Tell us which systems your company runs on. We’ll show you what your team can ask, and what IT gets to control.

Poyan Karimi
You’ll hear from Poyan Karimi
Co-founder · Deployed AI