zendesk-mcp
Provides tools for searching, retrieving, creating, and updating Zendesk tickets, managing users, and adding comments.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@zendesk-mcpsearch for tickets with status 'open' and tag 'priority_high'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
zendesk-mcp
Dedalus MCP server for Zendesk support workflows: ticket search, ticket lookup, user listing, ticket creation, internal notes or public comments, and ticket status updates.
Tools
search_tickets- Search Zendesk tickets with Zendesk search syntax.get_ticket- Fetch one ticket by ID.list_users- List Zendesk users, optionally filtered by role.create_ticket- Create a new ticket with an initial comment.add_ticket_comment- Add an internal note or customer-visible public comment.update_ticket_status- Change a ticket status.
Related MCP server: Zendesk API MCP Server
Safety Notes
create_ticket, add_ticket_comment, and update_ticket_status are write tools. Zendesk triggers, automations, and notification settings may email customers or alter support queues. add_ticket_comment defaults to public_comment=false; set it to true only when a customer-visible reply is intended.
Do not put Zendesk OAuth access tokens, client secrets, or requester personal data in commits, logs, issue trackers, screenshots, or public demos.
Authentication
This is a Dedalus Type 4 OAuth server. The server declares a DAuth connection named zendesk-mcp with secret key ZENDESK_ACCESS_TOKEN. Dedalus performs the OAuth flow and injects a bearer token at request time; the server code does not handle refresh tokens.
Required deployment variables:
OAUTH_ENABLED=true
OAUTH_AUTHORIZE_URL=https://<subdomain>.zendesk.com/oauth/authorizations/new
OAUTH_TOKEN_URL=https://<subdomain>.zendesk.com/oauth/tokens
OAUTH_CLIENT_ID=...
OAUTH_CLIENT_SECRET=...
OAUTH_SCOPES_AVAILABLE=read,write
OAUTH_BASE_URL=https://<subdomain>.zendesk.com
ZENDESK_BASE_URL=https://<subdomain>.zendesk.com
DEDALUS_AS_URL=https://as.dedaluslabs.aiFor local DirectDispatch development, set ZENDESK_ACCESS_TOKEN to a short-lived OAuth token and set ZENDESK_BASE_URL to your Zendesk subdomain URL.
Run Locally
uv run python src/main.pyIn another terminal:
MCP_SERVER_URL=http://127.0.0.1:8080/mcp uv run python src/_client.pysrc/_client.py calls every tool. Write-tool calls use smoke-test values from environment variables such as ZENDESK_TEST_TICKET_ID, ZENDESK_TEST_REQUESTER_EMAIL, and ZENDESK_TEST_STATUS.
Deploy
Publish this repository as dedalus-labs/zendesk-mcp, configure the OAuth variables above in Dedalus, deploy, then run:
DEDALUS_MCP_SERVER_ONLY=1 DEDALUS_MCP_SERVER=dedalus-labs/zendesk-mcp uv run python src/_client.pyComplete the OAuth browser flow when prompted.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/chenzhaoxuan0/zendesk-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server