Zendesk MCP Server Kon

🚀 Zendesk MCP Server KON

This is a forked project based on reminia/zendesk-mcp-server, with added support and improvements for additional features.

](https://opensource.org/licenses/Apache-2.0)

A model context protocol server for Zendesk. This server provides comprehensive integration with Zendesk, including:

• Tools for retrieving and managing tickets and comments.
• Tools for managing community posts, comments, and topics.
• Professional tips for ticket analysis and draft responses.
• Full access to the knowledge base of Zendesk Help Center articles.

🚀 Quick Start

📦 Installation

1. Install the package:

uv venv && uv pip install -e .

2. Configure in Claude Desktop:

{
  "mcpServers": {
    "zendesk": {
      "command": "uv",
      "args": [
        "--directory",
        "/path/to/zendesk-mcp-server-kon",
        "run",
        "zendesk"
      ],
      "env": {
        "ZENDESK_SUBDOMAIN": "your-zendesk-subdomain",
        "ZENDESK_EMAIL": "your-zendesk-email",
        "ZENDESK_API_KEY": "your-zendesk-api-key"
      }
    }
  }
}

Replace the environment variables with your Zendesk credentials:

• ZENDESK_SUBDOMAIN: Your Zendesk subdomain (e.g., if your Zendesk URL is company.zendesk.com, use company).
• ZENDESK_EMAIL: Your Zendesk administrator email address.
• ZENDESK_API_KEY: Your Zendesk API token.

💻 Usage Examples

Resources

• zendesk://knowledge-base, access the entire help center articles.

Tips

• analyze-ticket: Analyze a Zendesk ticket and provide detailed ticket analysis.
• draft-ticket-response: Draft a response for a Zendesk ticket.

Tools

Ticket Management

• get_ticket: Retrieve a Zendesk ticket by its ID.
  • Input:
    • ticket_id (integer): The ID of the ticket to retrieve.
• get_ticket_comments: Get all comments of 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.
    • public (boolean, optional): Whether the comment is public (default is true).

Community Management

• get_community_posts: Retrieve community posts by filtering and sorting.
  • Input:
    • filter_by (string, optional): Filter posts by status (planned, not_planned, completed, answered, none).
    • sort_by (string, optional): Sort posts by a sorting method.
• get_community_post: Retrieve a community article by its ID.
  • Input:
    • id (integer): The ID of the article to retrieve.
• create_community_post: Create a new community article.
  • Input:
    • title (string): The title of the article.
    • content (string): The content of the article.
    • author_id (integer): The user ID of the author.
    • metadata (JSON object, optional): The metadata of the article.
• update_community_post: Update a community article.
  • Input:
    • id (integer): The ID of the article to update.
    • title (string): The new title.
    • content (string): The new content.
    • metadata (JSON object, optional): The new metadata.
• delete_community_post: Delete a community article.
  • Input:
    • id (integer): The ID of the article to delete.

Comment Management

• create_comment: Create a comment.
  • Input:
    • parent_id (integer): The ID of the parent element (article or comment).
    • content (string): The comment content.
    • author_id (integer): The user ID of the author.
    • metadata (JSON object, optional): The metadata of the comment.
• update_comment: Update a comment.
  • Input:
    • id (integer): The ID of the comment to update.
    • content (string): The new content.
    • metadata (JSON object, optional): The new metadata.
• delete_comment: Delete a comment.
  • Input:
    • id (integer): The ID of the comment to delete.