---
title: "Zendesk Support MCP server for AI agents - actionlake"
description: "Give Claude 559 Zendesk Support actions through one MCP server: ticketing, people, groups. Your agent never holds the credential. 100,000 calls a month free."
canonical: https://actionlake.com/connectors/zendesk-support
updated: 2026-10-10
---

Connectors · Service desk & support

# Zendesk Support MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Zendesk Support and the rest of your systems. It gives your agent 559 Zendesk Support actions (304 reads, 173 writes and 82 that wait for a confirmation) and holds the Zendesk Support credential itself, so the agent never does. It paces Zendesk Support's limits and records every call.

[Connect Zendesk Support free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

`claude mcp add --transport http actionlake https://connect.actionlake.com/mcp`

the first call

```
do {
  action: "zendesk_support.users.list",
  intent: "check which Zendesk Support account is connected"
}
# List Users · read · 1 upstream call
```

- 559 actions in one signed file
- 304 read look, never change
- 173 write create and update
- 82 wait for a yes destructive, confirmed first

Set up

## Connect Zendesk Support in three steps.

1. 01
   ### Add actionlake to Claude.
   Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
   `https://connect.actionlake.com/mcp`
2. 02
   ### Connect Zendesk Support.
   Username and secret. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.
   - `email` Zendesk agent email
   - `api_token` Zendesk API token
   - `subdomain_host` Where your Zendesk Support lives: your subdomain host
   ```
   account { op: "connections.requirements", service: "zendesk_support" }
   # free: exactly what to paste, and what is found for you
   ```
3. 03
   ### Make the first call. Check before a write.
   Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free.
   ```
   do    { action: "zendesk_support.users.list" }
   # list users · read · 1 upstream call
   check { action: "zendesk_support.users.create", input: { … } }
   # free: inputs, permissions, cost and confirmations, nothing sent
   ```

Zendesk Support at a glance

**Sign-in**

Username and secret. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.

**You provide**

`email` `api_token`

**Setup fields**

`subdomain_host`

**Limits we pace to**

400 calls a minute, per connection

**API covered**

Zendesk Support API 2, at your Zendesk Support instance's API base URL, which you enter when connecting (path /api/v2)

**Built from**

Zendesk Support's documentation, read 14 September 2026[developer.zendesk.com](https://developer.zendesk.com/zendesk/oas.yaml) [developer.zendesk.com](https://developer.zendesk.com/api-reference/ticketing/introduction/)

**Service file**

Version 2.0.0, signed (Ed25519)

**Cached reads**

300 of 304 reads, for up to an hour; a write clears what it affects

**Ready-made plans**

10 in the store

**Shared entities**

5, so ask can line Zendesk Support up with your other systems

**Data**

Processed and stored in Sydney, Australia. No US region yet

Capabilities

## What an AI agent can do in Zendesk Support.

559 actions in 5 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

- **304** read look, never change
- **173** write create and update
- **82** destructive wait for a confirmation

1. ### Ticketing
   477
   256 read · 152 write · 69 destructive
   List Tickets · List Comments · List Macro Groups · List Requests
2. ### People
   32
   19 read · 8 write · 5 destructive
   List Users · Autocomplete Users · Show Compliance Deletion Statuses · Show Many Users
3. ### Groups
   26
   16 read · 6 write · 4 destructive
   List Groups · List Available Agents · Autocomplete Groups · List Assignable Groups
4. ### Accounts
   19
   11 read · 5 write · 3 destructive
   List Organizations · Show Many Organizations · List Organization Merges · List User Organizations
5. ### Roles
   5
   2 read · 2 write · 1 destructive
   List Custom Roles · Create Custom Role · Show Custom Role · Update Custom Role

Top actions

## The Zendesk Support API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 244 of Zendesk Support's 258 action names are shared with at least one other connector, so an agent learns them once.

| Action | What it does | Effect | Same name in |
| --- | --- | --- | --- |
| `zendesk_support.users.list` List Users | List Users — returns the users collection, paged. | read | `identity.user.list` 474 connectors |
| `zendesk_support.groups.list` List Groups | List Groups — returns the groups collection, paged. | read | `identity.group.list` 262 connectors |
| `zendesk_support.tickets.list` List Tickets | List Tickets — returns the tickets collection, paged. | read | `service.ticket.list` 56 connectors |
| `zendesk_support.ticket_comments.list` List Comments | List Comments — returns the comments collection, paged. | read | `service.ticket_note.list` 20 connectors |
| `zendesk_support.users.get_many` Show Many Users | Show Many Users — returns the users collection, paged. | read | `identity.user.list` 474 connectors |
| `zendesk_support.users.create` Create User | Create User — creates a user and returns it. | write | `identity.user.create` 262 connectors |
| `zendesk_support.groups.list_user` List User Groups | List User Groups — returns the groups collection, paged. | read | `identity.group.list` 262 connectors |
| `zendesk_support.users.create_many` Create Many Users | Create Many Users — creates a user and returns it. | write | `identity.user.create` 262 connectors |
| `zendesk_support.organizations.list` List Organizations | List Organizations — returns the organizations collection, paged. | read | `crm.company.list` 162 connectors |
| `zendesk_support.requests.list` List Requests | List Requests — returns the requests collection, paged. | read | `service.ticket.list` 56 connectors |
| `zendesk_support.tickets.create` Create Ticket | Create Ticket — creates a ticket and returns it. | write | `service.ticket.create` 54 connectors |
| `zendesk_support.users.delete` Delete User | Delete User — removes the record, permanently. | destructive | `identity.user.delete` 253 connectors |

Try it

## Prompts to paste into Claude.

Each one names the Zendesk Support actions it will call, so you know what it reads and what it changes before you send it.

1. Read read
   Which Zendesk Support tickets have been open the longest? Show me the ten oldest with their status.
   calls `zendesk_support.tickets.list`
2. Plan destructive
   Offboard a departing agent from groups and sessions in Zendesk Support. Ask me before anything is sent or changed.
   calls `zendesk_support.users.get` `zendesk_support.tickets.count_user_assigned` `zendesk_support.group_memberships.list_user` `zendesk_support.sessions.list_user` `zendesk_support.sessions.delete` +1 more
3. Plan write
   Onboard a new customer organization and its contacts in Zendesk Support.
   calls `zendesk_support.groups.create` `zendesk_support.tags.set_organization` `zendesk_support.users.create_or_update_many` `zendesk_support.organizations.update` `zendesk_support.organization_memberships.create` +1 more
4. Write write
   Create User in Zendesk Support. Show me exactly what you will send before you save it.
   calls `zendesk_support.users.create`
5. Across systems read
   Which Zendesk Support companies have invoices in ConnectWise PSA, and how many each?
   calls `zendesk_support.organizations.list` `connectwise_manage.invoices.list`

Across your systems

## Zendesk Support, joined to the rest of your business.

One `ask` fetches from Zendesk Support and another system, joins the rows on the same customer on our side, and hands your agent the answer, not every row.

- Which Zendesk Support companies have invoices in ConnectWise PSA, and how many each?
  `zendesk_support.organizations.list` + `connectwise_manage.invoices.list`, on `crm.company` · [ConnectWise PSA](https://actionlake.com/connectors/connectwise-psa)
- Which Zendesk Support companies have invoices in NetSuite, and how many each?
  `zendesk_support.organizations.list` + `netsuite.views.invoices`, on `crm.company` · [NetSuite](https://actionlake.com/connectors/netsuite)

Also mapped by other connectors `identity.user` **517** `identity.group` **239** `crm.company` **227** `service.ticket` **62** `service.ticket_note` **5**

ask

```
ask {
  intent: "which Zendesk Support companies have invoices in ConnectWise PSA, and how many each",
  steps: [
    { action: "zendesk_support.organizations.list", as: "co", input: {}, limit: 100, max_pages: 5 },
    { action: "connectwise_manage.invoices.list", as: "inv", input: {}, limit: 100, max_pages: 5 },
    { join: {
        left: "co",
        right: "inv",
        on: "crm.company",
        group_by: "co.name",
        select: ["co.name", "count(inv.id) as invoices"]
    } }
  ]
}
```

Example. Run it through check first: it validates the steps and prices them, and it is free.

The plan store

## Ready-made plans for Zendesk Support.

10 plans in the store. Install one and your agent runs it by name; the reply says which connections are still missing. A schedule can run a plan on a timetable. There are no triggers or webhooks, by design.

1. ### Triage open problem tickets and tag the stale ones
   Use it when A support lead wants the current problem tickets reviewed and tagged for follow-up.
   **Effect**
   write
   **Steps**
   2 · loops
   **Needs**
   triage tag
   **Install**
   `zendesk_support-triage-problem-tickets`
2. ### Export the audit log and wait for the job to finish
   Use it when Security or compliance asks for an audit log export covering a particular actor or time window.
   **Effect**
   write
   **Steps**
   4
   **Needs**
   audit log, filter actor id, filter created at and sample audit log id
   **Install**
   `zendesk_support-export-audit-log`
3. ### Review a suspended ticket and recover it
   Use it when A message was caught in the suspended queue and someone must decide whether to let it through.
   A person decides Recover this suspended ticket into the live queue — it is a genuine customer request, not spam.
   **Effect**
   write
   **Steps**
   4
   **Needs**
   suspended ticket and suspended ticket id
   **Install**
   `zendesk_support-recover-suspended-tickets`
4. ### Sweep a view for SLA breaches and flag them
   Use it when A duty manager wants the at-risk tickets in an SLA view checked and flagged before the shift ends.
   **Effect**
   write
   **Steps**
   4 · loops
   **Needs**
   breach tag, sla policy id and view id
   **Install**
   `zendesk_support-sla-breach-sweep`
5. ### Onboard a new customer organization and its contacts
   Use it when A new customer has signed and their organization, owning group and contacts must be set up in Zendesk.
   **Effect**
   write
   **Steps**
   6 · loops
   **Needs**
   group, organization, organization id, tag and users
   **Install**
   `zendesk_support-onboard-customer-organization`
6. ### Redact a string and its attachment from a ticket comment
   Use it when A customer or auditor asks for card numbers, credentials or personal data to be scrubbed from a ticket.
   A person decides Permanently redact the named string and attachment from this ticket comment. Redaction cannot be reversed.
   **Effect**
   write
   **Steps**
   6
   **Needs**
   attachment, attachment id, comment id, ticket comment, ticket comment id and ticket id
   **Install**
   `zendesk_support-redact-sensitive-comment`
7. ### Permanently purge soft-deleted users after sign-off
   Use it when Someone needs soft-deleted Zendesk users erased for good under a retention or GDPR obligation.
   A person decides Permanently erase every soft-deleted Zendesk user in the list above. This cannot be undone.
   **Effect**
   destructive
   **Steps**
   4 · loops
   **Install**
   `zendesk_support-purge-deleted-users`
8. ### Find and retire automations matching a search term
   Use it when An admin is cleaning up automations left over from a retired product, brand or workflow.
   A person decides Delete every automation matching the search term above. Deleted automations cannot be restored.
   **Effect**
   destructive
   **Steps**
   4 · loops
   **Needs**
   query
   **Install**
   `zendesk_support-retire-stale-automations`
9. ### Replace duplicate macros with one canonical macro
   Use it when The macro list has drifted into several near-identical macros and an admin wants one canonical version.
   A person decides Delete the duplicate macros found above, now that the canonical macro exists. Deleted macros cannot be restored.
   **Effect**
   destructive
   **Steps**
   5 · loops
   **Needs**
   keeper macro id, macro, query and sample ticket id
   **Install**
   `zendesk_support-merge-duplicate-macros`
10. ### Offboard a departing agent from groups and sessions
    Use it when An agent has left the team and their Zendesk access and group memberships must be wound down.
    A person decides Offboard this agent: end all their sessions and remove every group membership. Assigned tickets are NOT reassigned by this plan.
    **Effect**
    destructive
    **Steps**
    7 · loops
    **Needs**
    user id
    **Install**
    `zendesk_support-offboard-agent`

install a plan

```
account { op: "plans.install", slug: "zendesk_support-triage-problem-tickets" }
# then ask for it by name; a schedule can run it on a timetable
```

Governance for Zendesk Support

## Destructive actions wait for a yes.

82 Zendesk Support actions are destructive. The first 10:

- Delete User `zendesk_support.users.delete`
- Bulk Delete Users `zendesk_support.users.destroy_many`
- Permanently Delete User `zendesk_support.users.permanently_delete`
- Delete Group `zendesk_support.groups.delete`
- Delete Ticket `zendesk_support.tickets.delete`
- Bulk Delete Tickets `zendesk_support.tickets.bulk_delete`
- Delete Ticket Permanently `zendesk_support.tickets.delete_permanently`
- Delete Multiple Tickets Permanently `zendesk_support.tickets.bulk_permanently_delete`
- Delete Organization `zendesk_support.organizations.delete`
- Bulk Delete Organizations `zendesk_support.organizations.delete_many`

A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

do zendesk_support.users.delete confirm_policy: **human**

Delete User?

**intent:** the user asked me to delete User

run suspended · waiting for a named person · key _zendesk-support-agent_ cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

```
account {
  op: "keys.create", name: "zendesk-support-agent",
  allowed_actions: ["zendesk_support.*"], cap_calls: 2000,
  confirm_policy: "human_for_writes",
  approval_rules: [
    { match: "zendesk_support.users.delete", approver: "lead@example.com" },
    { match: "zendesk_support.users.destroy_many", approver: "lead@example.com" },
    { match: "zendesk_support.users.permanently_delete", approver: "lead@example.com" }
  ]
}
```

Illustrative. Scoped to Zendesk Support only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

## What Zendesk Support costs on actionlake.

Every Zendesk Support action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Zendesk Support refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

- 1 upstream call per action all 559 Zendesk Support actions
- 179 actions page each page of a long list is one call
- 300 reads can be cached a cache hit costs nothing
- 100,000 calls a month, free paid plans from US$49 a month for 250,000

[See pricing](https://actionlake.com/pricing)

Action index

## Every Zendesk Support action.

559 actions by area: the id your agent calls, what it does, and its effect.

**Ticketing 477**

- `zendesk_support.macros.list_groups` List Macro Groups read
- `zendesk_support.requests.list` List Requests read
- `zendesk_support.ticket_comments.list` List Comments read
- `zendesk_support.tickets.list` List Tickets read
- `zendesk_support.account_settings.get` Show Settings read
- `zendesk_support.account_settings.get_email` Show Email Settings read
- and 471 more in this area

**People 32**

- `zendesk_support.users.autocomplete` Autocomplete Users read
- `zendesk_support.users.get_compliance_deletion_statuses` Show Compliance Deletion Statuses read
- `zendesk_support.users.get_many` Show Many Users read
- `zendesk_support.users.list` List Users read
- `zendesk_support.users.autocomplete_post` Autocomplete Users by Request Body read
- `zendesk_support.users.count` Count Users read
- and 26 more in this area

**Groups 26**

- `zendesk_support.groups.autocomplete` Autocomplete Groups read
- `zendesk_support.groups.list` List Groups read
- `zendesk_support.groups.list_assignable` List Assignable Groups read
- `zendesk_support.groups.list_available_agents` List Available Agents read
- `zendesk_support.group_memberships.bulk_create` Bulk Create Memberships write
- `zendesk_support.group_memberships.bulk_delete` Bulk Delete Memberships destructive
- and 20 more in this area

**Accounts 19**

- `zendesk_support.organizations.get_many` Show Many Organizations read
- `zendesk_support.organizations.list` List Organizations read
- `zendesk_support.organizations.list_merges` List Organization Merges read
- `zendesk_support.organizations.list_user` List User Organizations read
- `zendesk_support.organizations.autocomplete` Autocomplete Organizations read
- `zendesk_support.organizations.count` Count Organizations read
- and 13 more in this area

**Roles 5**

- `zendesk_support.custom_roles.create` Create Custom Role write
- `zendesk_support.custom_roles.get_by_id` Show Custom Role read
- `zendesk_support.custom_roles.list` List Custom Roles read
- `zendesk_support.custom_roles.update_by_id` Update Custom Role write
- `zendesk_support.custom_roles.delete_by_id` Delete Custom Role destructive

This index shows a sample of each area. All 559 actions, with their inputs and prices, are in the [catalogue](https://actionlake.com/console/catalogue), which a free sandbox key can search.

Questions

## The Zendesk Support MCP server, answered.

**Is there a Zendesk Support MCP server for Claude?**

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 559 Zendesk Support actions across ticketing, people, groups and accounts, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Zendesk Support.

**What do I need to connect Zendesk Support?**

Zendesk agent email and Zendesk API token. Plus your subdomain host. The free call account { op: "connections.requirements", service: "zendesk_support" } lists exactly what to paste.

**Can an AI agent delete or change things in Zendesk Support?**

Only if its key allows it, and only with an explicit confirmation. 82 Zendesk Support actions are destructive, including delete User, bulk Delete Users and permanently Delete User. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

**Will an AI agent use up my Zendesk Support API limit?**

actionlake paces every call to the limits in the Zendesk Support service file: 400 calls a minute per connection. Repeated reads are answered from cache (300 Zendesk Support actions can be), which never reaches Zendesk Support.

**What does a Zendesk Support action cost?**

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (179 Zendesk Support actions page). Cache hits, searches, dry runs and calls Zendesk Support refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

**Which Zendesk Support API does it cover?**

The Zendesk Support API 2 at your Zendesk Support instance's API base URL, which you enter when connecting (path /api/v2). It is built from Zendesk Support's documentation as read on 14 September 2026. 559 actions in 5 areas, each one in the signed service file (version 2.0.0).

**Can I combine Zendesk Support with my other systems?**

Yes. ask joins Zendesk Support to ConnectWise PSA or NetSuite on the same customer and returns the answer rather than every row. Zendesk Support maps crm.company, which 227 other connectors also map.

**Does actionlake keep my Zendesk Support data, and where?**

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to an hour, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Zendesk Support credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

**Which AI clients can use it?**

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

## More connectors like Zendesk Support

Shares the most action names with

- [Freshdesk 74](https://actionlake.com/connectors/freshdesk)
- [Freshservice 52](https://actionlake.com/connectors/freshservice)
- [PagerDuty 44](https://actionlake.com/connectors/pagerduty)
- [Trengo 33](https://actionlake.com/connectors/trengo)
- [Jira Service Management 30](https://actionlake.com/connectors/jira-service-management)
- [Gorgias 27](https://actionlake.com/connectors/gorgias)

Joins with, on shared entities

- [HaloPSA 5](https://actionlake.com/connectors/halopsa)
- [Odoo 4](https://actionlake.com/connectors/odoo)
- [Microsoft Dynamics 365 4](https://actionlake.com/connectors/microsoft-dynamics-365)
- [TOPdesk 4](https://actionlake.com/connectors/topdesk)
- [Insightly CRM 4](https://actionlake.com/connectors/insightly-crm)
- [Mitti 4](https://actionlake.com/connectors/mitti)

Browse

- [All Service desk & support connectors](https://actionlake.com/connectors/category/service-desk-and-support)
- [All connectors](https://actionlake.com/connectors)
- [How actionlake compares](https://actionlake.com/compare)

actionlake is independent. It is not made or endorsed by Zendesk Support; the name is the vendor's own. Counts are from the Zendesk Support service file, version 2.0.0.

## Give your agent Zendesk Support today.

[Connect Zendesk Support free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.

---

Source: https://actionlake.com/connectors/zendesk-support
More: https://actionlake.com/llms.txt