FixFlow
Related Servers
Alternatives to FixFlow
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to analyze IT support tickets, categorize urgency, suggest responses, and retrieve statistics via MCP tools.-
- AlicenseBqualityCmaintenanceEnables MCP clients to search and manage customer support tickets, customer records, and knowledge base articles, with read-only and human-approved write workflows.81MIT
- FlicenseNot gradedqualityCmaintenanceEnables IT helpdesk operations such as retrieving user and device information, checking device status, and creating, retrieving, and updating support tickets through MCP tools.-
- FlicenseNot gradedqualityDmaintenanceMCP server that provides IT support tools to search known incidents, check ticket status, and create ticket drafts, enabling an AI assistant to help users with IT support queries.-
- 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 gradedqualityCmaintenanceEnables AI assistants to query and operate a help desk and service desk through MCP over HTTP, including tickets, requester communications, internal notes, attachments, stage and SLA history, time entries, clients, requesters, desks, knowledge base, contracts, and billing/satisfaction reports.MIT
TDQS
Scored across 5 tools
triage_request is an orchestrator that internally performs classification, manual search, warranty lookup, ticket creation, and escalation, so it overlaps heavily with search_manuals, check_warranty, and create_ticket. The descriptions do signal 'full workflow' vs. individual step, which helps, but agents must decide between one-shot triage and composing primitives with no guidance on when to prefer which.
All five tools follow a clean verb_noun snake_case pattern: triage_request, search_manuals, check_warranty, create_ticket, get_ticket. Verbs are distinct and predictable, and the resource noun is always at the end.
Five tools is well-scoped for a support triage workflow: one orchestrator plus four focused primitives. Each tool earns its place and nothing feels padded or missing at the count level.
Ticket handling is incomplete: you can create and get a ticket but not update, close, comment on, or list tickets, so agents hit dead ends after creation. Similarly, search_manuals returns article IDs but there is no tool to fetch a full article, and escalation only exists implicitly inside triage_request.