Search for tickets using RT's TicketSQL query language. TicketSQL has non-obvious syntax — consult get_ticketsql_grammar before writing any query involving Status, date conditions, custom fields, or special values. Key syntax notes: Status has meta-values Active and Inactive that match all active/inactive statuses across lifecycles (e.g. Status = 'Active' rather than Status = 'open'). Basic examples: "Queue = 'General' AND Owner = 'Nobody'", "Subject LIKE 'login'". Always include fields=Subject,Status,Queue,Owner,Requestor,Priority,LastUpdated,Due unless context calls for a different set.

Get detailed information about a specific ticket by its ID

Get the full details of a single transaction including decoded message content. Use this after get_ticket_history to read the actual text of a reply or comment.

Get the transaction history for a ticket. Returns a list of transactions (comments, replies, status changes, etc.)

List all attachments on a ticket (names, MIME types, sizes, IDs)

Retrieve a single attachment by ID. Text content is returned decoded; binary content is returned as MIME Base64. Use get_ticket_attachments or get_transaction to find attachment IDs.

Save an attachment to a local file. The MCP server writes the file directly, so this works on any platform. If path is a directory, the original filename is used.

Get details about a specific queue by ID or name

List all available queues

Returns the TicketSQL grammar reference for RT 6.0.2. Consult this before writing any TicketSQL query — especially for Status conditions, date/time fields, custom fields, and link fields where syntax is non-obvious.

Get the RT user account associated with the configured auth token. Use this to determine who "I" or "me" refers to when the user asks to assign tickets to themselves, find their own tickets, etc.

Search for RT users by name or email address

Get custom fields (with types and allowed values) and lifecycle name for a queue

Create a new ticket in RT

Update an existing ticket. Pass each property to change as a top-level parameter (e.g. Due, Status, Owner) — do NOT use a nested "fields" object.

Add an internal comment to a ticket (not visible to the requestor)

Send a reply (correspondence) on a ticket, visible to the requestor