Zendesk MCP by usefulapi

Last 30 days

Uptime

100%

Response time

229 ms typical, 229 ms slowest 5%

Last check

2 h ago

Next check

in 4 h

How to call it

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "zendesk-mcp-by-usefulapi": {
      "type": "http",
      "url": "https://zendesk.usefulapi.io/mcp"
    }
  }
}

19 tools

• zendesk_search

  Unified search across tickets, users, organizations and groups using Zendesk search syntax. Examples: `type:ticket status:open`, `type:user email:[email protected]`, `type:organization name:acme`. Zendesk REST: GET /search.json.

• zendesk_list_tickets

  List recent tickets (offset pagination). Zendesk REST: GET /tickets.json.

• zendesk_get_ticket

  Fetch a single ticket by id. Zendesk REST: GET /tickets/{id}.json.

• zendesk_list_ticket_comments

  List the comments (public replies and internal notes) on a ticket, oldest first. Zendesk REST: GET /tickets/{id}/comments.json.

• zendesk_current_user

  Return the currently authenticated user — a quick way to verify credentials and subdomain. Zendesk REST: GET /users/me.json.

• zendesk_get_user

  Fetch a single user by id. Zendesk REST: GET /users/{id}.json.

• zendesk_search_users

  Find users by name, email, phone, or other attributes. Zendesk REST: GET /users/search.json.

• zendesk_list_organizations

  List organizations (offset pagination). Zendesk REST: GET /organizations.json.

• zendesk_get_organization

  Fetch a single organization by id. Zendesk REST: GET /organizations/{id}.json.

• zendesk_list_groups

  List agent groups. Zendesk REST: GET /groups.json.

• zendesk_list_views

  List saved ticket views (curated ticket lists). Use zendesk_execute_view to run one. Zendesk REST: GET /views.json.

• zendesk_execute_view

  Run a saved view by id and return the matching tickets. Zendesk REST: GET /views/{id}/execute.json.

• zendesk_list_macros

  List macros (reusable sets of ticket actions/replies agents apply). Zendesk REST: GET /macros.json.

• zendesk_list_ticket_fields

  List all standard and custom ticket fields — useful for discovering field ids/values before creating or updating tickets. Zendesk REST: GET /ticket_fields.json.

• zendesk_get_ticket_metrics

  Fetch SLA / response / resolution time metrics for a ticket. Zendesk REST: GET /tickets/{id}/metrics.json.

• zendesk_list_satisfaction_ratings

  List customer satisfaction (CSAT) ratings, optionally filtered by score. Zendesk REST: GET /satisfaction_ratings.json.

• zendesk_create_ticket

  MUTATING: create a new support ticket. `subject` and `comment_body` are required; the comment becomes the ticket's first message. Zendesk REST: POST /tickets.json.

• zendesk_update_ticket

  MUTATING: update an existing ticket. Provide the ticket `id` plus at least one field to change (status, priority, assignee_id, group_id, type, tags, or a comment). Zendesk REST: PUT /tickets/{id}.json.

• zendesk_add_ticket_comment

  MUTATING: add a comment to a ticket. `public` defaults to true (a reply visible to the requester); set it false for an internal agent note. Convenience over PUT /tickets/{id}.json.

Security scan

• No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks