mcp-server-rtofficial
A
licenseA
qualityA
maintenanceConnects AI assistants to a Request Tracker (RT) instance, enabling natural language ticket search, creation, updates, and queue management via the MCP protocol.
43
47 npm
9
GPL 2.0
MCP Request Tracker CrunchTools
by crunchtools
Related Servers
Alternatives to MCP Request Tracker CrunchTools
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to create, search, and manage OTRS tickets and configuration items via the OTRS API.7Apache 2.0
- AlicenseAqualityCmaintenanceEnables AI agents to interact with Redmine API for managing tickets, projects, users, and time entries. Supports comprehensive operations including issue creation/updates, project management, time logging, and search with dual authentication (Basic Auth + API Key).1436 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Autotask REST API for ticket management and querying through natural language.-
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Yandex Tracker through its API for managing tasks, comments, and attachments. It supports issue searching, status transitions, and metadata retrieval for automated project management.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to find and manage Redmine tickets via the Redmine REST API, supporting issue listing, details, updates, and comments.17 npmMIT
TDQS
B3.2/5.0
Scored across 17 tools
Disambiguation2/5
Several tools have overlapping purposes: set_ticket_status_tool overlaps with open_ticket_tool and resolve_ticket_tool, while set_ticket_owner_tool overlaps with take_ticket_tool. get_my_open_tickets_tool and get_new_tickets_tool also largely duplicate functionality available through search_tickets_tool. The descriptions help somewhat, but the boundaries between general tools and workflow shortcuts are unclear.
Naming Consistency4/5
Tool names consistently use snake_case with a verb-first pattern and a _tool suffix (e.g., get_ticket_tool, set_ticket_status_tool). Minor deviations like reply_to_ticket_tool and complete_weekly_checklist_tool introduce prepositions or workflow-specific phrasing, but the overall pattern remains predictable.
Tool Count3/5
17 tools is on the heavy side for this domain, especially given the functional overlap between several tools. A ticketing system can reasonably support this many operations, but some tools (take_ticket_tool, open_ticket_tool, resolve_ticket_tool) could be consolidated without losing much capability.
Completeness4/5
The core ticket lifecycle is well covered: create, search, get details/history, update fields, manage owner/status, comment/reply, track time, and resolve. Minor gaps exist, such as no explicit attachment handling, queue management, or dedicated ticket deletion, but status can be set to deleted and most workflows are supported.
Maintenance
ActivityMaintained
ResponsivenessNo issues