# How to integrate Bolna MCP with Vercel AI SDK v6 ```json { "title": "How to integrate Bolna MCP with Vercel AI SDK v6", "toolkit": "Bolna", "toolkit_slug": "bolna", "framework": "Vercel AI SDK", "framework_slug": "ai-sdk", "url": "https://composio.dev/toolkits/bolna/framework/ai-sdk", "markdown_url": "https://composio.dev/toolkits/bolna/framework/ai-sdk.md", "updated_at": "2026-05-12T10:03:27.760Z" } ``` ## Introduction This guide walks you through connecting Bolna to Vercel AI SDK v6 using the Composio tool router. By the end, you'll have a working Bolna agent that can list all voice agents available to me, initiate a call using your sales agent, get status of recent agent executions through natural language commands. This guide will help you understand how to give your Vercel AI SDK agent real control over a Bolna account through Composio's Bolna MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Bolna with - [OpenAI Agents SDK](https://composio.dev/toolkits/bolna/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/bolna/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/bolna/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/bolna/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/bolna/framework/codex) - [OpenClaw](https://composio.dev/toolkits/bolna/framework/openclaw) - [Hermes](https://composio.dev/toolkits/bolna/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/bolna/framework/cli) - [Google ADK](https://composio.dev/toolkits/bolna/framework/google-adk) - [LangChain](https://composio.dev/toolkits/bolna/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/bolna/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/bolna/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/bolna/framework/crew-ai) ## TL;DR Here's what you'll learn: - How to set up and configure a Vercel AI SDK agent with Bolna integration - Using Composio's Tool Router to dynamically load and access Bolna 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 Bolna MCP server, and what's possible with it? The Bolna MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Bolna account. It provides structured and secure access to your Bolna voice agent platform, so your agent can perform actions like listing agents, making phone calls, managing executions, and retrieving analytics on your behalf. - Automated voice call initiation: Let your AI agent instantly initiate phone calls using your Bolna conversational agents, streamlining outreach and support tasks. - Agent and phone number management: Effortlessly fetch and list all your Bolna agents or phone numbers, making it easy to review and organize your voice assets. - Real-time execution monitoring: Retrieve detailed information about specific call executions or monitor all executions for a given agent to track performance and outcomes. - Batch processing for agents: List and manage batch operations associated with your agents, supporting bulk workflows and campaign management. - Agent cleanup and maintenance: Quickly delete agents or batches that are no longer needed, keeping your Bolna environment organized and up to date. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `BOLNA_ADD_PROVIDER` | Add Provider to Bolna | Tool to add a new telephony or voice service provider to your Bolna account. Use when you need to configure API keys for providers like Twilio, Deepgram, or ElevenLabs before creating agents. | | `BOLNA_COPY_AGENT` | Copy Bolna Agent | Tool to create a duplicate copy of an existing Bolna voice AI agent. Use when you need to replicate an agent's complete configuration (tasks, prompts, LLM settings, etc.) with a new name. | | `BOLNA_CREATE_AGENT` | Create Bolna Voice AI Agent (v2) | Tool to create a new Bolna Voice AI agent using the v2 API. Use when you need to set up a new conversational agent from scratch with custom LLM, synthesizer, transcriber, and task configurations. This fills the gap for end-to-end agent setup in workflows starting from an empty account state. | | `BOLNA_CREATE_BATCH` | Create Bolna Batch | Tool to create a new outbound calling batch by uploading a CSV of contacts to obtain a batch_id. Use when initiating a batch campaign; follow by calling BOLNA_SCHEDULE_BATCH_BY_ID to schedule execution. | | `BOLNA_CREATE_KNOWLEDGEBASE` | Create Bolna Knowledgebase | Tool to create a new knowledgebase for Voice AI agents to reference during conversations. Use when you need to provide agents with domain-specific knowledge from PDFs or web URLs. Note: Initially returns status 'processing'; poll or wait for status to become 'processed' before use. | | `BOLNA_CREATE_TEMPLATE_AGENT` | Create Template Agent | Tool to create a new Bolna Voice AI agent from a template. Use when you want to quickly set up an agent using predefined templates instead of building from scratch. | | `BOLNA_DELETE_AGENT_BY_ID` | Delete agent by id | Permanently delete a Voice AI agent and all associated data including batches, executions, and configurations | | `BOLNA_DELETE_BATCH_BY_ID` | Delete batch by id | Permanently delete a batch campaign by its ID, removing it from the system. This operation cannot be undone. | | `BOLNA_DELETE_KNOWLEDGEBASE` | Delete Knowledgebase | Tool to permanently delete a knowledgebase from your Bolna account. Use when you need to remove an existing RAG knowledgebase that is no longer needed. This operation cannot be undone. | | `BOLNA_FETCH_ALL_BATCHES_BY_AGENT_ID` | Fetch all batches by agent id | Retrieve all batches associated with a specific Bolna Voice AI agent. Returns a comprehensive list of batches with details including batch status (scheduled, created, queued, executed), creation and scheduled times, contact counts, file names, and execution status breakdown. Use this to monitor batch campaigns, track their progress, and manage outbound calling operations for the agent. | | `BOLNA_GET_ALL_AGENTS` | Get all agents | Retrieve all agents configured in your Bolna account Returns a comprehensive list of all voice agents with their configurations including: - Agent metadata (ID, name, type, status) - Task configurations (conversation settings, toolchains) - AI model settings (LLM, transcriber, synthesizer) - Webhook and phone number assignments - System prompts and guardrails This is useful for listing available agents, checking agent configurations, or finding specific agents by their properties. | | `BOLNA_GET_EXECUTION_BY_ID` | Get execution by id | Retrieve detailed information about a specific phone call execution by its ID. Returns comprehensive execution data including conversation transcript, duration, costs (LLM, TTS, STT, network, platform), telephony details (phone numbers, recording URL, provider info), usage metrics (tokens, characters, duration), and extracted structured data. Use this to: - Analyze individual call performance and outcomes - Access conversation transcripts and recordings - Review cost breakdowns and resource usage - Monitor call status and error messages - Retrieve extracted structured data from conversations | | `BOLNA_GET_KNOWLEDGEBASE` | Get knowledgebase by ID | Tool to retrieve details of a specific knowledgebase by its ID. Returns complete configuration including processing status, file information, vector ID, and embedding parameters (chunk size, similarity top k, overlapping). Use when you need to check if a knowledgebase has finished processing or to inspect its configuration before using it with an agent. | | `BOLNA_GET_USER_INFO` | Get User Information | Tool to retrieve information about the authenticated user. Use when you need details like name, email, wallet balance, or concurrency limits for the current user. | | `BOLNA_IMPORT_AGENT` | Import Bolna Agent | Tool to import an existing Bolna voice AI agent by its ID. Use when you need to copy or duplicate an agent configuration, create a new agent from a template, or migrate an agent from another environment. | | `BOLNA_LIST_AGENTS_PAGINATED` | List agents (paginated) | Tool to retrieve a paginated list of all agents in your Bolna account. Use when you need to fetch agents with optional filtering by user_id or sub_account_id. | | `BOLNA_LIST_KNOWLEDGEBASES` | List Knowledgebases | Tool to retrieve all knowledgebases from your Bolna account. Use when you need to view available RAG knowledgebases, check their processing status, or find specific knowledgebases by status. | | `BOLNA_LIST_PHONE_NUMBERS` | List all phone numbers | Tool to list all phone numbers associated with your Bolna account. Use when you need to retrieve details of all phone numbers including provider, associated agent, pricing, and rental status. | | `BOLNA_LIST_PROVIDERS` | List all providers | Retrieve all providers associated with your Bolna account Returns a list of all configured providers including: - Provider IDs (unique identifiers) - Provider names (e.g., API key types) - Masked provider values (secrets) - Creation timestamps (both absolute and human-readable) Use this when you need to view all configured API providers, check provider details, or verify provider setup in your Bolna account. | | `BOLNA_LIST_VOICES` | List available voices | Tool to list all available voices that can be utilized for Voice AI agents. Use when you need to see which voices are available across different providers. | | `BOLNA_MAKE_A_PHONE_CALL_FROM_AGENT` | Make an outbound phone call from agent | Initiate an outbound phone call using a configured Bolna Voice AI agent. The agent will call the specified recipient and engage in a conversation based on its configured prompt and capabilities. | | `BOLNA_REMOVE_PROVIDER` | Remove Provider from Bolna Account | Tool to remove a provider from your Bolna account by its key name. Use when you need to delete a provider configuration that is no longer needed or needs to be replaced. | | `BOLNA_RETRIEVE_AGENT_BY_ID` | Retrieve agent by id | Retrieve complete configuration and details for a specific Bolna voice AI agent by its ID. Returns comprehensive agent information including name, type, status, conversation tasks, LLM/synthesizer/transcriber settings, system prompts, webhook configuration, and timestamps. Use this to inspect agent setup before making calls or to verify agent configuration. | | `BOLNA_RETRIEVE_AGENT_EXECUTION_DETAILS` | Retrieve agent execution details | Retrieve detailed information about a specific execution (call/conversation) by an agent, including transcript, costs, duration, status, and telephony data | | `BOLNA_RETRIEVE_AGENT_EXECUTION_STATUS` | Retrieve agent execution status | Retrieve all executions for a specific agent with pagination and filtering support. Returns a paginated list of agent execution records including call status, cost breakdown, transcripts, and telephony data. | | `BOLNA_RETRIEVE_BATCH_DETAILS_BY_ID` | Retrieve Batch Details by ID | Retrieve comprehensive details about a specific Bolna batch by its ID. Returns batch metadata including creation time, execution status, scheduled time, contact statistics, and call status breakdown. Use this to monitor batch progress or retrieve information about previously created batch calling campaigns. | | `BOLNA_RETRIEVE_BATCH_EXECUTION_LIST` | Retrieve batch execution list | Retrieve all executions from a specific batch with pagination support. Returns detailed information about each call execution including conversation metrics, transcripts, costs, and resource usage breakdown (LLM tokens, synthesizer characters, etc.). Use this to monitor batch campaign results and analyze individual call outcomes. | | `BOLNA_SCHEDULE_BATCH_BY_ID` | Schedule Batch by ID | Schedule a batch to execute at a specific time. After creating a batch with BOLNA_CREATE_BATCH, use this action to set when the batch calls should begin. The batch must exist and be in a schedulable state (e.g., 'created' or 'stopped'). | | `BOLNA_SEARCH_PHONE_NUMBERS` | Search available phone numbers | Tool to search for available phone numbers that can be purchased for Bolna Voice agents. Use when you need to find purchasable phone numbers by country or prefix pattern before buying. | | `BOLNA_SETUP_INBOUND_CALL_FOR_AGENT` | Setup inbound call for agent | Add agent for inbound calls | | `BOLNA_STOP_AGENT_CALLS` | Stop Agent Calls | Tool to stop all queued or scheduled calls for a specific Voice AI agent. Use when you need to immediately halt all pending calls for an agent. | | `BOLNA_STOP_BATCH_BY_ID` | Stop batch by id | Stop a running batch by its ID. This halts all queued calls in the batch. Any calls currently in the queue waiting to be executed will be cancelled and will not be processed. Use this when you need to immediately halt a batch campaign that's in progress. | | `BOLNA_UPDATE_AGENT` | Update Bolna Voice AI Agent (v2) | Tool to update all settings and configuration of an existing Bolna Voice AI agent using the v2 API. Use when you need to modify an agent's full configuration including LLM settings, synthesizer, transcriber, tasks, prompts, or any other agent property. This performs a complete update (PUT operation). | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Bolna MCP server is an implementation of the Model Context Protocol that connects your AI agent to Bolna. It provides structured and secure access so your agent can perform Bolna 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 Bolna 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 Bolna-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: ["bolna"], }); 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 Bolna 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 bolna, 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 Bolna 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: ["bolna"], }); 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 bolna, 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 Bolna 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 Bolna MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/bolna/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/bolna/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/bolna/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/bolna/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/bolna/framework/codex) - [OpenClaw](https://composio.dev/toolkits/bolna/framework/openclaw) - [Hermes](https://composio.dev/toolkits/bolna/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/bolna/framework/cli) - [Google ADK](https://composio.dev/toolkits/bolna/framework/google-adk) - [LangChain](https://composio.dev/toolkits/bolna/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/bolna/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/bolna/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/bolna/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. - [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. - [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 Bolna MCP? With a standalone Bolna MCP server, the agents and LLMs can only access a fixed set of Bolna tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Bolna 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 Bolna tools. ### Can I manage the permissions and scopes for Bolna while using Tool Router? Yes, absolutely. You can configure which Bolna 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 Bolna data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)