How to integrate Request Tracker (RT) MCP with Claude Agent SDK

This guide walks you through connecting Request Tracker (RT) to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Request Tracker (RT) agent that can search your support tickets, create tickets, review ticket history, reply to tickets, and update tickets through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Request Tracker (RT) account through Composio's Request Tracker (RT) MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for freeGet a demo
Request Tracker (RT) logoRequest Tracker (RT)
Api Key

Request Tracker (RT) is a ticketing and workflow platform for managing support requests, queues, users, assets, and knowledge articles. It helps support and operations teams track work, enforce process, and keep request history in one place.

11 Tools

Introduction

This guide walks you through connecting Request Tracker (RT) to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Request Tracker (RT) agent that can search your support tickets, create tickets, review ticket history, reply to tickets, and update tickets through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Request Tracker (RT) account through Composio's Request Tracker (RT) MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Request Tracker (RT) with

OpenAI Agents SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Request Tracker (RT)
  • Configure an AI agent that can use Request Tracker (RT) as a tool
  • Run a live chat session where you can ask the agent to perform Request Tracker (RT) operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

What is the Request Tracker (RT) MCP server, and what's possible with it?

The Request Tracker (RT) MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Request Tracker (RT) account. It provides structured and secure access to your tickets, queues, users, ticket histories, and attachment details, so your agent can search, create, review, update, and respond to tickets on your behalf.

  • Ticket search and review: Have your agent find tickets using specific criteria and retrieve their current details for quick review.
  • Ticket creation and updates: Direct your agent to create tickets in the right queue or update selected ticket details as work progresses.
  • Replies and internal comments: Let the agent send public replies to requesters or add private comments for your support team.
  • Queue and user lookup: Instruct your agent to browse available queues and find users when choosing ticket requesters or owners.
  • History and attachment review: Have your agent review ticket activity, field changes, comments, timestamps, and available attachment details.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Request Tracker (RT) account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Request Tracker (RT) functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Request Tracker (RT)
  const session = await composio.create(USER_ID, {
    toolkits: ['request_tracker'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Request Tracker (RT)
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Request Tracker (RT) tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Request Tracker (RT)
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Request Tracker (RT) and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['request_tracker']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Request Tracker (RT) tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Request Tracker (RT) through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
TOOLS

Supported Tools

Every Request Tracker (RT) action and event your agent gets out of the box.

Add Ticket Comment

Add a private internal comment to an RT ticket.

Create Ticket

Create a durable RT ticket in a queue.

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.

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.

Search Tickets

Search visible RT tickets with an explicit TicketSQL expression and return one bounded page.

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.

FRAMEWORKS

How to build Request Tracker (RT) MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Request Tracker (RT) MCP with OpenAI Agents SDK

Claude Code logo

Claude Code

Use Request Tracker (RT) MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Request Tracker (RT) MCP with Claude Cowork

Codex logo

Codex

Use Request Tracker (RT) MCP with Codex

OpenClaw logo

OpenClaw

Use Request Tracker (RT) MCP with OpenClaw

Hermes logo

Hermes

Use Request Tracker (RT) MCP with Hermes

CLI logo

CLI

Use Request Tracker (RT) MCP with CLI

Google ADK logo

Google ADK

Use Request Tracker (RT) MCP with Google ADK

LangChain logo

LangChain

Use Request Tracker (RT) MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Request Tracker (RT) MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Request Tracker (RT) MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Request Tracker (RT) MCP with LlamaIndex

CrewAI logo

CrewAI

Use Request Tracker (RT) MCP with CrewAI

FAQ

Frequently asked questions

With a standalone Request Tracker (RT) MCP server, the agents and LLMs can only access a fixed set of Request Tracker (RT) tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Request Tracker (RT) and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Agent SDK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Request Tracker (RT) tools.

Yes, absolutely. You can configure which Request Tracker (RT) scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Request Tracker (RT) data and credentials are handled as safely as possible.

Start with Request Tracker (RT).It takes 30 seconds.

Managed auth, hosted MCP servers, and every Request Tracker (RT) tool your agent needs.Free to start.

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies