Get started

Request Tracker (RT) for AI agents

Request Tracker (RT) is an open-source ticketing system for managing support requests, queues, assets, and knowledge articles across a help desk. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect Request Tracker (RT)See the 11 actions ↓
Customer supportAPI keyMCP + RESTbestpractical.com
AUDIT LOG · REQUEST TRACKER (RT)POLICY: acme-support
09:41:07 · claude · u_8f2read
request_tracker_rt.list_queues
List Queues✓ allowed · 212ms
09:41:08 · claude · u_8f2read
request_tracker_rt.get_queue
Get Queue✓ allowed · 164ms
09:41:09 · claude · u_8f2write
request_tracker_rt.create_ticket
Create Ticket✓ approved · approved by user
EVERY REQUEST TRACKER (RT) CALL, ON THE RECORD
01 · USE CASES

What agents do in Request Tracker (RT).

01

Search open tickets

Search tickets in a queue to find ones still waiting on a customer response.

02

Reply to a ticket

Reply to a ticket with an update once the underlying issue is resolved.

03

Check history before closing

Get a ticket's full history first, then update its status only after confirming nothing is outstanding.

02 · ACTIONS

11 Request Tracker (RT) actions, graded by risk.

Every Request Tracker (RT) action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

7

Look things up. Allowed by default.

  • request_tracker_rt.get_queue
    Get Queue
  • request_tracker_rt.get_ticket
    Get Ticket
  • request_tracker_rt.list_queues
    List Queues
  • request_tracker_rt.search_users
    Search Users
  • request_tracker_rt.search_tickets
    Search Tickets
  • request_tracker_rt.get_ticket_history
    Get Ticket History
  • request_tracker_rt.list_ticket_attachments
    List Ticket Attachments

write

4

Create and change things. Allow, or ask the user first.

  • request_tracker_rt.create_ticket
    Create Ticket
  • request_tracker_rt.update_ticket
    Update Ticket
  • request_tracker_rt.add_ticket_comment
    Add Ticket Comment
  • request_tracker_rt.reply_to_ticket
    Reply to Ticket

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · HOW IT WORKS

Request Tracker (RT) in three steps.

  1. 01Your users connect Request Tracker (RT)They add their Request Tracker (RT) api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, and writes like “create Ticket” can wait for the user to approve.
  3. 03Any agent can actYour agent calls Request Tracker (RT) through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('request_tracker_rt', {
  read: 'allow',
  write: 'ask',        // create_ticket
  destructive: 'deny',  
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Request Tracker (RT) connects.

Users add their Request Tracker (RT) api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Request Tracker (RT) connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Request Tracker (RT) from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More customer support apps.

Intercom133 actionsGleap179 actionsHelp Scout129 actionsSupportbee41 actionsProductlane39 actionsHelpwise37 actionsFuseDesk27 actionsOnedesk24 actions
ALL CUSTOMER SUPPORT APPS →
07 · FAQ

Request Tracker (RT) and Arc0, answered.

Q01

Can I use Request Tracker (RT) with Claude, ChatGPT or Cursor?

Yes. Connect Request Tracker (RT) to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Request Tracker (RT) actions you allow.

Q02

How do users connect Request Tracker (RT)?

Users add their Request Tracker (RT) api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Request Tracker (RT) actions can my agent take?

11 in total: 7 read, 4 write and 0 destructive, such as “create Ticket”. Your policies decide which of them each agent may call.

Q04

Can I make my agent read-only in Request Tracker (RT)?

Yes. Allow read actions and deny writes in the Request Tracker (RT) policy. Your agent can still look things up, and any write it attempts is blocked and logged.

Q05

Can my own backend call Request Tracker (RT) too?

Yes. The same Request Tracker (RT) connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Request Tracker (RT) into your agent.

Your users connect Request Tracker (RT) once, under your brand. Your agent gets 11 actions behind your policies, with every call on the record.

Connect Request Tracker (RT)Browse all apps →

Free to build · MCP + REST · Audit log on every plan