# How to integrate Reply io MCP with CrewAI

```json
{
  "title": "How to integrate Reply io MCP with CrewAI",
  "toolkit": "Reply io",
  "toolkit_slug": "reply_io",
  "framework": "CrewAI",
  "framework_slug": "crew-ai",
  "url": "https://composio.dev/toolkits/reply_io/framework/crew-ai",
  "markdown_url": "https://composio.dev/toolkits/reply_io/framework/crew-ai.md",
  "updated_at": "2026-05-12T10:23:56.407Z"
}
```

## Introduction

This guide walks you through connecting Reply io to CrewAI using the Composio tool router. By the end, you'll have a working Reply io agent that can list all active campaigns this week, show contacts added to sales lists, delete a campaign by campaign id through natural language commands.
This guide will help you understand how to give your CrewAI agent real control over a Reply io account through Composio's Reply io MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Reply io with

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

## TL;DR

Here's what you'll learn:
- Get a Composio API key and configure your Reply io connection
- Set up CrewAI with an MCP enabled agent
- Create a Tool Router session or standalone MCP server for Reply io
- Build a conversational loop where your agent can execute Reply io operations

## What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.
Key features include:
- Agent Roles: Define specialized agents with specific goals and backstories
- Task Management: Create tasks with clear descriptions and expected outputs
- Crew Orchestration: Combine agents and tasks into collaborative workflows
- MCP Integration: Connect to external tools through Model Context Protocol

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

The Reply io 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 manage campaigns, handle contacts, organize sequences, and automate routine sales operations on your behalf.
- Campaign and sequence management: Effortlessly list, browse, and delete campaigns or sequences to keep your outreach organized and up to date.
- Contact and list organization: Let your agent fetch, review, and organize your Reply io contacts and contact lists for targeted sales actions.
- Email account administration: Retrieve all connected email accounts or remove outdated ones, making sure your sales tools stay streamlined.
- User and access control: Easily remove users or generate unique identifiers for tasks, maintaining security and clarity in your team’s workflow.
- Automated data retrieval: Quickly pull up paginated lists of campaigns, sequences, email accounts, or contact lists to inform your sales strategies and next steps.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `REPLY_IO_ADD_CONTACT_TO_SEQUENCE` | Add Contact to Sequence | Move an existing contact to a sequence in Reply.io. Use this action to enroll contacts in email sequences for automated outreach campaigns. This action allows you to specify where in the sequence to start, whether to remove the contact from their current sequence, and when to begin processing. |
| `REPLY_IO_ARCHIVE_SEQUENCE` | Archive Sequence | Tool to archive a sequence. Use when you need to archive an existing sequence without permanently deleting it. |
| `REPLY_IO_CLEAR_CONTACT_STATUS` | Clear Contact Status | Tool to clear statuses from contacts. Use when you need to remove specific or all clearable statuses from contacts. |
| `REPLY_IO_CONNECT_EXCHANGE_ACCOUNT` | Connect Exchange Account via OAuth | Tool to initiate OAuth connection for an Exchange email account. Use when you need to connect an Exchange account to Reply.io via OAuth flow. Returns the Microsoft OAuth consent page URL where the user should be redirected. |
| `REPLY_IO_CONNECT_GMAIL_ACCOUNT` | Connect Gmail Account | Tool to initiate Gmail account connection via OAuth. Returns the OAuth authorization URL where the user should be redirected to grant permissions. |
| `REPLY_IO_CREATE_CONTACT` | Create Contact | Tool to create a new contact in Reply.io. Use when adding contacts to your outreach database. |
| `REPLY_IO_CREATE_SEQUENCE_STEP` | Create Sequence Step | Tool to add a new step to an existing sequence. Use when you need to build or modify sequence workflows with Email, Call, Task, SMS, WhatsApp, LinkedIn, Condition, or Zapier steps. |
| `REPLY_IO_DELETE_CONTACT` | Delete Contact | Tool to delete a contact. Use after confirming the contact exists to remove it permanently. |
| `REPLY_IO_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_IO_DELETE_SCHEDULE` | Delete Schedule | Tool to delete a schedule. Use after confirming the schedule exists to remove it permanently. |
| `REPLY_IO_DELETE_SEQUENCE` | Delete Sequence | Tool to delete a sequence. Use after confirming the sequence exists to remove it permanently. |
| `REPLY_IO_DELETE_USER` | Delete User | Tool to delete a user. Use after confirming the user exists to remove them permanently. |
| `REPLY_IO_GENERATE_ULID` | Generate ULID | Generate ULID |
| `REPLY_IO_GET_CONTACT_BY_ID` | Get Contact by ID | Tool to retrieve a contact by ID. Use when you have a contact ID and need detailed contact information. |
| `REPLY_IO_GET_CONTACT_STATUS` | Get Contact Status | Tool to get contact status. Use when you need to retrieve all current statuses for a contact. |
| `REPLY_IO_GET_CURRENT_USER` | Get Current User | Tool to get the current authenticated user's ID. Use when you need to verify API key validity or identify the current user. |
| `REPLY_IO_GET_DISCONNECTED_EMAIL_ACCOUNTS` | Reply.io Get Disconnected Email Accounts | Tool to list email accounts that are currently disconnected due to authentication or connection errors. Use when you need to identify and troubleshoot problematic email accounts. |
| `REPLY_IO_GET_SEQUENCE_BY_ID` | Get Sequence By ID | Tool to retrieve detailed information about a sequence by its ID. Use when you need to get comprehensive sequence details including settings, email accounts, and workflow steps. |
| `REPLY_IO_GET_SEQUENCE_CONTACTS_EXTENDED` | Get Sequence Contacts Extended | Tool to retrieve all contacts enrolled in a sequence with additional details. Use when you need to see contact engagement status, current step, or completion timestamps within a sequence. |
| `REPLY_IO_GET_SEQUENCE_STEP_BY_ID` | Get Sequence Step by ID | Tool to retrieve details of a specific sequence step. Use when you need to inspect step configuration including type, delays, execution mode, and type-specific settings. |
| `REPLY_IO_LIST_CONTACTS_BASIC` | List Contacts Basic | Tool to list contacts. Use when verifying API access and gathering contact IDs. |
| `REPLY_IO_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_IO_LIST_LISTS` | Reply.io List Lists | Tool to list all contact lists. Use when you need to retrieve all available lists in your Reply.io account. |
| `REPLY_IO_LIST_SEQUENCES` | List Sequences | Tool to retrieve a paginated list of sequences. Use when you need to browse sequences with optional filtering by name. |
| `REPLY_IO_LIST_SEQUENCE_STEPS` | List Sequence Steps | Tool to retrieve all steps in a sequence. Use when you need to get the complete list of steps configured for a specific sequence. |
| `REPLY_IO_PAUSE_SEQUENCE` | Pause Sequence | Tool to pause a running sequence. Use when you need to temporarily stop a sequence from sending emails or executing steps. |
| `REPLY_IO_REMOVE_CONTACT_FROM_SEQUENCE` | Remove Contact From Sequence | Tool to remove a contact from a sequence. Use when you need to stop a contact from receiving further steps in a specific sequence. |
| `REPLY_IO_REMOVE_CONTACTS_FROM_SEQUENCE` | Bulk Remove Contacts from Sequence | Tool to bulk remove multiple contacts from a sequence at once. Use when you need to remove several contacts from a sequence efficiently in a single operation. |
| `REPLY_IO_SEARCH_CONTACTS` | Search Contacts by Email | Tool to search contacts by email. Use when you need to find existing contact IDs for update tests. |
| `REPLY_IO_SET_CONTACT_STATUS` | Set Contact Status | Tool to set the status of one or more contacts. Use when you need to update contact statuses in bulk. |
| `REPLY_IO_START_SEQUENCE` | Start Sequence | Tool to start a sequence. Use when you need to activate a sequence that is in New or Paused status. |
| `REPLY_IO_UPDATE_CONTACT` | Update Contact | Tool to update an existing contact's information. Use when you need to modify contact details. |
| `REPLY_IO_UPDATE_EMAIL_ACCOUNT` | Update Email Account | Tool to update an existing email account with custom SMTP/IMAP settings. Use when you need to modify email account configuration such as sender name, signature, server settings, or daily limits. |

## Supported Triggers

None listed.

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

The Reply io MCP server is an implementation of the Model Context Protocol that connects your AI agent to Reply io. It provides structured and secure access so your agent can perform Reply io 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:
- Python 3.9 or higher
- A Composio account and API key
- A Reply io connection authorized in Composio
- An OpenAI API key for the CrewAI LLM
- Basic familiarity with Python

### 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).
- Navigate to your API settings and generate a new API key.
- Store this key securely as you'll need it for authentication.

### 2. Install dependencies

**What's happening:**
- composio connects your agent to Reply io via MCP
- crewai provides Agent, Task, Crew, and LLM primitives
- crewai-tools[mcp] includes MCP helpers
- python-dotenv loads environment variables from .env
```bash
pip install composio crewai crewai-tools[mcp] python-dotenv
```

### 3. Set up environment variables

Create a .env file in your project root.
What's happening:
- COMPOSIO_API_KEY authenticates with Composio
- USER_ID scopes the session to your account
- OPENAI_API_KEY lets CrewAI use your chosen OpenAI model
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here
```

### 4. Import dependencies

**What's happening:**
- CrewAI classes define agents and tasks, and run the workflow
- MCPServerHTTP connects the agent to an MCP endpoint
- Composio will give you a short lived Reply io MCP URL
```python
import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")
```

### 5. Create a Composio Tool Router session for Reply io

**What's happening:**
- You create a Reply io only session through Composio
- Composio returns an MCP HTTP URL that exposes Reply io tools
```python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["reply_io"])

url = session.mcp.url
```

### 6. Initialize the MCP Server

**What's Happening:**
- Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
- MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
- Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
- Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
- Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.
```python
server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )
```

### 7. Create a CLI Chatloop and define the Crew

**What's Happening:**
- Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
- Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
- Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
- Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
- Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
- Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.
```python
print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
```

## Complete Code

```python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["reply_io"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")
```

## Conclusion

You now have a CrewAI agent connected to Reply io through Composio's Tool Router. The agent can perform Reply io operations through natural language commands.
Next steps:
- Add role-specific instructions to customize agent behavior
- Plug in more toolkits for multi-app workflows
- Chain tasks for complex multi-step operations

## How to build Reply io MCP Agent with another framework

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

## 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 io MCP?

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

### Can I use Tool Router MCP with CrewAI?

Yes, you can. CrewAI 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 io tools.

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

Yes, absolutely. You can configure which Reply io 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 io data and credentials are handled as safely as possible.

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