Zendesk MCP Server
by Jurgenr347
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZENDESK_EMAIL | No | Email paired with an API token (deprecated API token authentication). | |
| ZENDESK_API_KEY | No | Zendesk API token (deprecated; being retired). Used together with ZENDESK_EMAIL when ZENDESK_CLIENT_ID is not set. | |
| ZENDESK_CLIENT_ID | No | The OAuth client's Identifier, used for per-operator OAuth 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. Override to store tokens elsewhere, e.g. a Docker volume. | $XDG_CONFIG_HOME/zendesk-mcp/tokens.json |
| ZENDESK_OAUTH_SCOPES | No | Narrow the OAuth scopes requested, e.g. 'tickets:read users:read hc:read' for read-only access. | |
| 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 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
| 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
ResponsivenessNo issues