A
licenseA
qualityC
maintenanceProvides customer lookup, transaction history, knowledge-base search, and ticket management tools to any MCP client.
5
MIT
helpdesk-mcp
by s-talha
Related Servers
Alternatives to helpdesk-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables retrieval and management of tickets and comments, ticket analysis and response drafting, and access to Help Center articles as a knowledge base via MCP.-
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to list, create, and update support tickets, classify them by category, priority, and sentiment, detect duplicates, and answer queue questions using retrieval-augmented LLM tools.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI clients to access and manage an internal support ticket queue through MCP tools, resources, and prompts, including searching and viewing tickets, adding comments, closing tickets with confirmation, reading knowledge base articles, and viewing queue summaries over OAuth-secured Streamable HTTP.-
- AlicenseNot gradedqualityDmaintenanceEnables AI-driven customer support operations including conversation management, knowledge base, contacts, metrics, and settings via MCP.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search and retrieve support tickets, add notes, close tickets, and access SLA policies through MCP tools, resources, and prompts over Streamable HTTP.MIT
TDQS
B3.4/5.0
Scored across 8 tools
Disambiguation5/5
Each tool targets a distinct resource and action: search_tickets vs get_ticket (query vs single-fetch), ticket_stats (aggregates) vs search_tickets (filtered lists), get_customer vs get_ticket, and search_kb vs all ticket tools. add_comment and update_ticket also have clearly separate mutation scopes. No tool pair is likely to be confused.
Naming Consistency4/5
Seven tools follow a clean verb_noun pattern (search_tickets, get_ticket, get_customer, search_kb, add_comment, update_ticket, create_ticket). The lone outlier is ticket_stats, which is a noun-only name, a minor deviation from an otherwise predictable convention.
Tool Count5/5
Eight tools is well within the ideal range and each earns its place by covering a distinct capability (search, fetch, create, update, comment, stats, KB, customer). No redundant or filler tools are present.
Completeness4/5
Core helpdesk lifecycle is covered: create/read/search/update tickets, comment, stats, KB search, and customer lookup. Minor gaps exist (no customer listing/search, no comment editing or deletion), but the closed-is-final status workflow makes ticket deletion reasonably unnecessary.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues