# How to integrate V0 MCP with CrewAI ```json { "title": "How to integrate V0 MCP with CrewAI", "toolkit": "V0", "toolkit_slug": "v0", "framework": "CrewAI", "framework_slug": "crew-ai", "url": "https://composio.dev/toolkits/v0/framework/crew-ai", "markdown_url": "https://composio.dev/toolkits/v0/framework/crew-ai.md", "updated_at": "2026-05-12T10:29:38.327Z" } ``` ## Introduction This guide walks you through connecting V0 to CrewAI using the Composio tool router. By the end, you'll have a working V0 agent that can generate react code for a login page, list all your active v0 projects, summarize our last five chat sessions through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a V0 account through Composio's V0 MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate V0 with - [ChatGPT](https://composio.dev/toolkits/v0/framework/chatgpt) - [OpenAI Agents SDK](https://composio.dev/toolkits/v0/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/v0/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/v0/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/v0/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/v0/framework/codex) - [Cursor](https://composio.dev/toolkits/v0/framework/cursor) - [VS Code](https://composio.dev/toolkits/v0/framework/vscode) - [OpenCode](https://composio.dev/toolkits/v0/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/v0/framework/openclaw) - [Hermes](https://composio.dev/toolkits/v0/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/v0/framework/cli) - [Google ADK](https://composio.dev/toolkits/v0/framework/google-adk) - [LangChain](https://composio.dev/toolkits/v0/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/v0/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/v0/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/v0/framework/llama-index) ## TL;DR Here's what you'll learn: - Get a Composio API key and configure your V0 connection - Set up CrewAI with an MCP enabled agent - Create a Tool Router session or standalone MCP server for V0 - Build a conversational loop where your agent can execute V0 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 V0 MCP server, and what's possible with it? The V0 MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your V0 account. It provides structured and secure access to your V0 projects and chat-powered workflows, so your agent can perform actions like generating code, managing web projects, retrieving chat histories, and facilitating AI-driven conversations on your behalf. - AI-powered chat completions: Instantly generate conversational replies or code suggestions using V0's advanced chat models tailored for web development workflows. - Retrieve and manage chat sessions: List and access your previous AI-assisted chat threads, including support for filtering favorites and paginated results. - Project discovery and management: Fetch a complete list of your web development projects, making it easy for your agent to interact with or summarize project data. - Integrated development automation: Seamlessly combine chat capabilities and project management to automate code generation, troubleshooting, or project setup tasks. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `V0_ASSIGN_CHAT_TO_PROJECT` | Assign Chat To Project | Tool to assign a chat to a project. Use when you need to group a conversation under a shared project context for better organization. | | `V0_V0_CHAT_COMPLETIONS` | V0 Chat Completions | Tool to generate a chat model response given a list of messages. Use when you need AI-powered conversational replies via the v0 API. Note: This action uses the POST /chats endpoint which creates a persistent chat session in the user's v0 account. Each call will create a new chat that can be viewed at the returned webUrl or accessed via the apiUrl. | | `V0_CREATE_HOOK_V0` | Create Webhook | Tool to create a new webhook subscription for receiving event notifications. Use when you need to listen for chat or message events from v0. | | `V0_CREATE_PROJECT` | Create V0 Project | Tool to create a new v0 project container for chats and code generation. Use when you need to start a clean project with specific configuration. | | `V0_CREATE_PROJECT_ENV_VARS` | Create Project Environment Variables | Tool to create new environment variables for a v0 project. Use when you need to add environment variables to a project. By default, fails if any keys already exist unless upsert is set to true. | | `V0_CREATE_VERCEL_PROJECT` | Create Vercel Project | Tool to link a Vercel project to an existing v0 project. Use when you need to enable Vercel-related features and deployment integration for a v0 project. | | `V0_DELETE_CHAT` | Delete Chat | Tool to permanently delete a specific chat by ID. Use when you need to remove a chat and all its contents irreversibly. | | `V0_DELETE_DEPLOYMENT` | Delete Deployment | Tool to delete a deployment by ID from Vercel. Use when you need to remove a specific deployment permanently. | | `V0_DELETE_HOOK` | Delete Hook | Tool to delete a webhook by its ID. Use when you need to remove a webhook subscription. This action is irreversible. | | `V0_DELETE_PROJECT_ENV_VARS_V0` | Delete Project Environment Variables | Tool to delete multiple environment variables from a project by their IDs. Use when you need to remove environment variables from a v0 project. | | `V0_DELETE_V0_PROJECT` | Delete V0 Project | Tool to permanently delete a v0 project by its ID. Use when you need to remove a project and optionally all its associated chats. This operation is irreversible. | | `V0_DEPLOY_PROJECT` | Deploy Project | Tool to deploy a specific v0 chat version to Vercel. Use when you need to create a live deployment with public URLs after generating code via v0. | | `V0_DOWNLOAD_CHAT_VERSION` | Download Chat Version | Tool to download all files for a specific chat version as a zip or tarball archive. Use when you need to retrieve a complete downloadable archive of a version's files, optionally including deployment configuration files. | | `V0_EXPORT_PROJECT_CODE` | Export Project Code | Tool to export a deployable snapshot of a v0 chat version by retrieving all files (including default/deployment files). Use when you need to get the complete generated code for a specific version, ready for local deployment or artifact creation. | | `V0_FAVORITE_CHAT` | Favorite Chat | Tool to mark a chat as favorite or remove the favorite status. Use when you need to organize and quickly access important chats. | | `V0_V0_FIND_CHATS` | Find Chats | Tool to retrieve a list of chats. Use when you need to list user chats with pagination and optional favorite filtering after authentication. | | `V0_V0_FIND_PROJECTS` | Find Projects | Tool to retrieve a list of projects associated with the authenticated user. Use after obtaining a valid API key. | | `V0_FIND_VERCEL_PROJECTS` | Find Vercel Projects | Tool to retrieve a list of Vercel projects linked to the user's v0 workspace. Use when you need to discover available Vercel projects for deployment or integration purposes. | | `V0_FORK_CHAT` | Fork Chat | Tool to create a fork (copy) of an existing chat. Use when you need to explore alternative directions without modifying the original conversation. | | `V0_GET_CHAT` | Get Chat | Tool to retrieve the full details of a specific chat using its chatId. Use when you need to access chat messages, metadata, and configuration for a specific chat. | | `V0_GET_CHAT_PROJECT` | Get Chat Project | Tool to retrieve the v0 project associated with a given chat. Use when you need to determine the context or scope of a chat session. | | `V0_GET_DEPLOYMENT_ERRORS` | Get Deployment Errors | Tool to retrieve errors for a specific deployment. Use when diagnosing and debugging deployment issues. | | `V0_GET_DEPLOYMENT_LOGS` | Get Deployment Logs | Tool to retrieve logs for a specific deployment. Use when you need to debug or monitor deployment behavior by fetching log entries, optionally filtered by timestamp. | | `V0_GET_HOOK` | Get Hook | Tool to retrieve detailed information about a specific webhook by its ID. Use when you need to inspect webhook configuration, subscribed events, or target URL. | | `V0_GET_MESSAGE` | Get Chat Message | Tool to retrieve detailed information about a specific message within a chat. Use when you need to access message content, metadata, attachments, or model configuration for a known message ID. | | `V0_GET_PROJECT` | Get Project by ID | Tool to retrieve the details of a specific v0 project by its ID, including associated chats and metadata. Use when you need to inspect project configuration or access related chats. | | `V0_GET_PROJECT_ENV_VAR` | Get Project Environment Variable | Tool to retrieve a specific environment variable for a given project by its ID, including its value. Use when you need to get the details of a particular environment variable for a project. | | `V0_GET_RATE_LIMITS` | Get Rate Limits | Tool to retrieve the current rate limits for the authenticated user. Use when you need to monitor usage limits and avoid throttling. | | `V0_GET_USAGE_REPORT_V0` | Get Usage Report | Tool to retrieve detailed usage events including costs, models used, and metadata. Use when you need to access usage data from the dashboard, filter by chat/user, or analyze costs. | | `V0_GET_USER` | Get User | Tool to retrieve the currently authenticated user's information. Use when you need to get the user's ID, name, email, avatar, or account metadata. | | `V0_GET_USER_BILLING` | Get User Billing | Tool to fetch billing usage and quota information for the authenticated user. Use when you need to check the user's billing details or usage metrics. Can be scoped to a specific project or namespace. | | `V0_GET_USER_PLAN_V0` | Get User Plan | Tool to retrieve the authenticated user's subscription plan details including billing cycle and balance. Use to check plan status and usage limits. | | `V0_GET_USER_SCOPES` | Get User Scopes | Tool to retrieve all accessible scopes for the authenticated user, such as personal workspaces or shared teams. Use when you need to understand which workspaces the user can access. | | `V0_INIT_V0_CHAT` | Initialize Chat | Tool to initialize a new chat from source content such as files, repositories, registries, zip archives, or templates. Use when you need to start a new v0 chat session with pre-populated content. Initialization uses no tokens. | | `V0_LIST_CHAT_VERSIONS` | List Chat Versions | Tool to retrieve all versions (iterations) for a specific chat, ordered by creation date (newest first). Use when you need to view the history of a chat's generated versions with cursor-based pagination support. | | `V0_LIST_DEPLOYMENTS` | List Deployments | Tool to retrieve a list of deployments for a given project, chat, and version. Use when you need to check existing deployments for specific project versions. | | `V0_LIST_HOOKS` | List Hooks | Tool to retrieve all webhooks tied to chat events or deployments. Use when you need to list configured webhooks after authentication. | | `V0_LIST_MESSAGES` | List Messages | Tool to retrieve all messages within a specific chat. Use when you need to list messages with content, role, and type information. Supports pagination for chats with many messages. | | `V0_LIST_PROJECT_ENV_VARS` | List Project Environment Variables | Tool to retrieve all environment variables for a project with optional decryption. Use when you need to view project configuration or secrets. | | `V0_UPDATE_CHAT` | Update Chat | Tool to update metadata of an existing v0 chat. Use when you need to rename a chat or change its privacy setting after creation. | | `V0_UPDATE_CHAT_VERSION` | Update Chat Version Files | Tool to update source files of a specific chat version. Use when you need to manually edit generated files through the API. | | `V0_UPDATE_HOOK` | Update V0 Webhook | Tool to update the configuration of an existing webhook, including its name, event subscriptions, or target URL. Use when you need to modify webhook settings after creation. | | `V0_UPDATE_PROJECT` | Update V0 Project | Tool to update the metadata of an existing v0 project using its projectId. Use when you need to change the project name, description, instructions, or privacy setting. | | `V0_UPDATE_PROJECT_ENV_VARS` | Update Project Environment Variables | Tool to update environment variables for a v0 project. Use when you need to modify the values of existing environment variables. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The V0 MCP server is an implementation of the Model Context Protocol that connects your AI agent to V0. It provides structured and secure access so your agent can perform V0 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 V0 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 V0 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 V0 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 V0 **What's happening:** - You create a V0 only session through Composio - Composio returns an MCP HTTP URL that exposes V0 tools ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["v0"]) 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=["v0"], ) 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 V0 through Composio's Tool Router. The agent can perform V0 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 V0 MCP Agent with another framework - [ChatGPT](https://composio.dev/toolkits/v0/framework/chatgpt) - [OpenAI Agents SDK](https://composio.dev/toolkits/v0/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/v0/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/v0/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/v0/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/v0/framework/codex) - [Cursor](https://composio.dev/toolkits/v0/framework/cursor) - [VS Code](https://composio.dev/toolkits/v0/framework/vscode) - [OpenCode](https://composio.dev/toolkits/v0/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/v0/framework/openclaw) - [Hermes](https://composio.dev/toolkits/v0/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/v0/framework/cli) - [Google ADK](https://composio.dev/toolkits/v0/framework/google-adk) - [LangChain](https://composio.dev/toolkits/v0/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/v0/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/v0/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/v0/framework/llama-index) ## Related Toolkits - [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure. - [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms. - [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place. - [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences. - [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses. - [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure. - [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure. - [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction. - [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting. - [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache. - [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence. - [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place. - [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines. - [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure. - [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code. - [Bench](https://composio.dev/toolkits/bench) - Bench is a benchmarking tool for automated performance measurement and analysis. It helps you quickly evaluate, compare, and track your systems or workflows. - [Better stack](https://composio.dev/toolkits/better_stack) - Better Stack is a monitoring, logging, and incident management solution for apps and services. It helps teams ensure application reliability and performance with real-time insights. - [Bitbucket](https://composio.dev/toolkits/bitbucket) - Bitbucket is a Git-based code hosting and collaboration platform for teams. It enables secure repository management and streamlined code reviews. - [Blazemeter](https://composio.dev/toolkits/blazemeter) - Blazemeter is a continuous testing platform for web and mobile app performance. It empowers teams to automate and analyze large-scale tests with ease. - [Blocknative](https://composio.dev/toolkits/blocknative) - Blocknative delivers real-time mempool monitoring and transaction management for public blockchains. Instantly track pending transactions and optimize blockchain interactions with live data. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and V0 MCP? With a standalone V0 MCP server, the agents and LLMs can only access a fixed set of V0 tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from V0 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 V0 tools. ### Can I manage the permissions and scopes for V0 while using Tool Router? Yes, absolutely. You can configure which V0 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 V0 data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) ยท [Composio docs](https://docs.composio.dev/llms.txt)