Aerostack
Aerostack
electrical_services

Zendesk MCP Server — Hosted Customer Support, Any AI Agent

MCP Server language Hosted language Public

Manage support tickets, users, and knowledge base articles in Zendesk — AI-powered customer service automation.

aerostack @aerostack verified
• v0.1.0 • MIT • Updated Jun 28, 2026
add_circleAdd to Workspace
robot_2

Use with AI AssistantsMCP

Connect Claude, Cursor, or any MCP-compatible client — then call tools directly

① Add This MCP Server

Paste into your AI client config — then all its tools are available instantly.

.claude/mcp.json
{
  "mcpServers": {
    "zendesk": {
      "url": "https://mcp.aerostack.dev/s/aerostack/mcp-zendesk",
      "headers": {
        "Authorization": "Bearer YOUR_AEROSTACK_TOKEN"
      }
    }
  }
}

Replace YOUR_AEROSTACK_TOKEN with your API token from the dashboard.

② Call a Tool

Ask your AI assistant to call a specific tool, or send raw JSON-RPC:

+23 more

Natural Language Prompt

“Use the _ping tool to verify zendesk credentials by calling a lightweight read endpoint. used internally by aerostack to validate credentials”

Using a Workspace?

Add this MCP to your Workspace — your team shares one token, secrets are stored securely, and every AI agent in the workspace can call it without per-user setup.

add_circleAdd to Workspace

description Overview

mcp-zendesk — Zendesk MCP Server

Manage tickets, users, organizations, knowledge base, views, and CSAT analytics from your AI agents.

Zendesk is the enterprise support platform used by thousands of customer service teams to handle tickets, knowledge bases, and customer relationships. This MCP server exposes 26 tools across 6 functional groups — tickets, users, organizations, knowledge base, views and macros, and CSAT analytics — letting your AI agents handle everything from ticket creation and routing to CSAT trend analysis, all without logging into Zendesk.

Live endpoint: https://mcp.aerostack.dev/s/aerostack/mcp-zendesk

What You Can Do

  • Create support tickets with full context (subject, body, priority, tags, channel, and an internal AI summary note) as part of bot escalation workflows
  • Search and update existing tickets to handle status changes, reassignments, and customer replies from AI-driven support agents
  • Search and manage users and organizations to build full customer profiles before responding
  • Query CSAT scores and SLA metrics to generate daily support health reports without any Zendesk report configuration

Available Tools

Tool Description
list_tickets List recent tickets with optional status, priority, or assignee filters
search_tickets Full Zendesk search syntax — status:open, priority:urgent, tag:billing, free text
get_ticket Get full ticket details: subject, description, status, priority, tags, channel
create_ticket Create ticket with subject, body, requester, priority, tags, channel, and internal_note
update_ticket Update status, priority, assignee, or tags (use add_tags to append without overwriting)
delete_ticket Soft-delete a ticket (recoverable within 30 days)
list_ticket_comments Get all comments — public replies and internal notes
add_comment Add a public reply or internal note to a ticket (defaults to internal)
merge_tickets Merge a duplicate ticket into another
search_users Find users by email, name, phone, or free text
get_user Get full user profile: name, email, phone, org, role, tags, notes, timezone
get_user_tickets Get all tickets submitted by a specific user
create_user Create a new end-user, agent, or admin
update_user Update user name, email, phone, org, tags, or notes
get_user_identities Get all verified identities for a user (emails, phones, social)
search_organizations Find organizations by name, domain, or external ID
get_organization Get full org details: name, domains, tags, notes, group
create_organization Create a new organization with domains and tags
update_organization Update organization fields
search_articles Full-text search across published Help Center articles
list_articles List all articles sorted by last updated, optionally filtered by labels
get_article Get full article content (HTML stripped to plain text)
create_article Create a new Help Center article in a section
list_views List all active views (saved ticket queues)
get_view_tickets Get tickets in a specific view
list_macros List active macros with their actions
get_satisfaction_ratings Get CSAT scores, filterable by good/bad and date range
get_ticket_metrics Get SLA metrics — reply time, resolution time, reopens (calendar and business hours)

Configuration

Variable Required Description How to Get
ZENDESK_SUBDOMAIN Yes Your Zendesk subdomain (e.g. acme from acme.zendesk.com) Found in your Zendesk URL
ZENDESK_EMAIL Yes Admin email address for API authentication The email address you use to log into Zendesk admin
ZENDESK_API_TOKEN Yes API token for authentication your-subdomain.zendesk.com/admin → Apps and Integrations → APIs → Zendesk API → enable Token Access → Add API Token → copy the token (shown once)

Quick Start

Add to Aerostack Workspace
  1. Go to aerostack.dev → Your Project → MCPs
  2. Search for "Zendesk" and click Add to Workspace
  3. Add all three secrets under Project → Secrets

Once added, every AI agent in your workspace can call Zendesk tools automatically — no per-user setup needed.

Example Prompts
"Search for all open urgent tickets tagged billing and summarize the top 5 issues"
"Create a support ticket for sarah@acme.com with subject Refund request and flag it as high priority with an internal note explaining the situation"
"Get our CSAT scores for the last 30 days and calculate the good-to-bad ratio"
Direct API Call
curl -X POST https://mcp.aerostack.dev/s/aerostack/mcp-zendesk \
  -H 'Content-Type: application/json' \
  -H 'X-Mcp-Secret-ZENDESK-SUBDOMAIN: your-subdomain' \
  -H 'X-Mcp-Secret-ZENDESK-EMAIL: admin@yourcompany.com' \
  -H 'X-Mcp-Secret-ZENDESK-API-TOKEN: your-api-token' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_tickets","arguments":{"query":"status:open priority:urgent"}}}'

License

MIT

terminal Tools (29)

Available tools on this MCP server. Each tool can be called directly from any AI agent.

terminal
_ping #1

Verify Zendesk credentials by calling a lightweight read endpoint. Used internally by Aerostack to validate credentials.

terminal
list_tickets #2

List recent tickets with optional filters for status, priority, and assignee. Returns last 100 by default sorted by updated_at. For status filtering uses Zendesk search endpoint for accuracy.

terminal
search_tickets #3

Search tickets using Zendesk search syntax. Supports complex queries including status, priority, requester, tags, date ranges, and free text.

terminal
get_ticket #4

Get full details of a specific ticket by ID — subject, description, status, priority, tags, assignee, requester, channel, timestamps.

terminal
create_ticket #5

Create a new support ticket. Core tool for AI bot escalation — use internal_note to pass AI conversation summary to agents. The channel param (e.g. "whatsapp") is automatically added as a tag.

terminal
update_ticket #6

Update a ticket — change status, priority, assignee, tags. Optionally add a comment in the same API call. Use add_tags to append tags without removing existing ones.

terminal
delete_ticket #7

Soft-delete a ticket (moves to trash). Recoverable within 30 days from Admin Center → Trash.

terminal
list_ticket_comments #8

List all comments on a ticket — both public replies (visible to customer) and internal notes (agents only). Each comment shows author, body, public flag, and timestamp.

terminal
add_comment #9

⚠️ Add a comment to a ticket. DEFAULTS TO INTERNAL NOTE (public: false). Set public: true explicitly only when you want the customer to see it. Internal notes are only visible to agents.

terminal
merge_tickets #10

Merge one ticket into another. The source ticket is closed and its history is linked to the target ticket. Useful for deduplication.

terminal
search_users #11

Search for users by email, name, phone, or free text. Returns role (end-user/agent/admin), organization, tags, and account status.

terminal
get_user #12

Get full profile of a Zendesk user — name, email, phone, organization, role, tags, notes, time zone, created date.

terminal
get_user_tickets #13

Get all tickets submitted by a specific user. Useful for "what is their support history?" context.

terminal
create_user #14

Create a new Zendesk user (end-user by default). Use for new customers contacting via bot channels.

terminal
update_user #15

Update a Zendesk user profile — name, email, phone, organization, tags, or notes. Only provided fields are updated.

terminal
get_user_identities #16

Get all verified identities for a user — email addresses, phone numbers, social logins. Shows which is primary and which are verified.

terminal
search_organizations #17

Search organizations by name, domain name, or external ID. Returns organization list with domains and tags.

terminal
get_organization #18

Get full details of a Zendesk organization — name, domain names, tags, notes, group assignment.

terminal
create_organization #19

Create a new Zendesk organization (company/account). Associates users and tickets under a company umbrella.

terminal
update_organization #20

Update a Zendesk organization — name, domains, tags, notes, or default group. Only provided fields are updated.

terminal
search_articles #21

Full-text search across all published Help Center articles. Returns title, snippet, URL, and vote score. Use this FIRST before creating a ticket — most customer questions have KB answers.

terminal
list_articles #22

List all published Help Center articles, sorted by most recently updated. Optionally filter by locale or labels.

terminal
get_article #23

Get the full content of a Help Center article. HTML tags are stripped for readable plain text output.

terminal
create_article #24

Create a new Help Center article in a specific section. Useful for converting resolved tickets into KB articles.

terminal
list_views #25

List all active ticket views (saved filters). Views represent pre-configured ticket queues like "All Open Tickets", "Urgent Tickets", "Unassigned". Use get_view_tickets to see tickets in a view.

terminal
get_view_tickets #26

Get tickets in a specific view. Views are saved filters — use list_views to find view IDs first.

terminal
list_macros #27

List available macros (automated actions/templates). Macros can change ticket status, add tags, send canned responses, and more.

terminal
get_satisfaction_ratings #28

Get CSAT (customer satisfaction) ratings. Returns score (good/bad), comment, linked ticket and agent. Filter by score or time range for analysis.

terminal
get_ticket_metrics #29

Get SLA and performance metrics for a specific ticket — reply times, resolution times, reopen count, reply count. Both calendar and business hours reported.

Details

upgrade Version 0.1.0
gavel License MIT
wifi Transport streamable-http
lock Access Public
category Category Customer Support
terminal Tools 29

language Live Endpoint

https://mcp.aerostack.dev/s/aerostack/mcp-zendesk

Sub-50ms globally · Zero cold start

Publisher

aerostack
@aerostack verified

Pre-built functions for the most common MCP tool patterns. Clone, extend, and deploy.

Tags

support zendesk helpdesk tickets knowledge-base
Browse more servers

More in Customer Support

Browse Customer Support MCPs →
hub

Freshdesk

by @aerostack

Create tickets, manage contacts, and resolve support issues faster — give your AI agents full Freshdesk access.

customer-support
star 0
hub

Salesforce

by @aerostack

Query leads, contacts, opportunities, and accounts in Salesforce — full SOQL support for enterprise CRM automation.

customer-support
star 0
hub

Zoho Crm

by @aerostack

Manage leads, contacts, deals, accounts, and tasks in Zoho CRM with full CRUD operations and lead conversion.

customer-support
star 0

Frequently asked questions

What is the Zendesk MCP server and what can it do? +

The Zendesk MCP server is hosted on Aerostack and exposes these tools to your AI agent: `_ping`, `list_tickets`, `search_tickets`, `get_ticket`, `create_ticket`. You get one hosted URL — no self-hosting — that works from Claude, Cursor, ChatGPT, Gemini, VS Code, or any MCP-compatible client, and you can share it with your team or combine it with other MCP servers in a workspace.

Is the Zendesk MCP server hosted, or do I have to run it myself? +

It's hosted on Aerostack's edge infrastructure — you don't deploy or maintain anything. Add it to a workspace and you get one authenticated URL, with secrets encrypted, that any AI agent or editor can connect to. Use it solo or share the same URL across your whole team.

Which AI agents and editors can use the Zendesk MCP server? +

Any MCP client: Claude and Claude Code, Cursor, ChatGPT, Gemini, Windsurf, Cline, VS Code, and custom agents. Because it's one hosted URL, the same Zendesk MCP server works everywhere — and you can compose it with other MCP servers, skills, and functions behind a single workspace URL.

How do I install the Zendesk MCP server in Claude Desktop? +

Add the following to your Claude Desktop config (`claude_desktop_config.json`): ```json { "mcpServers": { "@aerostack/mcp-zendesk": { "command": "npx", "args": ["-y", "@aerostack/@aerostack/mcp-zendesk"] } } } ``` Then restart Claude Desktop and the tools will appear automatically.

How do I use the Zendesk MCP server in Cursor? +

In Cursor, open **Settings → MCP** and add: ```json { "name": "@aerostack/mcp-zendesk", "command": "npx", "args": ["-y", "@aerostack/@aerostack/mcp-zendesk"] } ``` Save and reload Cursor. The MCP tools will be available in Agent mode.

Does Zendesk MCP require authentication? +

Yes. Zendesk requires authentication. Check the MCP's documentation for the required credentials.