Zendesk MCP Server
by filippoo386
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZENDESK_EMAIL | No | Email address of the Zendesk user, used with ZENDESK_API_KEY for the deprecated API token authentication. | |
| ZENDESK_API_KEY | No | Deprecated Zendesk account-level API token, used together with ZENDESK_EMAIL. | |
| 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 the OAuth tokens are stored, for example a Docker volume. | $XDG_CONFIG_HOME/zendesk-mcp/tokens.json |
| ZENDESK_OAUTH_SCOPES | No | Space-separated OAuth scopes to request. Narrow them if you do not need every tool, for example 'tickets:read users:read hc:read' for read-only access. | tickets:read tickets:write ticket_attachments:read users:read hc:read |
| ZENDESK_OAUTH_REDIRECT_URI | No | OAuth redirect URI. Change it when port 4567 is in use or when the OAuth client is registered with a different redirect URL; it must match a redirect URL on the client exactly. | 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