RT (Request Tracker)

Connects Claude to a live RT (Request Tracker) instance via the REST2 API. Supports searching tickets with TicketSQL, reading ticket details and history, creating and updating tickets (including custom fields, custom roles, links, and date fields), adding comments and replies, and looking up queues and users.

View in the Claude registry

Integration type: Connector
Verification status: Verified connector
Platform: Claude
Category: Customer Support
Primary Subcategory: Helpdesk & Ticketing Platforms
Secondary Subcategories: None listed
Brand: Request Tracker
Access: Unknown
First tracked: 2026-03-31
Tool count: 17
Geography: US

Claude Discoverability Score

Your public score is being prepared

RT (Request Tracker) is tracked in the public registry. Its Discoverability Score will appear as soon as the public benchmark is ready - never as an estimate.

Get your Discoverability Score

Primary Subcategory

Competing in Claude Helpdesk & Ticketing Platforms

View Category

1Zoho Desk100/100

2Pylon82/100

3Unthread68/100

4Intercom11/100

5DevRev0/100

Score explained

How the Discoverability Score works

The Claude Discoverability Score will be the percentage of contested conversations where RT (Request Tracker) appears in the connector picker or Claude invokes it directly. Found and Positioned will be shown as diagnostics, not score inputs.

InvisibleBuriedEmergingCompetitiveWinning

Organic discovery scoring is pending. Your Connector score will appear on this scale when measurement goes live.

FoundDiagnostic

Whether Claude found your Connector in connector search. It must be Found before it can reach the picker, but the score counts picker appearances—not search results.

PickedMain score

How often your Connector appeared in the picker, or Claude invoked it directly, across contested conversations. This percentage is the Discoverability Score; the headline number is rounded.

PositionedDiagnostic

What position your Connector appeared in when it was shown in the picker. This shows prominence, but it does not affect the score.

Read the full scoring methodology Recommended guideHow to get your Claude Connector organically discoveredFollow the practical steps agents use to find, shortlist, and choose your Connector.

Tools

17 tools agents can invoke

Add an internal comment to a ticket (not visible to the requestor)
Send a reply (correspondence) on a ticket, visible to the requestor
Create a new ticket in RT
Retrieve a single attachment by ID
Get the RT user account associated with the configured auth token
Get details about a specific queue by ID or name
Get custom field definitions and lifecycle name for a queue
Get detailed information about a specific ticket by its ID
List all attachments on a ticket
Get the transaction history for a ticket
Returns the TicketSQL grammar reference for RT 6.0.2
Get the full details of a single transaction including decoded message content
List all available queues
Search for RT users by name or email address
Save an attachment to a local file
Search for tickets using RT's TicketSQL query language
Update fields on an existing ticket

RT (Request Tracker) FAQ

How do I improve a Verified connector's discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are RT (Request Tracker) alternatives on Claude?

As of 2026-08-14, RT (Request Tracker) competes with Zoho Desk, Pylon, Unthread, Intercom, DevRev, Freshservice, Front, Gorgias MCP, Siit AI service desk in Claude Helpdesk & Ticketing Platforms, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.