A
licenseA
qualityD
maintenanceRead-only MCP server for the HIT ticket management system that lists queues, searches/fetches ticket details, and lists ticket templates.
4
4 npm
1
MIT
RT MCP Server
by msekoranja
Related Servers
Alternatives to RT MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for Request Tracker REST2 API, enabling ticket, queue, user, and asset management via natural language.MIT
- FlicenseNot gradedqualityDmaintenanceRead-only MCP server for querying Movidesk tickets through the public Movidesk API.6 npm-
mcp-server-rtofficial
AlicenseAqualityAmaintenanceConnects AI assistants to a Request Tracker (RT) instance, enabling natural language ticket search, creation, updates, and queue management via the MCP protocol.4352 npm9GPL 2.0- AlicenseNot gradedqualityCmaintenanceA read-only MCP server for querying Redmine issue data via the Redmine REST API, designed for seamless integration with AI assistants.4 npmMIT
- AlicenseNot gradedqualityDmaintenanceRead-only MCP server that allows interaction with a Jama Connect instance via tools, wrapping the official py-jama-rest-client library.18MIT
TDQS
A4/5.0
Scored across 6 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: grammar reference, single ticket retrieval, search, correspondence, attachment download, and hierarchy. There is no overlap between tools, and an agent can easily select the right one.
Naming Consistency5/5
Tool names follow a consistent verb_noun pattern, mostly using 'get_' (get_ticket, get_correspondence, get_attachment, get_hierarchy) plus 'search_tickets' which appropriately uses 'search' for the query capability. All names are snake_case and readable.
Tool Count5/5
Six tools is well-scoped for an RT ticket system. The set covers core read operations without being bloated, and each tool serves a distinct and necessary function.
Completeness3/5
The tool set provides solid read coverage: retrieval, search, correspondence, attachments, and hierarchy. However, it lacks any write operations such as creating or updating tickets, replying, or changing status, which are fundamental to a ticketing system and would likely be expected by agents.
Maintenance
ActivityMaintained
ResponsivenessNo issues