# How to integrate Reply io MCP with Vercel AI SDK v6 ```json { "title": "How to integrate Reply io MCP with Vercel AI SDK v6", "toolkit": "Reply io", "toolkit_slug": "reply_io", "framework": "Vercel AI SDK", "framework_slug": "ai-sdk", "url": "https://composio.dev/toolkits/reply_io/framework/ai-sdk", "markdown_url": "https://composio.dev/toolkits/reply_io/framework/ai-sdk.md", "updated_at": "2026-05-12T10:23:56.407Z" } ``` ## Introduction This guide walks you through connecting Reply io to Vercel AI SDK v6 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 Vercel AI SDK 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) - [Mastra AI](https://composio.dev/toolkits/reply_io/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/reply_io/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/reply_io/framework/crew-ai) ## TL;DR Here's what you'll learn: - How to set up and configure a Vercel AI SDK agent with Reply io integration - Using Composio's Tool Router to dynamically load and access Reply io tools - Creating an MCP client connection using HTTP transport - Building an interactive CLI chat interface with conversation history management - Handling tool calls and results within the Vercel AI SDK framework ## What is Vercel AI SDK? The Vercel AI SDK is a TypeScript library for building AI-powered applications. It provides tools for creating agents that can use external services and maintain conversation state. Key features include: - streamText: Core function for streaming responses with real-time tool support - MCP Client: Built-in support for Model Context Protocol via @ai-sdk/mcp - Step Counting: Control multi-step tool execution with stopWhen: stepCountIs() - OpenAI Provider: Native integration with OpenAI models ## 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 you begin, make sure you have: - Node.js and npm installed - A Composio account with API key - An OpenAI API key ### 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 required dependencies First, install the necessary packages for your project. What you're installing: - @ai-sdk/openai: Vercel AI SDK's OpenAI provider - @ai-sdk/mcp: MCP client for Vercel AI SDK - @composio/core: Composio SDK for tool integration - ai: Core Vercel AI SDK - dotenv: Environment variable management ```bash npm install @ai-sdk/openai @ai-sdk/mcp @composio/core ai dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's needed: - OPENAI_API_KEY: Your OpenAI API key for GPT model access - COMPOSIO_API_KEY: Your Composio API key for tool access - COMPOSIO_USER_ID: A unique identifier for the user session ```bash OPENAI_API_KEY=your_openai_api_key_here COMPOSIO_API_KEY=your_composio_api_key_here COMPOSIO_USER_ID=your_user_id_here ``` ### 4. Import required modules and validate environment What's happening: - We're importing all necessary libraries including Vercel AI SDK's OpenAI provider and Composio - The dotenv/config import automatically loads environment variables - The MCP client import enables connection to Composio's tool server ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Composio } from "@composio/core"; import * as readline from "readline"; import { streamText, type ModelMessage, stepCountIs } from "ai"; import { createMCPClient } from "@ai-sdk/mcp"; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set"); if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set"); if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set"); const composio = new Composio({ apiKey: composioAPIKey, }); ``` ### 5. Create Tool Router session and initialize MCP client What's happening: - We're creating a Tool Router session that gives your agent access to Reply io tools - The create method takes the user ID and specifies which toolkits should be available - The returned mcp object contains the URL and authentication headers needed to connect to the MCP server - This session provides access to all Reply io-related tools through the MCP protocol ```typescript async function main() { // Create a tool router session for the user const session = await composio.create(composioUserID!, { toolkits: ["reply_io"], }); const mcpUrl = session.mcp.url; ``` ### 6. Connect to MCP server and retrieve tools What's happening: - We're creating an MCP client that connects to our Composio Tool Router session via HTTP - The mcp.url provides the endpoint, and mcp.headers contains authentication credentials - The type: "http" is important - Composio requires HTTP transport - tools() retrieves all available Reply io tools that the agent can use ```typescript const mcpClient = await createMCPClient({ transport: { type: "http", url: mcpUrl, headers: session.mcp.headers, // Authentication headers for the Composio MCP server }, }); const tools = await mcpClient.tools(); ``` ### 7. Initialize conversation and CLI interface What's happening: - We initialize an empty messages array to maintain conversation history - A readline interface is created to accept user input from the command line - Instructions are displayed to guide the user on how to interact with the agent ```typescript let messages: ModelMessage[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log( "Ask any questions related to reply_io, like summarize my last 5 emails, send an email, etc... :)))\n", ); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); ``` ### 8. Handle user input and stream responses with real-time tool feedback What's happening: - We use streamText instead of generateText to stream responses in real-time - toolChoice: "auto" allows the model to decide when to use Reply io tools - stopWhen: stepCountIs(10) allows up to 10 steps for complex multi-tool operations - onStepFinish callback displays which tools are being used in real-time - We iterate through the text stream to create a typewriter effect as the agent responds - The complete response is added to conversation history to maintain context - Errors are caught and displayed with helpful retry suggestions ```typescript rl.on("line", async (userInput: string) => { const trimmedInput = userInput.trim(); if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) { console.log("\nGoodbye!"); rl.close(); process.exit(0); } if (!trimmedInput) { rl.prompt(); return; } messages.push({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); try { const stream = streamText({ model: openai("gpt-5"), messages, tools, toolChoice: "auto", stopWhen: stepCountIs(10), onStepFinish: (step) => { for (const toolCall of step.toolCalls) { console.log(`[Using tool: ${toolCall.toolName}]`); } if (step.toolCalls.length > 0) { console.log(""); // Add space after tool calls } }, }); for await (const chunk of stream.textStream) { process.stdout.write(chunk); } console.log("\n\n---\n"); // Get final result for message history const response = await stream.response; if (response?.messages?.length) { messages.push(...response.messages); } } catch (error) { console.error("\nAn error occurred while talking to the agent:"); console.error(error); console.log( "\nYou can try again or restart the app if it keeps happening.\n", ); } finally { rl.prompt(); } }); rl.on("close", async () => { await mcpClient.close(); console.log("\n👋 Session ended."); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Complete Code ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Composio } from "@composio/core"; import * as readline from "readline"; import { streamText, type ModelMessage, stepCountIs } from "ai"; import { createMCPClient } from "@ai-sdk/mcp"; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set"); if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set"); if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set"); const composio = new Composio({ apiKey: composioAPIKey, }); async function main() { // Create a tool router session for the user const session = await composio.create(composioUserID!, { toolkits: ["reply_io"], }); const mcpUrl = session.mcp.url; const mcpClient = await createMCPClient({ transport: { type: "http", url: mcpUrl, headers: session.mcp.headers, // Authentication headers for the Composio MCP server }, }); const tools = await mcpClient.tools(); let messages: ModelMessage[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log( "Ask any questions related to reply_io, like summarize my last 5 emails, send an email, etc... :)))\n", ); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); rl.on("line", async (userInput: string) => { const trimmedInput = userInput.trim(); if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) { console.log("\nGoodbye!"); rl.close(); process.exit(0); } if (!trimmedInput) { rl.prompt(); return; } messages.push({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); try { const stream = streamText({ model: openai("gpt-5"), messages, tools, toolChoice: "auto", stopWhen: stepCountIs(10), onStepFinish: (step) => { for (const toolCall of step.toolCalls) { console.log(`[Using tool: ${toolCall.toolName}]`); } if (step.toolCalls.length > 0) { console.log(""); // Add space after tool calls } }, }); for await (const chunk of stream.textStream) { process.stdout.write(chunk); } console.log("\n\n---\n"); // Get final result for message history const response = await stream.response; if (response?.messages?.length) { messages.push(...response.messages); } } catch (error) { console.error("\nAn error occurred while talking to the agent:"); console.error(error); console.log( "\nYou can try again or restart the app if it keeps happening.\n", ); } finally { rl.prompt(); } }); rl.on("close", async () => { await mcpClient.close(); console.log("\n👋 Session ended."); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Conclusion You've successfully built a Reply io agent using the Vercel AI SDK with streaming capabilities! This implementation provides a powerful foundation for building AI applications with natural language interfaces and real-time feedback. Key features of this implementation: - Real-time streaming responses for a better user experience with typewriter effect - Live tool execution feedback showing which tools are being used as the agent works - Dynamic tool loading through Composio's Tool Router with secure authentication - Multi-step tool execution with configurable step limits (up to 10 steps) - Comprehensive error handling for robust agent execution - Conversation history maintenance for context-aware responses You can extend this further by adding custom error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows. ## 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) - [Mastra AI](https://composio.dev/toolkits/reply_io/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/reply_io/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/reply_io/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. - [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. - [Getprospect](https://composio.dev/toolkits/getprospect) - Getprospect is a business email discovery tool with LinkedIn integration. Use it to quickly find and verify professional email addresses. ## 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 Vercel AI SDK v6? Yes, you can. Vercel AI SDK v6 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)