Skip to main content
Glama
Zendesk API MCP Server

Zendesk API MCP Server

Zendesk API MCP Server

A comprehensive Model Context Protocol (MCP) server for interacting with the Zendesk API. This server provides tools and resources for managing Zendesk Support, Talk, Chat, and Guide products.

## Features

- Complete coverage of Zendesk API functionality
- Tools for managing tickets, users, organizations, and more
- Resources for accessing Zendesk API documentation
- Secure authentication with Zendesk API tokens

## Getting Started

### Prerequisites

- Node.js 14 or higher
- A Zendesk account with API access

### Installation

1. Clone this repository
2. Install dependencies:
   ```
   npm install
   ```
3. Create a `.env` file with your Zendesk credentials:
   ```
   ZENDESK_SUBDOMAIN=your-subdomain
   ZENDESK_EMAIL=your-email@example.com
   ZENDESK_API_TOKEN=your-api-token
   ```

### Running the Server

Start the server:
```
npm start
```

For development with auto-restart:
```
npm run dev
```

### Testing with MCP Inspector

Test the server using the MCP Inspector:
```
npm run inspect
```

## Available Tools

### Tickets
- `list_tickets`: List tickets in Zendesk
- `get_ticket`: Get a specific ticket by ID
- `create_ticket`: Create a new ticket
- `update_ticket`: Update an existing ticket
- `delete_ticket`: Delete a ticket

### Users
- `list_users`: List users in Zendesk
- `get_user`: Get a specific user by ID
- `create_user`: Create a new user
- `update_user`: Update an existing user
- `delete_user`: Delete a user

### Organizations
- `list_organizations`: List organizations in Zendesk
- `get_organization`: Get a specific organization by ID
- `create_organization`: Create a new organization
- `update_organization`: Update an existing organization
- `delete_organization`: Delete an organization

### Groups
- `list_groups`: List agent groups in Zendesk
- `get_group`: Get a specific group by ID
- `create_group`: Create a new agent group
- `update_group`: Update an existing group
- `delete_group`: Delete a group

### Macros
- `list_macros`: List macros in Zendesk
- `get_macro`: Get a specific macro by ID
- `create_macro`: Create a new macro
- `update_macro`: Update an existing macro
- `delete_macro`: Delete a macro

### Views
- `list_views`: List views in Zendesk
- `get_view`: Get a specific view by ID
- `create_view`: Create a new view
- `update_view`: Update an existing view
- `delete_view`: Delete a view

### Triggers
- `list_triggers`: List triggers in Zendesk
- `get_trigger`: Get a specific trigger by ID
- `create_trigger`: Create a new trigger
- `update_trigger`: Update an existing trigger
- `delete_trigger`: Delete a trigger

### Automations
- `list_automations`: List automations in Zendesk
- `get_automation`: Get a specific automation by ID
- `create_automation`: Create a new automation
- `update_automation`: Update an existing automation
- `delete_automation`: Delete an automation

### Search
- `search`: Search across Zendesk data

### Help Center
- `list_articles`: List Help Center articles
- `get_article`: Get a specific Help Center article by ID
- `create_article`: Create a new Help Center article
- `update_article`: Update an existing Help Center article
- `delete_article`: Delete a Help Center article

### Talk
- `get_talk_stats`: Get Zendesk Talk statistics

### Chat
- `list_chats`: List Zendesk Chat conversations

## Available Resources

- `zendesk://docs/{section}`: Access documentation for different sections of the Zendesk API

## License

MIT

Available Tools

49 tools
create_articleD

Inputs: title (required), body (required), section_id (required), locale, +4 more.

create_automationD

Inputs: title (required), conditions (required), actions (required), description.

create_groupD

Inputs: name (required), description.

create_macroD

Inputs: title (required), actions (required), description.

create_organizationD

Inputs: name (required), domain_names, details, notes, +1 more.

create_ticketD

Inputs: subject (required), comment (required), priority, status, +5 more.

create_triggerD

Inputs: title (required), conditions (required), actions (required), description.

create_userD

Inputs: name (required), email (required), role, phone, +3 more.

create_viewD

Inputs: title (required), conditions (required), description.

delete_articleD

Inputs: id (required).

delete_automationD

Inputs: id (required).

delete_groupD

Inputs: id (required).

delete_macroD

Inputs: id (required).

delete_organizationD

Inputs: id (required).

delete_ticketD

Inputs: id (required).

delete_triggerD

Inputs: id (required).

delete_userD

Inputs: id (required).

delete_viewD

Inputs: id (required).

get_articleD

Inputs: id (required).

get_automationD

Inputs: id (required).

get_groupD

Inputs: id (required).

get_macroD

Inputs: id (required).

get_organizationD

Inputs: id (required).

get_talk_statsD

Inputs: no named parameters.

get_ticketD

Inputs: id (required).

get_triggerD

Inputs: id (required).

get_userD

Inputs: id (required).

get_viewD

Inputs: id (required).

list_articlesD

Inputs: page, per_page, sort_by, sort_order.

list_automationsD

Inputs: page, per_page.

list_chatsD

Inputs: page, per_page.

list_groupsD

Inputs: page, per_page.

list_macrosD

Inputs: page, per_page.

list_organizationsD

Inputs: page, per_page.

list_ticketsD

Inputs: page, per_page, sort_by, sort_order.

list_triggersD

Inputs: page, per_page.

list_usersD

Inputs: page, per_page, role.

list_viewsD

Inputs: page, per_page.

support_infoD

Inputs: no named parameters.

update_articleD

Inputs: id (required), title, body, locale, +4 more.

update_automationD

Inputs: id (required), title, description, conditions, +1 more.

update_groupD

Inputs: id (required), name, description.

update_macroD

Inputs: id (required), title, description, actions.

update_organizationD

Inputs: id (required), name, domain_names, details, +2 more.

update_ticketD

Inputs: id (required), subject, comment, priority, +5 more.

update_triggerD

Inputs: id (required), title, description, conditions, +1 more.

update_userD

Inputs: id (required), name, email, role, +4 more.

update_viewD

Inputs: id (required), title, description, conditions.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2/5.0

    Scored across 49 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific Zendesk resources (articles, tickets, users, etc.) with specific actions (create, get, list, update, delete). The naming convention makes it impossible to confuse tools since each combination of verb and resource name is unique and unambiguous.

    Naming Consistency5/5

    All 49 tools follow a perfectly consistent verb_noun pattern with snake_case throughout. The verbs (create, get, list, update, delete, search, support_info) are applied systematically across resources, creating a predictable and readable naming scheme.

    Tool Count2/5

    With 49 tools, this server feels excessively heavy for typical MCP usage. While Zendesk has many resource types, the tool count suggests over-fragmentation where a more consolidated approach might be more agent-friendly. This many tools will likely overwhelm agents and increase misselection risk.

    Completeness5/5

    The tool surface provides comprehensive CRUD coverage for all major Zendesk resources (articles, automations, groups, macros, organizations, tickets, triggers, users, views) plus listing operations, search, and support info. There are no obvious gaps for the customer support domain this server targets.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      This server provides a comprehensive integration with Zendesk. Retrieving and managing tickets and comments. Ticket analyzes and response drafting. Access to help center articles as knowledge base.
      7
      126
      Apache 2.0
    • A
      license
      B
      quality
      D
      maintenance
      A server implementation that provides Claude AI with the ability to interact with Zendesk ticketing systems through various functions including retrieving, searching, creating, and updating tickets.
      7
      287 npm
      16
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Zendesk support workflows that enables ticket search, lookup, creation, commenting, status updates, and user listing through natural language. It uses OAuth authentication and supports both internal notes and public comments.
      MIT