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.8Apache 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
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Autotask REST API for ticket management and querying through natural language.MIT
- 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.5 npmMIT
TDQS
B3.4/5.0
Scored across 17 tools
Disambiguation4/5
Tools are mostly distinct, but there is overlap among set_ticket_owner_tool, take_ticket_tool, and open_ticket_tool, which all can set ownership or change status. complete_weekly_checklist_tool also duplicates a multi-step workflow, though its description clearly marks it as a shortcut. An agent may struggle to choose between the ownership/open variants.
Naming Consistency5/5
All tools use snake_case with a consistent _tool suffix and follow a verb_noun pattern (e.g., get_ticket_tool, set_ticket_status_tool). This is highly predictable and uniform throughout.
Tool Count4/5
17 tools is slightly above the typical 3-15 range but remains reasonable for a full ticket-tracking workflow with specialized actions. A few tools could be consolidated, but each generally has a clear role.
Completeness5/5
The surface covers the full ticket lifecycle: create, search, get, update, assign, status changes, comments (private/public), time tracking, history, and resolution. No major gaps for typical RT workflows.
Maintenance
ActivityActive
ResponsivenessWithin a week