Zendesk MCP Server
by Enrico90498
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZENDESK_EMAIL | No | Deprecated API token authentication: the email address of the Zendesk user paired with the API token. | |
| ZENDESK_API_KEY | No | Deprecated API token authentication: the account-level Zendesk API token. Zendesk is retiring API tokens; prefer OAuth. | |
| ZENDESK_CLIENT_ID | No | The Identifier of the public OAuth client registered in Zendesk Admin Center. When set, OAuth authentication takes precedence over API token authentication. | |
| ZENDESK_SUBDOMAIN | No | Your Zendesk subdomain, e.g. `acme` for https://acme.zendesk.com | |
| ZENDESK_TOKEN_FILE | No | Location where OAuth tokens are stored, for example a Docker volume. Defaults to ~/.config/zendesk-mcp/tokens.json. | $XDG_CONFIG_HOME/zendesk-mcp/tokens.json |
| ZENDESK_OAUTH_SCOPES | No | Space-separated OAuth scopes to request, to narrow access if you do not need every tool (for read-only access: `tickets:read users:read hc:read`). | |
| ZENDESK_OAUTH_REDIRECT_URI | No | OAuth redirect URI. Must match a redirect URL registered on the OAuth client exactly. Change if port 4567 is in use. | 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
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityActive
ResponsivenessResponsive