mcp-server-rt
OfficialRelated Servers
Alternatives to mcp-server-rt
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
- AlicenseBqualityBmaintenanceEnables secure interaction with Request Tracker (RT) for ticket management, including search, creation, updates, resolution, time tracking, and workflow automation.17AGPL 3.0

tickiti-mcpofficial
AlicenseBqualityBmaintenanceAn MCP server that exposes the Tickiti helpdesk API to AI assistants, enabling ticket management and helpdesk operations via natural language.11MIT- AlicenseAqualityBmaintenanceMCP server that exposes the i-net HelpDesk Ticket Web-API as tools for AI agents, enabling ticket search, reading, creation, and actions like replying, closing, and escalating, with attachment support.8MIT
- AlicenseBqualityBmaintenanceAn MCP server that enables AI assistants to create, search, and manage OTRS tickets through standardized interfaces.5Apache 2.0
- AlicenseAqualityDmaintenanceMCP server for Otobo ITSM enabling AI assistants to search, create, update, and manage tickets via the Generic Interface REST API.1081MIT
TDQS
Scored across 43 tools
Each tool targets a distinct resource and action, and close pairs like list_group_members vs get_group and get_ticket_history vs get_transaction are explicitly differentiated in their descriptions. Even with 43 tools, the annotations make the intended selection clear without true overlap.
The vast majority of tools follow a clear verb_noun pattern such as get_, list_, create_, update_, add_, and remove_. Minor singular/plural inconsistencies like grant_rights vs revoke_right and add_group_members vs remove_group_member prevent a perfect score.
43 tools is a very large surface for a single server, spanning tickets, queues, groups, lifecycles, rights, and custom fields. Even though each tool appears purposeful, the count is well beyond the typical well-scoped MCP toolset and creates significant selection burden for agents.
Ticket, queue, lifecycle, and rights workflows are covered thoroughly, including create/read/update operations. However, group and custom field management lack update/delete operations, and user management is limited to lookup and current-user, leaving notable gaps in the administrative lifecycle.