Skip to main content
hc
Submit
mcpSource-backedReview first Safety ✓ Privacy ✓

Zendesk MCP Server for Claude

Retrieve and manage Zendesk tickets, analyze support conversations, draft ticket responses, and search the Zendesk Help Center knowledge base — with the open-source Zendesk MCP server supporting ticket CRUD, threaded comments, and built-in analysis prompts.

by reminia·added 2026-06-18·
Claude CodeCodexCursorClaude Desktop
HarnessClaude CodeCodexCursorClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Safety notes

  • `create_ticket` and `update_ticket` write to your live Zendesk instance — changes affect real customer tickets and are visible to your support team.
  • `create_ticket_comment` posts public or internal notes on tickets — set the `public` parameter to `false` for internal notes only.

Privacy notes

  • Ticket content including customer messages, email addresses, and conversation history are surfaced in Claude's context.
  • The Zendesk Help Center knowledge base (zendesk://knowledge-base) exposes all published articles in your instance.
  • Treat your Zendesk API token as a secret — do not commit it to version control.

Prerequisites

  • A Zendesk account with Admin or Agent access.
  • Your Zendesk subdomain (the part before `.zendesk.com`), email address, and API token (Settings → API → Zendesk API → Add API Token).
  • Python with `uv` installed: `pip install uv` or `brew install uv`.
  • An MCP client such as Claude Code or Claude Desktop.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
10 minutes
Difficulty
beginner
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "zendesk": {
      "command": "uvx",
      "args": ["zendesk-mcp-server"],
      "env": {
        "ZENDESK_SUBDOMAIN": "your-subdomain",
        "ZENDESK_EMAIL": "you@example.com",
        "ZENDESK_API_KEY": "your-api-key"
      }
    }
  }
}

About this resource

Overview

The Zendesk MCP Server connects Claude to your Zendesk support instance for ticket management, comment threading, and knowledge base access. It includes two specialized prompts — analyze-ticket and draft-ticket-response — that leverage Claude's reasoning to help support agents understand complex tickets and write effective responses faster. Licensed under Apache-2.0 with 104 stars on GitHub.

Key capabilities

  • Ticket management — fetch the latest tickets with pagination, retrieve individual tickets by ID, create new tickets, and update ticket fields (status, priority, assignee).
  • Comment threading — read all comments on a ticket and post new public or internal notes.
  • Knowledge base — access the entire Zendesk Help Center via the zendesk://knowledge-base resource for grounded responses based on your documentation.
  • Analysis prompts — built-in analyze-ticket and draft-ticket-response prompts for structured ticket analysis and AI-assisted response drafting.

Tools

Tool Purpose
get_tickets Fetch latest tickets with pagination (max 100 per page)
get_ticket Retrieve a specific ticket by ID
get_ticket_comments Get all comments for a ticket
create_ticket_comment Add a public or internal note to a ticket
create_ticket Create a new support ticket
update_ticket Update ticket status, priority, or assignee

How it compares

Server Ticket CRUD Comments Knowledge base Built-in prompts Auth
Zendesk MCP Yes Yes Yes Yes API token
Intercom MCP Yes Yes Limited No API key
Freshdesk MCP Yes Limited No No API key
HubSpot MCP Partial Yes No No OAuth

The built-in analysis and response-drafting prompts are purpose-built for support workflows — unique among help desk MCP servers.

Installation

Claude Code

claude mcp add zendesk \
  -e ZENDESK_SUBDOMAIN=your-subdomain \
  -e ZENDESK_EMAIL=you@example.com \
  -e ZENDESK_API_KEY=your-api-key \
  -- uvx zendesk-mcp-server

Claude Desktop

{
  "mcpServers": {
    "zendesk": {
      "command": "uvx",
      "args": ["zendesk-mcp-server"],
      "env": {
        "ZENDESK_SUBDOMAIN": "your-subdomain",
        "ZENDESK_EMAIL": "you@example.com",
        "ZENDESK_API_KEY": "your-api-key"
      }
    }
  }
}

Get your API token in Zendesk: Admin Center → Apps and integrations → APIs → Zendesk API → Add API token.

Docker

docker run --rm -i --env-file /path/to/.env zendesk-mcp-server

Requirements

  • A Zendesk account with API access and an API token.
  • Python with uv installed.
  • An MCP client (Claude Code or Claude Desktop).

Security

  • Uses API token + email authentication — no OAuth or stored sessions.
  • Keep your API token out of version control; use environment variables or a secrets manager.

Source Verification Notes

Verified on 2026-06-18:

  • GitHub repository reminia/zendesk-mcp-server (Apache-2.0, 104 stars) documents the zendesk-mcp-server PyPI package (v0.1.1), the ZENDESK_SUBDOMAIN/ZENDESK_EMAIL/ ZENDESK_API_KEY environment variables, all six tools (get_tickets, get_ticket, get_ticket_comments, create_ticket_comment, create_ticket, update_ticket), the zendesk://knowledge-base resource, the analyze-ticket and draft-ticket-response prompts, and the Docker build option.
  • Claude Code MCP documentation at code.claude.com/docs/en/mcp describes the stdio connector pattern used above.
#zendesk#customer-support#help-desk#tickets#knowledge-base

Source citations

Add this badge to your README

Show that Zendesk MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/zendesk-mcp-server.svg)](https://heyclau.de/entry/mcp/zendesk-mcp-server)

How it compares

Zendesk MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

FieldZendesk MCP Server for Claude

Retrieve and manage Zendesk tickets, analyze support conversations, draft ticket responses, and search the Zendesk Help Center knowledge base — with the open-source Zendesk MCP server supporting ticket CRUD, threaded comments, and built-in analysis prompts.

Open dossier 		Intercom MCP Server for Claude

Access customer conversations, tickets, and user data in real-time

Open dossier 		GrowthBook MCP Server for Claude

Manage A/B experiments and feature flags in GrowthBook from Claude — list and create experiments, manage feature flags, check experiment results, and interact with your GrowthBook workspace — with the official GrowthBook MCP server.

Open dossier 		Unleash MCP Server for Claude

Create and manage Unleash feature flags from Claude — evaluate whether a change needs a flag, detect existing flags to prevent duplicates, set rollout strategies, toggle environments, and get cleanup guidance — with the official Unleash MCP server following Unleash best practices.

Open dossier
Trust
Install riskReview firstLow riskReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Categorymcpmcpmcpmcp
Sourcesource-backedfirst-partysource-backedsource-backed
AuthorreminiaIntercomGrowthBookUnleash
Added2026-06-182025-09-182026-06-182026-06-18
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓`create_ticket` and `update_ticket` write to your live Zendesk instance — changes affect real customer tickets and are visible to your support team. `create_ticket_comment` posts public or internal notes on tickets — set the `public` parameter to `false` for internal notes only.✓Restrict Intercom workspace access and review outbound message or ticket changes before using it on live customer support data.✓`create_experiment` and `create_feature` write to your GrowthBook workspace — capabilities are scoped by your API key/PAT permissions. Creating experiments or feature flags may immediately affect production if they are in a live environment — review before confirming.✓`toggle_flag_environment` enables or disables a feature flag in a production environment — confirm before toggling live flags. `create_flag` writes to your Unleash instance; capabilities are scoped by your PAT's permissions. Remote MCP (`--transport http`) is experimental and must be enabled on your Unleash instance.
Privacy notes✓Ticket content including customer messages, email addresses, and conversation history are surfaced in Claude's context. The Zendesk Help Center knowledge base (zendesk://knowledge-base) exposes all published articles in your instance. Treat your Zendesk API token as a secret — do not commit it to version control.✓Customer conversations, emails, user profiles, tickets, company records, and support metadata may be sent through model context.✓Experiment configurations, feature flag definitions, targeting rules, and experiment results from your GrowthBook workspace are surfaced in Claude's context. Your `GB_API_KEY` is a secret — store it as an environment variable, not in version-controlled config files.✓Feature flag names, descriptions, targeting rules, rollout configurations, and project metadata from your Unleash instance are surfaced in Claude's context. Your `UNLEASH_PAT` is a secret — store it as an environment variable and do not commit it to version control.
Prerequisites
  • A Zendesk account with Admin or Agent access.
  • Your Zendesk subdomain (the part before `.zendesk.com`), email address, and API token (Settings → API → Zendesk API → Add API Token).
  • Python with `uv` installed: `pip install uv` or `brew install uv`.
  • An MCP client such as Claude Code or Claude Desktop.
  • Intercom workspace account (sign up at https://www.intercom.com if needed)
  • Intercom Access Token (for private apps) or OAuth credentials (for public apps) - get from Intercom Developer Hub
  • HTTP/SSE transport support (remote MCP server at https://mcp.intercom.com/sse)
  • Internet connection (remote Intercom API access required)
  • A GrowthBook account (cloud at growthbook.io or self-hosted).
  • A GrowthBook API key (from API Keys settings or a Personal Access Token with appropriate permissions).
  • Your GrowthBook account email (used when creating experiments and feature flags).
  • Node.js with `npx` available.
  • An Unleash instance (hosted at unleash.cloud or self-hosted).
  • A personal access token with permission to create feature flags (Settings → API Access → Personal access tokens).
  • Node.js 22+ with `npx` available.
  • An MCP client such as Claude Code or Claude Desktop.
Install
claude mcp add zendesk -e ZENDESK_SUBDOMAIN=your-subdomain -e ZENDESK_EMAIL=you@example.com -e ZENDESK_API_KEY=your-api-key -- uvx zendesk-mcp-server
claude mcp list && claude mcp status intercom
claude mcp add growthbook -e GB_API_KEY=your-api-key -e GB_EMAIL=you@example.com -- npx @growthbook/growthbook-mcp
claude mcp add unleash -e UNLEASH_BASE_URL=https://your-instance.unleash.cloud -e UNLEASH_PAT=your-pat -- npx -y @unleash/mcp@latest --log-level error
Config
{
  "mcpServers": {
    "zendesk": {
      "command": "uvx",
      "args": ["zendesk-mcp-server"],
      "env": {
        "ZENDESK_SUBDOMAIN": "your-subdomain",
        "ZENDESK_EMAIL": "you@example.com",
        "ZENDESK_API_KEY": "your-api-key"
      }
    }
  }
}
{
  "mcpServers": {
    "intercom": {
      "url": "https://mcp.intercom.com/sse",
      "type": "sse"
    }
  }
}
{
  "mcpServers": {
    "growthbook": {
      "command": "npx",
      "args": ["@growthbook/growthbook-mcp"],
      "env": {
        "GB_API_KEY": "your-api-key",
        "GB_EMAIL": "you@example.com",
        "GB_API_URL": "https://api.growthbook.io",
        "GB_APP_ORIGIN": "https://app.growthbook.io"
      }
    }
  }
}
{
  "mcpServers": {
    "unleash": {
      "command": "npx",
      "args": ["-y", "@unleash/mcp@latest", "--log-level", "error"],
      "env": {
        "UNLEASH_BASE_URL": "https://your-instance.unleash.cloud",
        "UNLEASH_PAT": "your-personal-access-token"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.