# How to integrate Vapi MCP with CrewAI ```json { "title": "How to integrate Vapi MCP with CrewAI", "toolkit": "Vapi", "toolkit_slug": "vapi", "framework": "CrewAI", "framework_slug": "crew-ai", "url": "https://composio.dev/toolkits/vapi/framework/crew-ai", "markdown_url": "https://composio.dev/toolkits/vapi/framework/crew-ai.md", "updated_at": "2026-10-12T14:17:21.817Z" } ``` ## Introduction This guide walks you through connecting Vapi to CrewAI using the Composio tool router. By the end, you'll have a working Vapi agent that can start a new outbound call campaign, get transcript from the last agent call, pause all ongoing voice agent sessions through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Vapi account through Composio's Vapi MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Vapi with - [Claude Code](https://composio.dev/toolkits/vapi/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/vapi/framework/claude-cowork) - [OpenAI Agents SDK](https://composio.dev/toolkits/vapi/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/vapi/framework/claude-agents-sdk) - [Codex](https://composio.dev/toolkits/vapi/framework/codex) - [OpenClaw](https://composio.dev/toolkits/vapi/framework/openclaw) - [Hermes](https://composio.dev/toolkits/vapi/framework/hermes-agent) - [Atomic Agent](https://composio.dev/toolkits/vapi/framework/atomic-agent) - [Google ADK](https://composio.dev/toolkits/vapi/framework/google-adk) - [LangChain](https://composio.dev/toolkits/vapi/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/vapi/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/vapi/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/vapi/framework/llama-index) - [Pydantic AI](https://composio.dev/toolkits/vapi/framework/pydantic-ai) - [AutoGen](https://composio.dev/toolkits/vapi/framework/autogen) ## TL;DR Here's what you'll learn: - Get a Composio API key and configure your Vapi connection - Set up CrewAI with an MCP enabled agent - Create a Tool Router session or standalone MCP server for Vapi - Build a conversational loop where your agent can execute Vapi 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 Vapi MCP server, and what's possible with it? The Vapi MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Vapi account. It provides structured and secure access to your voice assistants, calls, chats, phone numbers, and analytics, so your agent can create assistants, review conversations, analyze performance, manage phone numbers, and configure monitoring on your behalf. - Voice assistant configuration: Have your agent create new voice assistants with selected transcribers, voices, and AI models, or update existing assistant settings. - Call and chat review: Let the agent list calls and chats, then retrieve the details needed to examine specific conversations. - Analytics and quality evaluation: Direct your agent to run analytics queries, review evaluations, and remove evaluations you no longer need. - Phone number management: Instruct your agent to list, update, or delete phone numbers connected to your Vapi organization. - Monitoring and supporting resources: Have your agent create and review monitoring policies, retrieve stored files, inspect available tools and provider resources, or create new sessions. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `VAPI_ASSISTANT_CONTROLLER_UPDATE` | Update Assistant | Tool to update an existing Vapi assistant configuration. Use when you need to modify assistant properties such as name, voice settings, transcriber configuration, model settings, messages, or other behavior parameters. Only include fields you want to update. | | `VAPI_CALL_CONTROLLER_FIND_ALL` | List Calls | Tool to list calls from Vapi. Use when you need to retrieve multiple calls with optional filtering by id, assistantId, phoneNumberId, or date ranges. Returns an array of call objects with details including status, costs, messages, and artifacts. | | `VAPI_CHAT_CONTROLLER_DELETE_CHAT` | Delete Chat | Tool to delete a chat by its ID from Vapi. Use when you need to permanently remove a chat conversation. | | `VAPI_CHAT_CONTROLLER_GET_CHAT` | Get Chat | Tool to fetch chat details by ID. Use when you have a chat ID and need full chat information including messages, costs, and configuration. | | `VAPI_CREATE_ANALYTICS_QUERY` | Create Analytics Queries | Tool to create and execute analytics queries on VAPI data. Use when you need to analyze call or subscription metrics with aggregations like count, sum, average, min, or max. Supports grouping by various dimensions and time-based analysis with custom time ranges. | | `VAPI_CREATE_ASSISTANT` | Create Assistant | Tool to create a new Vapi assistant with specified transcriber, voice, and AI model configurations. Use when setting up a conversational AI assistant for voice interactions. The assistant requires transcription (speech-to-text), voice (text-to-speech), and AI model (conversation logic) configurations at minimum. | | `VAPI_CREATE_EVAL` | Create Eval | Tool to create an eval for testing conversation flows. Use when you need to validate that an AI assistant responds correctly to specific conversation scenarios. | | `VAPI_CREATE_OPEN_AI_CHAT` | Create OpenAI Chat | Tool to create an OpenAI-compatible chat using the Vapi API. Use when you need to send a chat message to an assistant or squad and receive a response. Supports both streaming and non-streaming modes. | | `VAPI_CREATE_POLICY` | Create Monitoring Policy | Tool to create a monitoring policy in VAPI. Use when you need to set up automated monitoring rules based on thresholds and time windows. Policies can trigger alerts based on event counts or percentages over a specified lookback window. | | `VAPI_CREATE_PROVIDER_RESOURCE` | Create Provider Resource | Tool to create an 11Labs pronunciation dictionary resource. Use when you need to define custom pronunciations for specific terms or acronyms in voice synthesis. | | `VAPI_CREATE_SCORECARD` | Create Scorecard | Tool to create a scorecard for observability and evaluation. Use when setting up metrics to evaluate assistant performance based on structured outputs. Scorecards contain metrics with conditions that calculate normalized scores on a 100-point scale. | | `VAPI_DELETE_CALL` | Delete Call | Tool to delete a call by its unique identifier. Use when you need to remove call data from the system. Returns the deleted call object with all its associated data. | | `VAPI_DELETE_EVAL` | Delete Eval | Tool to delete an eval by ID. Use when you need to permanently remove an eval from the system. | | `VAPI_DELETE_PHONE_NUMBER` | Delete Phone Number | Tool to delete a phone number from Vapi. Use when you need to remove a phone number from your Vapi organization. Returns the deleted phone number object. | | `VAPI_EVAL_CONTROLLER_GET` | Get Eval | Tool to retrieve an eval by its ID. Use when you need to fetch details about a specific eval including its mock conversation messages and metadata. | | `VAPI_EVAL_CONTROLLER_REMOVE_RUN` | Delete Eval Run | Tool to delete an eval run by its ID from Vapi. Use when you need to permanently remove an evaluation run. | | `VAPI_EVAL_CONTROLLER_UPDATE` | Update Eval | Tool to update an existing eval in Vapi. Use when you need to modify eval properties like name, description, type, or mock conversation messages. | | `VAPI_GET_ASSISTANT` | Get Assistant | Tool to retrieve a specific assistant by ID from Vapi. Use when you need to fetch details about an existing assistant. | | `VAPI_GET_CALL` | Get Call | Tool to fetch call details by ID. Use when you have a call ID and need full call information including status, duration, costs, messages, and recordings. | | `VAPI_GET_FILE` | Get File | Tool to retrieve a file by its ID from Vapi. Use when you need to get details about a specific file including its status, metadata, storage location, and timestamps. | | `VAPI_GET_MONITORING` | List Monitoring Policies | Tool to retrieve monitoring policies from Vapi. Use when you need to list, filter, or search for monitoring policies configured in the organization. Supports filtering by policy ID, severity level, monitor ID, and date ranges for creation/update timestamps. | | `VAPI_GET_STRUCTURED_OUTPUTS` | List Structured Outputs | Tool to list structured outputs with optional filtering. Use when you need to retrieve structured output configurations with pagination support. Supports filtering by ID, name, timestamps, and includes pagination controls. | | `VAPI_INSIGHT_CONTROLLER_FIND_ALL` | Get Insights | Tool to retrieve insights from VAPI. Use when you need to list insights with optional filtering by ID, creation date, or update date. Supports pagination and sorting. | | `VAPI_LIST_ASSISTANTS` | List Assistants | Tool to list all assistants in your VAPI organization. Use when you need to retrieve information about configured assistants. Supports filtering by creation and update timestamps. | | `VAPI_LIST_CHATS` | List Chats | Tool to retrieve a list of chat conversations from VAPI. Use when you need to view existing chats, optionally filtered by assistant, squad, session, or time range. Supports pagination and sorting for efficient retrieval of large chat histories. | | `VAPI_LIST_EVALS` | List Evals | Tool to retrieve a paginated list of evals from Vapi. Use when you need to list or search evals with optional filtering by creation/update timestamps. | | `VAPI_LIST_PHONE_NUMBERS` | List Phone Numbers | Tool to list phone numbers in the Vapi organization. Use when you need to enumerate available phone numbers for routing or selection workflows. Supports filtering by creation and update timestamps. | | `VAPI_LIST_PROVIDER_RESOURCES` | List Provider Resources | Tool to retrieve provider resources from Vapi (e.g., 11labs pronunciation dictionaries). Use when you need to list or search provider-specific resources with optional filtering by timestamps. | | `VAPI_PATCH_INSIGHT_INSIGHT` | Update Insight | Tool to update an existing insight configuration in VAPI. Use when you need to modify insight properties like name, queries, time range, or visualization settings. Supports all four insight types (bar, pie, line, text) with type-specific configurations. | | `VAPI_PHONE_NUMBER_CONTROLLER_CREATE` | Create Phone Number | Tool to create a phone number with VAPI. Use when you need to provision a new phone number for voice AI applications. Supports multiple providers (VAPI, Twilio, Vonage, Telnyx, BYO). Required parameters vary by provider. | | `VAPI_SCORECARD_CONTROLLER_GET_PAGINATED` | List Scorecards | Tool to retrieve a paginated list of scorecards from Vapi. Use when you need to list or search scorecards with optional filtering by creation/update timestamps. | | `VAPI_SESSION_CONTROLLER_CREATE` | Create Session | Tool to create a new session in Vapi. Use when you need to establish a persistent conversation context that can span multiple chats. Sessions automatically expire after 24 hours. | | `VAPI_SESSION_CONTROLLER_FIND_ALL_PAGINATED` | List Sessions | Tool to retrieve a paginated list of sessions from VAPI. Use when you need to list sessions with optional filtering by session ID, name, assistant, squad, or workflow. Supports pagination, sorting, and timestamp-based filtering. | | `VAPI_TOOL_CONTROLLER_FIND_ONE` | Get Tool | Tool to fetch tool details by ID. Use when you have a tool ID and need full tool configuration including type, messages, function definitions, and server settings. | | `VAPI_TOOL_CONTROLLER_TEST_CODE_EXECUTION` | Test Code Tool Execution | Tool to test TypeScript code execution in Vapi's code tool environment. Use when validating code before deploying it as a tool. | | `VAPI_TOOL_CONTROLLER_UPDATE` | Update Tool | Tool to update an existing Vapi tool configuration. Use when you need to modify tool properties such as function definitions, server settings, messages, or other tool-specific parameters. | | `VAPI_UPDATE_PHONE_NUMBER` | Update Phone Number | Tool to update an existing phone number configuration in VAPI. Use when you need to modify phone number settings such as name, associated assistant/workflow, or provider-specific configurations. | | `VAPI_UPLOAD_FILE` | Upload File | Tool to upload a file to Vapi Knowledge Base. Use when you need to add files for AI assistants to reference. Returns file metadata including ID, storage URLs, and processing status. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Vapi MCP server is an implementation of the Model Context Protocol that connects your AI agent to Vapi. It provides structured and secure access so your agent can perform Vapi 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 Vapi 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 Vapi 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 Vapi 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 Vapi **What's happening:** - You create a Vapi only session through Composio - Composio returns an MCP HTTP URL that exposes Vapi tools ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["vapi"]) 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=["vapi"], ) 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 Vapi through Composio's Tool Router. The agent can perform Vapi 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 Vapi MCP Agent with another framework - [Claude Code](https://composio.dev/toolkits/vapi/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/vapi/framework/claude-cowork) - [OpenAI Agents SDK](https://composio.dev/toolkits/vapi/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/vapi/framework/claude-agents-sdk) - [Codex](https://composio.dev/toolkits/vapi/framework/codex) - [OpenClaw](https://composio.dev/toolkits/vapi/framework/openclaw) - [Hermes](https://composio.dev/toolkits/vapi/framework/hermes-agent) - [Atomic Agent](https://composio.dev/toolkits/vapi/framework/atomic-agent) - [Google ADK](https://composio.dev/toolkits/vapi/framework/google-adk) - [LangChain](https://composio.dev/toolkits/vapi/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/vapi/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/vapi/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/vapi/framework/llama-index) - [Pydantic AI](https://composio.dev/toolkits/vapi/framework/pydantic-ai) - [AutoGen](https://composio.dev/toolkits/vapi/framework/autogen) ## Related Toolkits - [Composio](https://composio.dev/toolkits/composio) - Composio is an integration platform that connects AI agents with hundreds of business tools. It streamlines authentication and lets you trigger actions across services—no custom code needed. - [Composio search](https://composio.dev/toolkits/composio_search) - Composio search is a unified web search toolkit spanning travel, e-commerce, news, financial markets, images, and more. It lets you and your apps tap into up-to-date web data from a single, easy-to-integrate service. - [Perplexityai](https://composio.dev/toolkits/perplexityai) - Perplexityai delivers natural, conversational AI models for generating human-like text. Instantly get context-aware, high-quality responses for chat, search, or complex workflows. - [Browser tool](https://composio.dev/toolkits/browser_tool) - Browser tool is a virtual browser integration that lets AI agents interact with the web programmatically. It enables automated browsing, scraping, and action-taking from any AI workflow. - [Ai ml api](https://composio.dev/toolkits/ai_ml_api) - Ai ml api is a suite of AI/ML models for natural language and image tasks. It provides fast, scalable access to advanced AI capabilities for your apps and workflows. - [Aivoov](https://composio.dev/toolkits/aivoov) - Aivoov is an AI-powered text-to-speech platform offering 1,000+ voices in over 150 languages. Instantly turn written content into natural, human-like audio for any application. - [All images ai](https://composio.dev/toolkits/all_images_ai) - All-Images.ai is an AI-powered image generation and management platform. It helps you create, search, and organize images effortlessly with advanced AI capabilities. - [AltTextLab](https://composio.dev/toolkits/alt_text_lab) - AltTextLab is an AI service that generates accessible, SEO-aware alt text for images. It helps teams make image content easier to understand, index, and publish. - [Anthropic administrator](https://composio.dev/toolkits/anthropic_administrator) - Anthropic administrator is an API for managing Anthropic organizational resources like members, workspaces, and API keys. It helps you automate admin tasks and streamline resource management across your Anthropic organization. - [Api labz](https://composio.dev/toolkits/api_labz) - Api labz is a platform offering a suite of AI-driven APIs and workflow tools. It helps developers automate tasks and build smarter, more efficient applications. - [Apiframe](https://composio.dev/toolkits/apiframe) - Apiframe is an API platform for generating and managing AI images, videos, music, uploads, assets, jobs, and custom LoRAs. It gives developers one clean API for creative AI workflows without juggling multiple model providers. - [Apipie ai](https://composio.dev/toolkits/apipie_ai) - Apipie ai is an AI model aggregator offering a single API for accessing top AI models from multiple providers. It helps developers build cost-efficient, latency-optimized AI solutions without juggling multiple integrations. - [Arize AX](https://composio.dev/toolkits/arize_ax) - Arize AX is an AI engineering platform for tracing, evaluating, and improving AI applications. Use it to debug LLM behavior, compare experiments, and improve production AI quality. - [Artificial Analysis](https://composio.dev/toolkits/artificial_analysis) - Artificial Analysis is an independent benchmarking platform for AI models and API providers. Use it to compare model intelligence, coding, math, pricing, latency, throughput, and arena rankings. - [AssemblyAI](https://composio.dev/toolkits/assemblyai) - AssemblyAI is a speech-to-text and audio intelligence API for uploaded or hosted media. Use it to turn audio and video into accurate transcripts, summaries, and insights. - [Astica ai](https://composio.dev/toolkits/astica_ai) - Astica ai provides APIs for computer vision, NLP, and voice synthesis. Integrate advanced AI features into your app with a single API key. - [Avoma](https://composio.dev/toolkits/avoma) - Avoma is an AI meeting assistant for recording, transcribing, analyzing, and managing meetings, calls, notes, scorecards, and conversation intelligence. It helps teams turn conversations into searchable notes, follow-ups, coaching insights, and revenue intelligence. - [Bigml](https://composio.dev/toolkits/bigml) - BigML is a machine learning platform that lets you build, train, and deploy predictive models from your data. Its intuitive interface and robust API make machine learning accessible and efficient. - [Black Forest Labs](https://composio.dev/toolkits/bfl) - Black Forest Labs provides hosted FLUX models for generating and editing images and videos. It offers fast, flexible media creation with asynchronous processing and fine-tuning support. - [Bland AI](https://composio.dev/toolkits/bland_ai) - Bland AI is a conversational AI platform for building voice agents, phone calls, messaging, and communication workflows. Use it to automate calling, evaluate conversations, and run voice operations at scale. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Vapi MCP? With a standalone Vapi MCP server, the agents and LLMs can only access a fixed set of Vapi tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Vapi 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 Vapi tools. ### Can I manage the permissions and scopes for Vapi while using Tool Router? Yes, absolutely. You can configure which Vapi 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 Vapi data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)