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 | |