Skip to main content
Glama
asukaalves1873

Zendesk MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ZENDESK_EMAILNoEmail address for deprecated API token authentication; used together with ZENDESK_API_KEY. A deprecation warning is logged on first authentication.
ZENDESK_API_KEYNoAPI token for deprecated API token authentication; used together with ZENDESK_EMAIL. API tokens stop working permanently on 2027-04-30.
ZENDESK_CLIENT_IDNoThe OAuth client Identifier noted when registering the public OAuth client in Zendesk Admin Center
ZENDESK_SUBDOMAINNoThe Zendesk subdomain, e.g. 'acme' for https://acme.zendesk.com
ZENDESK_TOKEN_FILENoPath where OAuth tokens are stored. Defaults to ~/.config/zendesk-mcp/tokens.json; useful for storing tokens elsewhere, e.g. a Docker volume.$XDG_CONFIG_HOME/zendesk-mcp/tokens.json
ZENDESK_OAUTH_SCOPESNoSpace-separated OAuth scopes to request, e.g. 'tickets:read users:read hc:read'. Defaults to all scopes needed by the server's tools.
ZENDESK_OAUTH_REDIRECT_URINoOAuth redirect URI; must match a redirect URL registered on the OAuth client exactly. Change if port 4567 is in use or the client is registered with a different redirect URL.http://localhost:4567/callback

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription

No tools

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources