How to integrate V0 MCP with Kimi Code

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

V0 logo
Kimi Code logo
divider

How to integrate V0 MCP with Kimi Code

Kimi Code is Moonshot AI's open-source coding agent, powered by Kimi K2.6. It runs in your terminal, reads and edits code, executes shell commands, and plans multi-step tasks, with native MCP support for extending it to outside tools.

In this guide, I will explain the easiest and most secure way to connect your V0 account to Kimi Code via Composio Connect, so it can generate React code for a login page, list all your active V0 projects, summarize our last five chat sessions, and more without ever putting your account credentials at risk.

Also integrate V0 with

Why use Composio?

Composio provides:

  • Access to 1,000+ managed apps from a single MCP endpoint. This makes it convenient for agents to run cross-app workflows.
  • Managed OAuth. You do not have to worry about authentication and authorization flows for every app.
  • Programmatic tool calling. Allows LLMs to write code in a remote workbench to handle complex tool chaining. This reduces back-and-forth for frequent tool calls.
  • Large tool response handling outside the LLM context. This minimizes context bloat from large tool responses.
  • Dynamic just-in-time access to thousands of tools across hundreds of apps. Composio loads the tools your agent needs, so LLMs are not overwhelmed by tools they do not need.

Connect V0 to Kimi Code

Kimi Code is a TypeScript agent distributed through npm. It acts as an MCP client and reads server definitions from an mcp.json file, and it can also add and authenticate servers conversationally through /mcp-config. Composio is a remote HTTP server that authenticates with OAuth, so no API key is stored anywhere.

1. Install Kimi Code

The quickest way is the official install script, which requires no pre-installed Node.js and places the kimi executable on your PATH.

bash
# macOS or Linux
curl -fsSL https://code.kimi.com/kimi-code/install.sh | bash

# Windows PowerShell
irm https://code.kimi.com/kimi-code/install.ps1 | iex

# Confirm the installation
kimi --version

2. Log in

Start Kimi Code in your project directory, then sign in from the interactive UI:

bash
kimi

Run /login and choose Kimi Code OAuth using the device-code flow, or use a Moonshot API key.

3. Add Composio with /mcp-config

In current versions of Kimi Code, MCP servers are managed inside the app, not with a shell subcommand. From the interactive UI, run:

bash
/mcp-config
Kimi Code MCP config flow for adding the Composio MCP server

Tell it the server name and URL in plain language. For example:

Server name is Composio, and here is the server URL: https://connect.composio.dev/mcp

Kimi Code asks whether to add it globally, at ~/.kimi-code/mcp.json, or project-local for the current checkout, then writes the entry for you:

bash
{
  "mcpServers": {
    "Composio": {
      "url": "https://connect.composio.dev/mcp"
    }
  }
}

There is no transport field to set. Kimi Code infers HTTP from the url.

4. Restart the session

The new server is picked up on a fresh session, not the current one. Start a new session:

bash
/new

On the new session, Kimi Code detects that the server needs authorization and prompts you to run:

bash
/mcp-config login Composio

5. Authorize with OAuth

Run the command Kimi suggests:

bash
/mcp-config login composio

Kimi Code opens Composio's authorization page or surfaces a URL. Approve access, then return to the session. You should see confirmation that the Composio MCP server is connected.

Composio authorization page for Kimi Code MCP setup

Check the connection status any time with /mcp. Composio should appear as connected with its tools listed.

Kimi Code showing Composio connected after OAuth authorization

Connect your V0 account

Back in a Kimi Code session, ask the agent to connect to V0 or give it any V0-related task.

For example, ask it to:

  • "Generate React code for a login page"
  • "List all your active V0 projects"
  • "Summarize our last five chat sessions"

It will prompt you to authenticate and authorize access to V0.

That is it. Composio tools are now available in Kimi Code, and your V0 account is ready to use.

Supported Tools & Triggers

Tools
Assign Chat To ProjectTool to assign a chat to a project.
V0 Chat CompletionsTool to generate a chat model response given a list of messages.
Create WebhookTool to create a new webhook subscription for receiving event notifications.
Create V0 ProjectTool to create a new v0 project container for chats and code generation.
Create Project Environment VariablesTool to create new environment variables for a v0 project.
Create Vercel ProjectTool to link a Vercel project to an existing v0 project.
Delete ChatTool to permanently delete a specific chat by ID.
Delete DeploymentTool to delete a deployment by ID from Vercel.
Delete HookTool to delete a webhook by its ID.
Delete Project Environment VariablesTool to delete multiple environment variables from a project by their IDs.
Delete V0 ProjectTool to permanently delete a v0 project by its ID.
Deploy ProjectTool to deploy a specific v0 chat version to Vercel.
Download Chat VersionTool to download all files for a specific chat version as a zip or tarball archive.
Export Project CodeTool to export a deployable snapshot of a v0 chat version by retrieving all files (including default/deployment files).
Favorite ChatTool to mark a chat as favorite or remove the favorite status.
Find ChatsTool to retrieve a list of chats.
Find ProjectsTool to retrieve a list of projects associated with the authenticated user.
Find Vercel ProjectsTool to retrieve a list of Vercel projects linked to the user's v0 workspace.
Fork ChatTool to create a fork (copy) of an existing chat.
Get ChatTool to retrieve the full details of a specific chat using its chatId.
Get Chat ProjectTool to retrieve the v0 project associated with a given chat.
Get Deployment ErrorsTool to retrieve errors for a specific deployment.
Get Deployment LogsTool to retrieve logs for a specific deployment.
Get HookTool to retrieve detailed information about a specific webhook by its ID.
Get Chat MessageTool to retrieve detailed information about a specific message within a chat.
Get Project by IDTool to retrieve the details of a specific v0 project by its ID, including associated chats and metadata.
Get Project Environment VariableTool to retrieve a specific environment variable for a given project by its ID, including its value.
Get Rate LimitsTool to retrieve the current rate limits for the authenticated user.
Get Usage ReportTool to retrieve detailed usage events including costs, models used, and metadata.
Get UserTool to retrieve the currently authenticated user's information.
Get User BillingTool to fetch billing usage and quota information for the authenticated user.
Get User PlanTool to retrieve the authenticated user's subscription plan details including billing cycle and balance.
Get User ScopesTool to retrieve all accessible scopes for the authenticated user, such as personal workspaces or shared teams.
Initialize ChatTool to initialize a new chat from source content such as files, repositories, registries, zip archives, or templates.
List Chat VersionsTool to retrieve all versions (iterations) for a specific chat, ordered by creation date (newest first).
List DeploymentsTool to retrieve a list of deployments for a given project, chat, and version.
List HooksTool to retrieve all webhooks tied to chat events or deployments.
List MessagesTool to retrieve all messages within a specific chat.
List Project Environment VariablesTool to retrieve all environment variables for a project with optional decryption.
Update ChatTool to update metadata of an existing v0 chat.
Update Chat Version FilesTool to update source files of a specific chat version.
Update V0 WebhookTool to update the configuration of an existing webhook, including its name, event subscriptions, or target URL.
Update V0 ProjectTool to update the metadata of an existing v0 project using its projectId.
Update Project Environment VariablesTool to update environment variables for a v0 project.

Conclusion

You have successfully connected V0 to Kimi Code using Composio Connect. Your agent can now manage V0 from the terminal with natural language, without exposing credentials in prompts or local scripts.

Since the same Composio endpoint exposes 1,000+ apps, you can add Slack, Calendar, Linear, and more to the same server and chain them into cross-app workflows.

How to build V0 MCP Agent with another framework

FAQ

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 Kimi Code?

Yes, you can. Kimi 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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.