How to integrate V0 MCP with Mastra AI

This guide walks you through connecting V0 to Mastra AI 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 Mastra AI 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.

V0 logoV0
Api Key

V0 is an AI-powered web development assistant from Vercel that generates real, production-ready code for modern apps. Build modern web experiences faster with automated, intelligent code suggestions and UI components.

44 Tools

Introduction

This guide walks you through connecting V0 to Mastra AI 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 Mastra AI 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

TL;DR

Here's what you'll learn:
  • Set up your environment so Mastra, OpenAI, and Composio work together
  • Create a Tool Router session in Composio that exposes V0 tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch V0 tool definitions and attach them as a toolset
  • Build a Mastra agent that can reason, call tools, and return structured results
  • Run an interactive CLI where you can chat with your V0 agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

  • MCP Client: Built-in support for Model Context Protocol servers
  • Toolsets: Organize tools into logical groups
  • Step Callbacks: Monitor and debug agent execution
  • OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

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.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Node.js 18 or higher
  • A Composio account with an active API key
  • An OpenAI API key
  • Basic familiarity with TypeScript
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key.
  • You need credits or a connected billing setup to use the models.
  • Store the key somewhere safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Go to Settings and copy your API key.
  • This key lets your Mastra agent talk to Composio and reach V0 through MCP.
3

Install dependencies

bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

  • @composio/core is the Composio SDK for creating MCP sessions
  • @mastra/core provides the Agent class
  • @mastra/mcp is Mastra's MCP client
  • @ai-sdk/openai is the model wrapper for OpenAI
  • dotenv loads environment variables from .env
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio
  • COMPOSIO_USER_ID tells Composio which user this session belongs to
  • OPENAI_API_KEY lets the Mastra agent call OpenAI models
5

Import libraries and validate environment

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});
What's happening:
  • dotenv/config auto loads your .env so process.env.* is available
  • openai gives you a Mastra compatible model wrapper
  • Agent is the Mastra agent that will call tools and produce answers
  • MCPClient connects Mastra to your Composio MCP server
  • Composio is used to create a Tool Router session
6

Create a Tool Router session for V0

typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["v0"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("V0 MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "v0" for V0 access
  • session.mcp.url is the MCP URL that Mastra's MCPClient will connect to
7

Configure Mastra MCP client and fetch tools

typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
What's happening:
  • MCPClient takes an id for this client and a list of MCP servers
  • The headers property includes the x-api-key for authentication
  • getTools fetches the tool definitions exposed by the V0 toolkit
8

Create the Mastra agent

typescript
const agent = new Agent({
    name: "v0-mastra-agent",
    instructions: "You are an AI agent with V0 tools via Composio.",
    model: "openai/gpt-5",
  });
What's happening:
  • Agent is the core Mastra agent
  • name is just an identifier for logging and debugging
  • instructions guide the agent to use tools instead of only answering in natural language
  • model uses openai("gpt-5") to configure the underlying LLM
9

Set up interactive chat interface

typescript
let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\n");

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        v0: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
What's happening:
  • messages keeps the full conversation history in Mastra's expected format
  • agent.generate runs the agent with conversation history and V0 toolsets
  • maxSteps limits how many tool calls the agent can take in a single run
  • onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

Here's the complete code to get you started with V0 and Mastra AI:

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["v0"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      v0: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "v0-mastra-agent",
    instructions: "You are an AI agent with V0 tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { v0: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with V0 through Composio's Tool Router. You can extend this further by:
  • Adding other toolkits like Gmail, Slack, or GitHub
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows
TOOLS

Supported Tools

Every V0 action and event your agent gets out of the box.

Assign Chat To Project

Tool to assign a chat to a project.

V0 Chat Completions

Tool to generate a chat model response given a list of messages.

Create Webhook

Tool to create a new webhook subscription for receiving event notifications.

Create V0 Project

Tool to create a new v0 project container for chats and code generation.

Create Project Environment Variables

Tool to create new environment variables for a v0 project.

Create Vercel Project

Tool to link a Vercel project to an existing v0 project.

Delete Chat

Tool to permanently delete a specific chat by ID.

Delete Deployment

Tool to delete a deployment by ID from Vercel.

Delete Hook

Tool to delete a webhook by its ID.

Delete Project Environment Variables

Tool to delete multiple environment variables from a project by their IDs.

Delete V0 Project

Tool to permanently delete a v0 project by its ID.

Deploy Project

Tool to deploy a specific v0 chat version to Vercel.

Download Chat Version

Tool to download all files for a specific chat version as a zip or tarball archive.

Export Project Code

Tool to export a deployable snapshot of a v0 chat version by retrieving all files (including default/deployment files).

Favorite Chat

Tool to mark a chat as favorite or remove the favorite status.

Find Chats

Tool to retrieve a list of chats.

Find Projects

Tool to retrieve a list of projects associated with the authenticated user.

Find Vercel Projects

Tool to retrieve a list of Vercel projects linked to the user's v0 workspace.

Fork Chat

Tool to create a fork (copy) of an existing chat.

Get Chat

Tool to retrieve the full details of a specific chat using its chatId.

Get Chat Project

Tool to retrieve the v0 project associated with a given chat.

Get Deployment Errors

Tool to retrieve errors for a specific deployment.

Get Deployment Logs

Tool to retrieve logs for a specific deployment.

Get Hook

Tool to retrieve detailed information about a specific webhook by its ID.

Get Chat Message

Tool to retrieve detailed information about a specific message within a chat.

Get Project by ID

Tool to retrieve the details of a specific v0 project by its ID, including associated chats and metadata.

Get Project Environment Variable

Tool to retrieve a specific environment variable for a given project by its ID, including its value.

Get Rate Limits

Tool to retrieve the current rate limits for the authenticated user.

Get Usage Report

Tool to retrieve detailed usage events including costs, models used, and metadata.

Get User

Tool to retrieve the currently authenticated user's information.

Get User Billing

Tool to fetch billing usage and quota information for the authenticated user.

Get User Plan

Tool to retrieve the authenticated user's subscription plan details including billing cycle and balance.

Get User Scopes

Tool to retrieve all accessible scopes for the authenticated user, such as personal workspaces or shared teams.

Initialize Chat

Tool to initialize a new chat from source content such as files, repositories, registries, zip archives, or templates.

List Chat Versions

Tool to retrieve all versions (iterations) for a specific chat, ordered by creation date (newest first).

List Deployments

Tool to retrieve a list of deployments for a given project, chat, and version.

List Hooks

Tool to retrieve all webhooks tied to chat events or deployments.

List Messages

Tool to retrieve all messages within a specific chat.

List Project Environment Variables

Tool to retrieve all environment variables for a project with optional decryption.

Update Chat

Tool to update metadata of an existing v0 chat.

Update Chat Version Files

Tool to update source files of a specific chat version.

Update V0 Webhook

Tool to update the configuration of an existing webhook, including its name, event subscriptions, or target URL.

Update V0 Project

Tool to update the metadata of an existing v0 project using its projectId.

Update Project Environment Variables

Tool to update environment variables for a v0 project.

FAQ

Frequently asked questions

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.

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

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.

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.

Start with V0.It takes 30 seconds.

Managed auth, hosted MCP servers, and every V0 tool your agent needs.Free to start.

Start building