# How to integrate Reply MCP with OpenAI Agents SDK

```json
{
  "title": "How to integrate Reply MCP with OpenAI Agents SDK",
  "toolkit": "Reply",
  "toolkit_slug": "reply",
  "framework": "OpenAI Agents SDK",
  "framework_slug": "open-ai-agents-sdk",
  "url": "https://composio.dev/toolkits/reply/framework/open-ai-agents-sdk",
  "markdown_url": "https://composio.dev/toolkits/reply/framework/open-ai-agents-sdk.md",
  "updated_at": "2026-05-12T10:23:54.555Z"
}
```

## Introduction

This guide walks you through connecting Reply to the OpenAI Agents SDK using the Composio tool router. By the end, you'll have a working Reply agent that can list all active email campaigns this week, get contacts in your 'leads q3' list, show all available email templates through natural language commands.
This guide will help you understand how to give your OpenAI Agents SDK agent real control over a Reply account through Composio's Reply MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Reply with

- [Claude Agent SDK](https://composio.dev/toolkits/reply/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/reply/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/reply/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/reply/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/reply/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/reply/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/reply/framework/cli)
- [Google ADK](https://composio.dev/toolkits/reply/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/reply/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/reply/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/reply/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/reply/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/reply/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- Get and set up your OpenAI and Composio API keys
- Install the necessary dependencies
- Initialize Composio and create a Tool Router session for Reply
- Configure an AI agent that can use Reply as a tool
- Run a live chat session where you can ask the agent to perform Reply operations

## What is OpenAI Agents SDK?

The OpenAI Agents SDK is a lightweight framework for building AI agents that can use tools and maintain conversation state. It provides a simple interface for creating agents with hosted MCP tool support.
Key features include:
- Hosted MCP Tools: Connect to external services through hosted MCP endpoints
- SQLite Sessions: Persist conversation history across interactions
- Simple API: Clean interface with Agent, Runner, and tool configuration
- Streaming Support: Real-time response streaming for interactive applications

## What is the Reply MCP server, and what's possible with it?

The Reply MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Reply.io account. It provides structured and secure access to your sales engagement platform, so your agent can create and manage lists, fetch campaign schedules, organize contacts, and monitor outreach performance for you.
- Personal list creation and management: Easily instruct your agent to create, organize, or delete personal contact lists to streamline your outreach workflow.
- Contact organization and retrieval: Have your agent fetch contacts within specific lists, helping you target and personalize campaigns more effectively.
- Campaign and schedule insights: Ask your agent to retrieve all campaign schedules or see which campaigns a specific contact belongs to, giving you up-to-date visibility into your outreach pipeline.
- Email account and template discovery: Let your agent pull a list of available email accounts or fetch your personal, team, and community templates for quick access while composing new campaigns.
- Blacklist monitoring and management: Direct your agent to retrieve the full list of blacklisted domains and emails, so you can ensure compliance and maintain deliverability standards with ease.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `REPLY_CREATE_LIST` | Create Personal List | Tool to add a new personal list on the People page. Use when you need to organize contacts into a custom list. |
| `REPLY_DELETE_EMAIL_ACCOUNT` | Delete Email Account | Tool to delete a specific email account. Use when you need to remove an existing email account identified by its ID. |
| `REPLY_DELETE_LIST_BY_ID` | Delete List By ID | Tool to delete a list by its ID. Use when you need to remove a personal list you own. |
| `REPLY_DELETE_SEQUENCE` | Delete Sequence | Tool to delete a sequence. Use after confirming the sequence exists to remove it permanently. |
| `REPLY_DELETE_USER` | Delete User | Tool to delete a user. Use after confirming the user exists to remove them permanently. |
| `REPLY_GENERATE_ULID` | Generate ULID | Generate ULID |
| `REPLY_GET_ALL_LISTS` | Get All Lists | Tool to retrieve all available people lists. Use when you need to list all lists in your Reply account. |
| `REPLY_GET_BLACKLIST_ALL` | Get full blacklist of domains and emails | Tool to retrieve the full list of blacklisted domains and emails. Use after confirming updates to the blacklist when you need a complete view. |
| `REPLY_GET_CAMPAIGN_SCHEDULES_ALL` | Get all campaign schedules | Retrieves all campaign schedules from Reply.io, including the default schedule and any user-created schedules. Each schedule contains timezone settings, daily timing configurations (mainTimings), and follow-up timings. Use this to view available schedules before assigning one to a campaign or to audit existing schedule configurations. |
| `REPLY_GET_CAMPAIGNS_FOR_CONTACT` | Get Campaigns For Contact | Tool to retrieve campaigns a contact belongs to by contact ID. Use when you need to list all sequences (campaigns) associated with a specific contact. |
| `REPLY_GET_CONTACTS_IN_LIST_BY_ID` | Get Contacts in List by ID | Tool to retrieve contacts in a specific personal list. Use after obtaining the list ID when you need a paginated set of contacts for that list. |
| `REPLY_GET_LIST_BY_ID` | Get List by ID | Tool to return a specific people list by its ID. Use after you know the list ID and need its details. |
| `REPLY_GET_TEMPLATES_LIST` | Get templates list | Retrieves all email templates from Reply.io, including user-created, team-shared, organization-wide, and community templates. Use this to browse available templates before sending emails or creating campaigns. No parameters required - returns all accessible templates for the authenticated user. |
| `REPLY_LIST_CAMPAIGNS` | List Campaigns | Tool to list all campaigns (sequences). Use when you need a paginated list of campaigns. |
| `REPLY_LIST_CONTACTS_BASIC` | List Contacts Basic | Tool to list contacts. Use when verifying API access and gathering contact IDs. |
| `REPLY_LIST_EMAIL_ACCOUNTS` | Reply.io List Email Accounts | Tool to list all email accounts. Use when you need to retrieve email accounts page by page. |
| `REPLY_MARK_CONTACT_AS_FINISHED` | Mark Contact As Finished | Marks a contact (by email) or all contacts under a domain as finished in all Reply.io campaigns. Use this tool to stop outreach for contacts who have been successfully engaged or should no longer receive campaign messages. - When using 'email': The specific contact must exist and be enrolled in at least one campaign. - When using 'domain': Marks all contacts with that email domain as finished (succeeds even if no contacts match). Note: Provide exactly one of 'email' or 'domain', not both. |
| `REPLY_MARK_CONTACT_AS_REPLIED` | Mark Contact as Replied | Tool to mark a contact as replied in all campaigns by email or domain. Use after confirming the contact has responded. |
| `REPLY_MOVE_CONTACTS_TO_LISTS` | Move Contacts to Lists | Tool to move one or more contacts to specified lists. Use when reorganizing contacts across lists after verifying contact and list IDs. |
| `REPLY_REMOVE_DOMAIN_FROM_BLACKLIST` | Remove Domain from Blacklist | Tool to remove the specified domain from the blacklist. Use when you need to allow sending to that domain again. |
| `REPLY_SEARCH_CONTACTS` | Search Contacts by Email | Tool to search contacts by email. Use when you need to find existing contact IDs for update tests. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Reply MCP server is an implementation of the Model Context Protocol that connects your AI agent to Reply. It provides structured and secure access so your agent can perform Reply operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before starting, make sure you have:
- Composio API Key and OpenAI API Key
- Primary know-how of OpenAI Agents SDK
- A live Reply project
- Some knowledge of Python or Typescript

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models, or you can connect to another model provider.
- Keep the API key safe.
Composio API Key
- Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Go to Settings and copy your API key.

### 2. Install dependencies

Install the Composio SDK and the OpenAI Agents SDK.
```python
pip install composio_openai_agents openai-agents python-dotenv
```

```typescript
npm install @composio/openai-agents @openai/agents dotenv
```

### 3. Set up environment variables

Create a .env file and add your OpenAI and Composio API keys.
```bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com
```

### 4. Import dependencies

What's happening:
- You're importing all necessary libraries.
- The Composio and OpenAIAgentsProvider classes are imported to connect your OpenAI agent to Composio tools like Reply.
```python
import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';
```

### 5. Set up the Composio instance

No description provided.
```python
load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())
```

```typescript
dotenv.config();

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.USER_ID;

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});
```

### 6. Create a Tool Router session

What is happening:
- You give the Tool Router the user id and the toolkits you want available. Here, it is only reply.
- The router checks the user's Reply connection and prepares the MCP endpoint.
- The returned session.mcp.url is the MCP URL that your agent will use to access Reply.
- This approach keeps things lightweight and lets the agent request Reply tools only when needed during the conversation.
```python
# Create a Reply Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["reply"]
)

mcp_url = session.mcp.url
```

```typescript
// Create Tool Router session for Reply
const session = await composio.create(userId as string, {
  toolkits: ['reply'],
});
const mcpUrl = session.mcp.url;
```

### 7. Configure the agent

No description provided.
```python
# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Reply. "
        "Help users perform Reply operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)
```

```typescript
// Configure agent with MCP tool
const agent = new Agent({
  name: 'Assistant',
  model: 'gpt-5',
  instructions:
    'You are a helpful assistant that can access Reply. Help users perform Reply operations through natural language.',
  tools: [
    hostedMcpTool({
      serverLabel: 'tool_router',
      serverUrl: mcpUrl,
      headers: { 'x-api-key': composioApiKey },
      requireApproval: 'never',
    }),
  ],
});
```

### 8. Start chat loop and handle conversation

No description provided.
```python
print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
```

```typescript
// Keep conversation state across turns
const conversationSession = new OpenAIConversationsSession();

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

console.log('\nComposio Tool Router session created.');
console.log('\nChat started. Type your requests below.');
console.log("Commands: 'exit', 'quit', or 'q' to end\n");

try {
  const first = await run(agent, 'What can you help me with?', { session: conversationSession });
  console.log(`Assistant: ${first.finalOutput}\n`);
} catch (e) {
  console.error('Error:', e instanceof Error ? e.message : e, '\n');
}

rl.prompt();

rl.on('line', async (userInput) => {
  const text = userInput.trim();

  if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
    console.log('Goodbye!');
    rl.close();
    process.exit(0);
  }

  if (!text) {
    rl.prompt();
    return;
  }

  try {
    const result = await run(agent, text, { session: conversationSession });
    console.log(`\nAssistant: ${result.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();
});

rl.on('close', () => {
  console.log('\n👋 Session ended.');
  process.exit(0);
});
```

## Complete Code

```python
import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession

load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())

# Create Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["reply"]
)
mcp_url = session.mcp.url

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Reply. "
        "Help users perform Reply operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.USER_ID;

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});

async function main() {
  // Create Tool Router session
  const session = await composio.create(userId as string, {
    toolkits: ['reply'],
  });
  const mcpUrl = session.mcp.url;

  // Configure agent with MCP tool
  const agent = new Agent({
    name: 'Assistant',
    model: 'gpt-5',
    instructions:
      'You are a helpful assistant that can access Reply. Help users perform Reply operations through natural language.',
    tools: [
      hostedMcpTool({
        serverLabel: 'tool_router',
        serverUrl: mcpUrl,
        headers: { 'x-api-key': composioApiKey },
        requireApproval: 'never',
      }),
    ],
  });

  // Keep conversation state across turns
  const conversationSession = new OpenAIConversationsSession();

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

  console.log('\nComposio Tool Router session created.');
  console.log('\nChat started. Type your requests below.');
  console.log("Commands: 'exit', 'quit', or 'q' to end\n");

  try {
    const first = await run(agent, 'What can you help me with?', { session: conversationSession });
    console.log(`Assistant: ${first.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();

  rl.on('line', async (userInput) => {
    const text = userInput.trim();

    if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
      console.log('Goodbye!');
      rl.close();
      process.exit(0);
    }

    if (!text) {
      rl.prompt();
      return;
    }

    try {
      const result = await run(agent, text, { session: conversationSession });
      console.log(`\nAssistant: ${result.finalOutput}\n`);
    } catch (e) {
      console.error('Error:', e instanceof Error ? e.message : e, '\n');
    }

    rl.prompt();
  });

  rl.on('close', () => {
    console.log('\nSession ended.');
    process.exit(0);
  });
}

main().catch((err) => {
  console.error('Fatal error:', err);
  process.exit(1);
});
```

## Conclusion

This was a starter code for integrating Reply MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Reply.
Key features:
- Hosted MCP tool integration through Composio's Tool Router
- SQLite session persistence for conversation history
- Simple async chat loop for interactive testing
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

## How to build Reply MCP Agent with another framework

- [Claude Agent SDK](https://composio.dev/toolkits/reply/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/reply/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/reply/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/reply/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/reply/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/reply/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/reply/framework/cli)
- [Google ADK](https://composio.dev/toolkits/reply/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/reply/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/reply/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/reply/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/reply/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/reply/framework/crew-ai)

## Related Toolkits

- [Aeroleads](https://composio.dev/toolkits/aeroleads) - Aeroleads is a B2B lead generation platform for finding business emails and phone numbers. Grow your sales pipeline faster with powerful prospecting tools.
- [Autobound](https://composio.dev/toolkits/autobound) - Autobound is an AI-powered sales engagement platform that crafts hyper-personalized outreach and insights. It helps sales teams boost response rates and close more deals through tailored content and recommendations.
- [Better proposals](https://composio.dev/toolkits/better_proposals) - Better Proposals is a web-based tool for crafting and sending professional proposals. It helps teams impress clients and close deals faster with slick, easy-to-use templates.
- [Bidsketch](https://composio.dev/toolkits/bidsketch) - Bidsketch is a proposal software that helps businesses create professional proposals quickly and efficiently. It streamlines the proposal process, saving time while boosting client win rates.
- [Bolna](https://composio.dev/toolkits/bolna) - Bolna is an AI platform for building conversational voice agents. It helps businesses automate support and streamline interactions through natural, voice-powered conversations.
- [Botsonic](https://composio.dev/toolkits/botsonic) - Botsonic is a no-code AI chatbot builder for easily creating and deploying chatbots to your website. It empowers businesses to offer conversational experiences without writing code.
- [Botstar](https://composio.dev/toolkits/botstar) - BotStar is a comprehensive chatbot platform for designing, developing, and training chatbots visually on Messenger and websites. It helps businesses automate conversations and customer interactions without coding.
- [Callerapi](https://composio.dev/toolkits/callerapi) - CallerAPI is a white-label caller identification platform for branded caller ID and fraud prevention. It helps businesses boost customer trust while stopping spam, fraud, and robocalls.
- [Callingly](https://composio.dev/toolkits/callingly) - Callingly is a lead response management platform that automates immediate call and text follow-ups with new leads. It helps sales teams boost response speed and close more deals by connecting seamlessly with CRMs and lead sources.
- [Callpage](https://composio.dev/toolkits/callpage) - Callpage is a lead capture platform that lets businesses instantly connect with website visitors via callback. It boosts lead generation and increases your sales conversion rates.
- [Clearout](https://composio.dev/toolkits/clearout) - Clearout is an AI-powered service for verifying, finding, and enriching email addresses. It boosts deliverability and helps you discover high-quality leads effortlessly.
- [Clientary](https://composio.dev/toolkits/clientary) - Clientary is a platform for managing clients, invoices, projects, proposals, and more. It streamlines client work and saves you serious admin time.
- [Convolo ai](https://composio.dev/toolkits/convolo_ai) - Convolo ai is an AI-powered communications platform for sales teams. It accelerates lead response and improves conversion rates by automating calls and integrating workflows.
- [Delighted](https://composio.dev/toolkits/delighted) - Delighted is a customer feedback platform based on the Net Promoter System®. It helps you quickly gather, track, and act on customer sentiment.
- [Docsbot ai](https://composio.dev/toolkits/docsbot_ai) - Docsbot ai is a platform that lets you build custom AI chatbots trained on your documentation. It automates customer support and content generation, saving time and improving response quality.
- [Emelia](https://composio.dev/toolkits/emelia) - Emelia is an all-in-one B2B prospecting platform for cold-email, LinkedIn outreach, and prospect research. It streamlines outbound campaigns so you can find, engage, and warm up leads faster.
- [Findymail](https://composio.dev/toolkits/findymail) - Findymail is a B2B data provider offering verified email and phone contacts for sales prospecting. Enhance outreach with automated exports, email verification, and CRM enrichment.
- [Freshdesk](https://composio.dev/toolkits/freshdesk) - Freshdesk is customer support software with ticketing and automation tools. It helps teams streamline helpdesk operations for faster, better customer support.
- [Fullenrich](https://composio.dev/toolkits/fullenrich) - FullEnrich is a B2B contact enrichment platform that aggregates emails and phone numbers from 15+ data vendors. Instantly find and verify lead contact data to boost your outreach.
- [Gatherup](https://composio.dev/toolkits/gatherup) - GatherUp is a customer feedback and online review management platform. It helps businesses boost their reputation by streamlining how they collect and manage customer feedback.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Reply MCP?

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

### Can I use Tool Router MCP with OpenAI Agents SDK?

Yes, you can. OpenAI Agents 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 Reply tools.

### Can I manage the permissions and scopes for Reply while using Tool Router?

Yes, absolutely. You can configure which Reply 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.

### How safe is my data with Composio Tool Router?

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 Reply data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)