RT MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RT_TOKEN | Yes | Your RT authentication token | |
| RT_BASE_URL | Yes | RT server base URL (e.g., https://rt.example.com/REST/2.0) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_ticketsA | Search for tickets using RT's TicketSQL query language. Returns summary information for matching tickets, with optional sorting and pagination. The
Call the get_ticketsql_grammar tool for the full TicketSQL field/operator reference. |
| get_ticketsql_grammarA | Get the TicketSQL query language reference (fields, operators, date literals, and examples) used by the search_tickets |
| get_ticketA | Get complete ticket information by ticket ID, including subject, status, queue, owner, dates, priority, and custom fields. |
| get_ticket_correspondenceA | Get ticket correspondence (comments and replies with attachments). Retrieves all correspondence entries grouped by transaction, showing inline text messages and file attachment metadata. |
| get_attachmentA | Download a specific attachment by ID. Returns base64-encoded content with metadata for any file type. |
| get_ticket_hierarchyA | Get ticket hierarchy (parent/child relationships). Builds the complete hierarchy tree if recursive=true, or only immediate relationships if recursive=false. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
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.
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.
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.
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.