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.

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.ai

For 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.py

In another terminal:

MCP_SERVER_URL=http://127.0.0.1:8080/mcp uv run python src/_client.py

src/_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.py

Complete the OAuth browser flow when prompted.