Zendesk Live MCP
Related Servers
Alternatives to Zendesk Live MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceRead-only MCP server for querying Movidesk tickets through the public Movidesk API.13 npm-
- AlicenseBqualityBmaintenanceAn MCP server that provides operational tooling over the Zendesk Support API — ticket triage, SLA monitoring, agent workload analysis, and system health audits.111MIT
- AlicenseAqualityBmaintenanceMCP server exposing Cursor's HTTP APIs for managing Cloud Agents, Team/Org Admin, Analytics, Bugbot, AI Code Tracking, and Fleet with read-only and read-write modes.61MIT
- AlicenseBqualityCmaintenanceRead-only MCP server for querying Shopify analytics data, including orders, customers, products, sales, retention, and attribution.19MIT
- AlicenseAqualityCmaintenanceRead-only MCP server for Twilio call data, providing tools to search calls, fetch recordings and transcripts, list agents, and generate summaries while explicitly handling timezone and duration measurement discrepancies.6MIT
- AlicenseAqualityDmaintenanceMCP server that authenticates via browser session cookies to access Zendesk's REST API without API tokens, supporting reads and writes with agent permissions.199 npm1MIT
TDQS
Scored across 6 tools
The three reporting tools (build_ticket_dashboard, dashboard_by_field, run_ticket_report) have overlapping purposes as they all produce ticket reports, though descriptions distinguish complete dashboards from single breakdowns and custom grouped reports. An agent could still confuse dashboard_by_field with run_ticket_report, but the guidance (e.g., 'use build_ticket_dashboard') helps.
Five tools follow a clear verb_noun pattern (list, build, run, search, get), but dashboard_by_field breaks the pattern with a noun-phrase style, creating a minor inconsistency.
Six tools is a reasonable number for a Zendesk reporting server, with no redundant or extraneous tools.
The tool set covers field discovery, ticket searching, detail retrieval, and multiple reporting/breakdown capabilities. The only notable gap is the lack of a direct 'list all tickets' tool, but search_live_tickets can fulfill this, so it's a minor gap.