Tidio MCP Server
Related Servers
Alternatives to Tidio MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables AI agents to interact with Freshdesk, supporting ticket management, customer and company operations, agent lookup, and knowledge base search through natural language.19MIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with the Gorgias helpdesk API, providing tools to manage tickets, customers, and other helpdesk functionalities through natural language.4-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to manage Intercom support workflows, including searching and updating contacts, handling conversations, assigning and closing tickets, and logging notes.-
- FlicenseAqualityCmaintenanceEnables AI agents to create, query, search, and manage Movidesk tickets directly via natural language.813 npm1-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage Gorgias support tickets: list open tickets, read conversation history, draft internal notes, send outbound replies (gated), and look up customer history.MIT

Xalantis MCP Serverofficial
AlicenseAqualityBmaintenanceEnables managing support tickets from Claude, Cursor, and other AI tools, including listing, creating, updating, and replying to tickets.67 npmMIT
TDQS
Scored across 16 tools
Each tool targets a distinct resource and action: contacts, tickets, departments, operators, and contact properties are cleanly separated. Even similar-sounding operations like reply_to_a_ticket and add_internal_note_to_a_ticket are clearly differentiated by their public/internal nature and descriptions.
The vast majority of tools follow a clear verb_noun pattern (get_contacts, create_ticket, delete_contact). Two exceptions, reply_to_a_ticket and add_internal_note_to_a_ticket, use longer verb-preposition phrases, which are slightly inconsistent but still predictable and readable.
16 tools is just above the typical well-scoped range of 3-15, but the count feels justified for a customer support platform covering contacts, tickets, and related operational entities. There is no bloat or redundancy.
Contacts and tickets both have full CRUD coverage, and ticket-specific actions like replying, adding notes, and unassigning are present. Minor gaps exist, such as lack of ticket filtering or department/operator management, but these are not critical for the primary workflows.