App

Request Tracker (RT) integrations

Connect Request Tracker (RT) to any other app, or use it from your AI client over MCP. Request Tracker (RT) is an open-source, enterprise-grade ticketing system.

Connects with an API keybestpractical.com

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

Build solutions, not workarounds.

What do you want to automate with Request Tracker (RT)?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

Set it up in your client
Claude Code

Run this in the directory you want to work in.

claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai

Start Claude Code there, approve the server, and sign in in the browser page it opens.

Claude Code guide (opens in a new tab)
Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

Setup guide (opens in a new tab)
Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

Setup guide (opens in a new tab)
Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

Setup guide (opens in a new tab)
Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

Setup guide (opens in a new tab)
Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

Setup guide (opens in a new tab)

Pair it

Connect Request Tracker (RT) with another app

What your agent can do with Request Tracker (RT)

Triggers and actions 3 triggers · 19 actions

  • Trigger
    Ticket Correspondence

    Triggers when a ticket is replied to (that is, corresponded with).

  • Trigger
    Ticket Created

    Triggers when a new Request Tracker ticket is created.

  • Trigger
    Ticket Status Changed

    Triggers when a Request Tracker ticket changes status. Can watch for any status change or only for changes to a specific status.

  • Action
    Add asset

    Create an asset.

  • Action
    Add user

    Create a user.

  • Action
    Comment on a Ticket

    Add an internal comment to a ticket and send to any internal watchers.

  • Action
    Create Ticket

    Create a new ticket in Request Tracker.

  • Action
    Find Attachment

    Locate an attachment by ID.

  • Action
    Find Ticket

    Locate a ticket by ID.

  • Action
    Find Tickets

    Issue a query to find matching tickets.

  • Action
    Find Transaction

    Find a transaction by ID

  • Action
    Get asset

    Retrieves one asset by ID: name, description, status, catalog, owner, held by, contact, custom fields.

  • Action
    Get queue

    Get a queue by id or name.

  • Action
    Get user

    Get a user by id or name.

  • Action
    List queues

    List all queues visible to user.

  • Action
    List ticket history

    List transactions of a ticket.

  • Action
    Reply to a Ticket

    Reply to the requestor and any internal or external watchers of a ticket.

  • Action
    Update ticket

    General ticket update (Owner, Priority, Queue, custom fields).

  • Action
    Update Ticket Due Date

    Update the due date of a ticket.

  • Action
    Update Ticket Status

    Update the status of a ticket.

  • Action
    Update Ticket Subject

    Update the subject of a ticket.

  • Action
    Update user

    Update a user.

Reviews

What our customers say

Questions

Request Tracker (RT), answered

Is there a Request Tracker (RT) MCP server?

APIANT's MCP server at https://mcp.apiant.ai works with Request Tracker (RT). Add that address to any AI client that takes a remote MCP server, sign in once in your browser, and your client can build, test and run automations that use Request Tracker (RT). Nothing to install.

What can start an automation from Request Tracker (RT)?

Any of Request Tracker (RT)'s 3 triggers in the catalog, including Ticket Created, Ticket Status Changed and Ticket Correspondence. Describe the moment in plain language and your agent picks the right one.

What can your agent do in Request Tracker (RT)?

Any of Request Tracker (RT)'s 19 actions, including Create Ticket, Update ticket, Update Ticket Due Date and Update Ticket Status. Your agent maps the data both ways and tests every scenario before it ships.

Which apps can Request Tracker (RT) connect to?

Any app in the catalog; the list on this page pairs Request Tracker (RT) with each of them. If the other app is missing, point your agent at its API documentation and it builds the connector.

What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.