# How to integrate V0 MCP with Claude Code

```json
{
  "title": "How to integrate V0 MCP with Claude Code",
  "toolkit": "V0",
  "toolkit_slug": "v0",
  "framework": "Claude Code",
  "framework_slug": "claude-code",
  "url": "https://composio.dev/toolkits/v0/framework/claude-code",
  "markdown_url": "https://composio.dev/toolkits/v0/framework/claude-code.md",
  "updated_at": "2026-05-12T10:29:38.327Z"
}
```

## Introduction

Manage your V0 directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.
You can do this in two different ways:
- Via [Composio Connect](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code) - Direct and easiest approach
- Via [Composio SDK](https://docs.composio.dev/docs?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_sdk) - Programmatic approach with more control

## 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 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)
- [CrewAI](https://composio.dev/toolkits/v0/framework/crew-ai)

## TL;DR

- Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
- Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
- Handling Large tool responses out of LLM context to minimize context rot.
- Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

## Connect V0 to Claude Code

### Connecting V0 to Claude Code using Composio
1. Add the Composio MCP to Claude

```bash
claude mcp add --scope user --transport http composio https://connect.composio.dev/mcp
```

## What is Claude Code?

Claude Code is Anthropic's command line developer tool that lets you use Claude directly inside your terminal. Instead of switching between your editor, browser, and chat, you can stay in your project folder and ask Claude to help you build, debug, refactor, and understand code right where you're working.
Key features include:
- Terminal-Native Experience: Work with Claude directly in your command line without switching contexts
- MCP Support: Built-in support for Model Context Protocol servers to extend Claude's capabilities
- Project Context: Claude understands your project structure and can read, write, and modify files
- Interactive Development: Ask questions, debug code, and get help in real-time while coding
- Multi-Platform: Works on macOS, Linux, WSL, and Windows

## 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 Claude Code (and other AI assistants like Claude and Cursor) directly to your V0 account. It provides structured and secure access so Claude can perform V0 operations on your behalf.
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:
- Claude Pro, Max, or API billing enabled Anthropic account
- Composio API Key
- A V0 account
- Basic knowledge of Python or TypeScript

### 1. Install Claude Code

To install Claude Code, use one of the following methods based on your operating system:
```bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd
```

### 2. Set up Claude Code

Open a terminal, go to your project folder, and start Claude Code:
- Claude Code will open in your terminal
- Follow the prompts to sign in with your Anthropic account
- Complete the authentication flow
- Once authenticated, you can start using Claude Code
```bash
cd your-project-folder
claude
```

### 3. Set up environment variables

Create a .env file in your project root with the following variables:
- COMPOSIO_API_KEY authenticates with Composio (get it from [Composio dashboard](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=api_key&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code))
- USER_ID identifies the user for session management (use any unique identifier)
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
```

### 4. Install Composio library

No description provided.
```python
pip install composio-core python-dotenv
```

```typescript
npm install @composio/core dotenv
```

### 5. Generate Composio MCP URL

No description provided.
```python
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

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

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["v0"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http v0-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['v0'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http v0-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

### 6. Run the script and copy the MCP URL

No description provided.
```python
python generate_mcp_url.py
```

```typescript
node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts
```

### 7. Add V0 MCP to Claude Code

In your terminal, add the MCP server using the command from the previous step. The command format is:
- claude mcp add registers a new MCP server with Claude Code
- --transport http specifies that this is an HTTP-based MCP server
- The server name (v0-composio) is how you'll reference it
- The URL points to your Composio Tool Router session
- --headers includes your Composio API key for authentication
After running the command, close the current Claude Code session and start a new one for the changes to take effect.
```bash
claude mcp add --transport http v0-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude
```

### 8. Verify the installation

Check that your V0 MCP server is properly configured.
- This command lists all MCP servers registered with Claude Code
- You should see your v0-composio entry in the list
- This confirms that Claude Code can now access V0 tools
If everything is wired up, you should see your v0-composio entry listed:
```bash
claude mcp list
```

### 9. Authenticate V0

The first time you try to use V0 tools, you'll be prompted to authenticate.
- Claude Code will detect that you need to authenticate with V0
- It will show you an authentication link
- Open the link in your browser (or copy/paste it)
- Complete the V0 authorization flow
- Return to the terminal and start using V0 through Claude Code
Once authenticated, you can ask Claude Code to perform V0 operations in natural language. For example:
- "Generate React code for a login page"
- "List all my active V0 projects"
- "Summarize our last five chat sessions"

## Complete Code

```python
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

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

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["v0"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http v0-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['v0'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http v0-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

## Conclusion

You've successfully integrated V0 with Claude Code using Composio's MCP server. Now you can interact with V0 directly from your terminal using natural language commands.
Key features of this setup:
- Terminal-native experience without switching contexts
- Natural language commands for V0 operations
- Secure authentication through Composio's managed MCP
- Tool Router for dynamic tool discovery and execution
Next steps:
- Try asking Claude Code to perform various V0 operations
- Add more toolkits to your Tool Router session for multi-app workflows
- Integrate this setup into your development workflow for increased productivity
You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

## 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 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)
- [CrewAI](https://composio.dev/toolkits/v0/framework/crew-ai)

## 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 Claude Code?

Yes, you can. Claude Code 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)