A simple Zendesk MCP server
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"orange-zendesk-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Zendesk MCP Server  [](https://opensource.org/licenses/Apache-2.0) A Model Context Protocol server for Zendesk. This server provides a comprehensive integration with Zendesk. It offers: - Tools for retrieving and managing Zendesk tickets and comments - Specialized prompts for ticket analysis and response drafting - Full access to the Zendesk Help Center articles as knowledge base  ## Setup - build: `uv venv && uv pip install -e .` or `uv build` in short. - setup zendesk credentials in `.env` file, refer to [.env.example](.env.example). - configure in Claude desktop: ```json { "mcpServers": { "zendesk": { "command": "uv", "args": [ "--directory", "/path/to/zendesk-mcp-server", "run", "zendesk" ] } } } ``` ## Resources - zendesk://knowledge-base, get access to the whole help center articles. ## Prompts ### analyze-ticket Analyze a Zendesk ticket and provide a detailed analysis of the ticket. ### draft-ticket-respons Draft a response to a Zendesk ticket. ## Tools ### get_ticket Retrieve a Zendesk ticket by its ID - Input: - `ticket_id` (integer): The ID of the ticket to retrieve ### get_ticket_comments Retrieve all comments for a Zendesk ticket by its ID - Input: - `ticket_id` (integer): The ID of the ticket to get comments for ### create_ticket_comment Create a new comment on an existing Zendesk ticket - Input: - `ticket_id` (integer): The ID of the ticket to comment on - `comment` (string): The comment text/content to add - `public` (boolean, optional): Whether the comment should be public (defaults to true)
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.