Skip to content

Zendesk

Artific Connect · Zendesk gives a key five tools over Zendesk Support: search or list tickets, read one ticket, create a ticket, add a comment, and list users. Zendesk has announced an MCP server but not shipped it, so this bundle reaches the same REST API directly. It installs from the Marketplace like any other bundle.

What you get

One toolset, zendesk, holding the five connectors, plus a skill that tells the model Zendesk's search syntax and what to confirm before creating a ticket or a comment.

What you supply at install

Zendesk's API lives at https://<your-subdomain>.zendesk.com, one host under all five connectors, so this bundle asks for it once:

  • zendesk_subdomain_url — paste https://<your-subdomain>.zendesk.com with your own subdomain filled in. Every connector below adds its own path to this one address (search's /api/v2/search.json, a ticket's /api/v2/tickets/{id}.json, and so on) — you never see or edit those paths yourself.

And zendesk_credential, a Basic credential built from your agent email and your API token, with the literal /token suffix on the username that tells Zendesk it is a token and not a password:

{ "type": "basic", "username": "<your agent email>/token", "password": "<your API token>" }

Until both are supplied the subscription waits at needs configuration.

Before it works

Your administrator has to allow your Zendesk host in the key's own egress policy.

Good to know

  • Verified 2026-09-24 on developer.zendesk.com: the Basic auth form (base64(email/token:api_token)) and that Zendesk is retiring plain API tokens — accounts created from 28 July 2026 cannot create or use one at all, and existing tokens unused for 30 days deactivate. An organisation on the newer side of that date needs an OAuth access token instead of an API token; this bundle does not yet offer that form.
  • Zendesk's remote MCP server is announced, not shipped; this guide will move to it once it is, without changing which tools a key already has attached.
  • The mark: this bundle's card still uses Artific's own placeholder. Zendesk's trademark guidelines refuse the marks to anyone without a written licence or agreement, which this deployment does not have (checked 2026-09-24).