Request Tracker (RT)
Request Tracker is a ticketing and workflow platform for managing support requests, queues, users, assets, knowledge articles, and related operations.
Integration
- Vendor
- Request Tracker (RT)
- Category
- other
- Auth
- API_KEY
- Tools
- 11
- Composio slug
request_tracker
Tools
- Add Ticket Comment
Add a private internal comment to an RT ticket. The comment creates a durable transaction that REST2 cannot remove; RT scrips may still notify staff.
- Create Ticket
Create a durable RT ticket in a queue. Creation may run RT scrips or send notifications and cannot be fully erased through REST2.
- Get Queue
Retrieve one visible RT queue by id or exact name, including lifecycle and capability-sensitive links.
- Get Ticket
Retrieve one visible RT ticket, including its current fields and capability-sensitive links for allowed follow-up operations.
- Get Ticket History
Return one page of detailed ticket history, including transaction types, field changes, comments, creators, and timestamps.
- List Queues
List queues visible to the connected RT user so an agent can select a queue for ticket search or creation. Returns one bounded page.
- List Ticket Attachments
List attachment metadata references associated with a visible RT ticket without downloading attachment content.
- Reply to Ticket
Send public correspondence on an RT ticket. This can email requestors or other recipients according to RT configuration and creates a durable transaction that REST2 cannot remove.
- Search Tickets
Search visible RT tickets with an explicit TicketSQL expression and return one bounded page. Use a condition such as `id > 0` when listing tickets; an omitted search does not list all tickets.
- Search Users
Search RT users with structured field conditions and return one bounded page of user references or selected fields for requester and owner lookup.
- Update Ticket
Update selected metadata on an existing RT ticket and verify every requested field by reading it back. Omitted fields are unchanged.
Setup
- Create or open a Switchy Project.
- Open Integrations and connect Request Tracker (RT).
- Authorise through api_key. Switchy stores the connection against your org.
- Everyone in the Project can now @-mention the Request Tracker (RT) tools in chat.
What teammates see: by default, memories from Request Tracker (RT) are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.