customer-support-mcp
Related Servers
Alternatives to customer-support-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables natural language queries, CRUD operations, and analytics on a PostgreSQL database (Neon) via Claude, supporting customers, tickets, products, and analytics.MIT
- FlicenseNot gradedqualityCmaintenanceEnables ticket management and AI triage through Mistral-compatible models, with tools for creating, listing, retrieving, triaging, and updating support tickets.-
- FlicenseNot gradedqualityDmaintenanceEnables querying and managing a CRM database through natural language conversations with Claude Desktop.-

Xalantis MCP Serverofficial
AlicenseAqualityBmaintenanceEnables managing support tickets from Claude, Cursor, and other AI tools, including listing, creating, updating, and replying to tickets.615 npmMIT- FlicenseNot gradedqualityDmaintenanceEnables Claude to access and manage a travel company's customer data, trip history, and information requests. Supports searching customers, querying trips by destination or date, and tracking customer inquiries through natural language.1-
- FlicenseNot gradedqualityCmaintenanceExposes read-only knowledge base articles on returns, warranty and shipping policies alongside tools that search, retrieve and create real support tickets. This lets an LLM agent ground its answers in store policy without inventing information, and act on actual ticket data rather than simulated records.-
TDQS
Scored across 13 tools
Most tools are distinct, but get_ticket_tool and get_ticket_details_tool overlap, as do resolve_ticket_tool and change_ticket_status_tool. The descriptions provide clear guidance on when to use each, so an agent can disambiguate, though slight redundancy exists.
All tool names follow a consistent verb_noun pattern with snake_case, e.g., get_customer_tool, list_tickets_tool, change_ticket_status_tool. No mixed conventions or irregular verbs.
With 13 tools covering customers, tickets, comments, assignments, and knowledge articles, the count is well-scoped for a customer support server. Each tool serves a clear purpose without excessive redundancy.
The surface covers core customer and ticket lifecycles: create/get/list for customers, full ticket management (create, list, get, status changes, resolve, assign, comment, delete). Minor gaps include no update/delete for customers and no ability to modify ticket content, but these are not critical for typical support workflows.