A
licenseA
qualityB
maintenanceRead-only MCP server for Request Tracker (RT) via REST2 API, enabling ticket search, retrieval, correspondence viewing, attachment download, and hierarchy exploration.
6
26 npm
1
MIT
No user-submitted related servers found.
Scored across 4 tools
Each tool targets a distinct resource: individual ticket details, queues, templates, and ticket lists. No overlap in functionality.
All tools follow a consistent verb_noun pattern with underscores: get_ticket, list_queues, list_templates, list_tickets.
4 tools is a reasonable number for a read-only ticket system interface, each serving a clear purpose without being excessive.
The tool set is limited to read operations (list/get) and lacks any create, update, delete, or action tools for tickets, leaving significant gaps for a full workflow.