How to integrate Vercel MCP with Mastra AI

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Vercel logo
Mastra AI logo
divider

Introduction

This guide walks you through connecting Vercel to Mastra AI using the Composio tool router. By the end, you'll have a working Vercel agent that can deploy latest changes to your project, add api key as production environment variable, check if mydomain.com is available for purchase through natural language commands.

This guide will help you understand how to give your Mastra AI agent real control over a Vercel account through Composio's Vercel MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Vercel 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 Vercel tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Vercel 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 Vercel 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 Vercel MCP server, and what's possible with it?

The Vercel MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Vercel account. It provides structured and secure access to your Vercel projects and deployments, so your agent can perform actions like creating deployments, managing environment variables, handling edge configs, and checking domain statuses on your behalf.

  • Automated deployments and rollbacks: Easily instruct your agent to create new deployments or remove outdated ones, streamlining your release process without manual steps.
  • Environment variable management: Let your agent add or update sensitive configuration values across different environments, ensuring your projects are set up correctly before a deploy.
  • Edge configuration and token handling: Have your agent create new edge configs or generate secure tokens for read-only access, optimizing how your content is served globally.
  • Domain availability and pricing checks: Ask your agent to verify if a domain is available and fetch the latest price before you make a purchase decision.
  • Authentication token management: Enable your agent to create or revoke Vercel API tokens, giving you fine-grained control over programmatic access to your account.

Supported Tools & Triggers

Tools
Add Environment VariableTool to add an environment variable to a Vercel project.
Add Domain to ProjectTool to attach a custom domain to a Vercel project.
Assign Alias to DeploymentTool to assign an alias to a specific Vercel deployment.
Batch Remove Project Environment VariablesTool to batch remove environment variables from a Vercel project.
Buy DomainsTool to purchase multiple domains through Vercel's domain registrar.
Buy Single DomainTool to purchase a domain through Vercel's domain registrar.
Check Artifact ExistsTool to check if a cache artifact exists by its hash.
Check Domain AvailabilityTool to check if a domain is available for registration.
Check Domain PriceCheck pricing for a domain including purchase, renewal, and transfer costs.
Create Auth TokenTool to create a new authentication token.
Create DNS RecordTool to create a new DNS record for a domain.
Create Edge ConfigCreates a new Edge Config for storing key-value data at the edge.
Create Edge Config TokenCreate a read access token for a specific Edge Config.
Create new deploymentTool to create a new deployment.
Create or Transfer DomainTool to add an existing domain to the Vercel platform.
Create Vercel Project (v2)Tool to create a new Vercel project with comprehensive configuration options.
Create Project Transfer RequestTool to create a project transfer request.
Create Shared Environment VariableTool to create one or more shared environment variables in Vercel.
Create WebhookTool to create a webhook for receiving notifications about Vercel events.
Dangerously Delete By Source ImagesTool to dangerously delete edge cache by source image URLs.
Dangerously Delete Cache By TagsTool to dangerously delete edge cache by tags.
Delete Vercel AliasTool to delete an alias from Vercel.
Delete Auth TokenTool to delete an authentication token.
Purge All Data CacheTool to purge all data cache entries for a specific project.
Delete Deployment (V2)Permanently delete a Vercel deployment by its ID or URL.
Delete DNS RecordTool to delete a DNS record from a domain.
Delete DomainTool to remove a domain by name from Vercel.
Delete Edge ConfigTool to delete an Edge Config by its unique identifier.
Delete Edge Config Tokens (v2)Tool to delete one or more Edge Config tokens.
Delete Vercel Project (v2)Tool to delete a Vercel project by ID or name.
Remove Project Environment VariableTool to remove an environment variable from a Vercel project.
Delete Rolling Release ConfigurationTool to delete rolling release configuration for a project.
Delete Shared Env VariableTool to delete one or more shared environment variables.
Delete Vercel WebhookDelete a webhook by its unique ID to stop receiving event notifications.
Download Cache ArtifactDownload a cache artifact from Vercel's Remote Cache by its hash.
Edit Project Environment VariableTool to edit an environment variable in a Vercel project.
Filter Project Environment VariablesTool to retrieve environment variables of a Vercel project by id or name.
Get Active Attack StatusTool to read active attack data from Vercel Firewall for a specific project.
Get Vercel AliasTool to retrieve information about a Vercel alias by ID or alias name.
Query Artifact InformationTool to query information about artifacts by their hashes.
Get Auth Token MetadataTool to retrieve metadata for an authentication token.
Get Authenticated UserTool to get the authenticated user's profile.
Get Bulk Domain AvailabilityTool to check availability for multiple domains at once.
Get Remote Caching StatusTool to get the status of Remote Caching for the principal.
Get SSL/TLS CertificatesTool to retrieve SSL/TLS certificates for the authenticated user or team.
Get Integration ConfigurationsTool to get configurations for the authenticated user or team.
Get Contact Info SchemaTool to retrieve the contact information schema for a domain's top-level domain (TLD).
Get Deployment by ID or URLTool to get a deployment by ID or URL.
Get Deployment EventsTool to get deployment events for a specific Vercel deployment by ID or URL.
Get Deployment File ContentsRetrieve the contents of a specific file from a Vercel deployment.
Get Deployment Runtime LogsTool to retrieve runtime logs for a specific Vercel deployment by project and deployment ID.
Get DeploymentsTool to list deployments from Vercel.
Get Domain InformationTool to retrieve complete information for a single domain.
Get Domain ConfigurationTool to get a domain's configuration details from Vercel.
Get Domain Transfer InfoTool to get information required to transfer a domain to Vercel.
Get All DrainsTool to retrieve a list of all drains.
Get Edge ConfigTool to retrieve detailed information about a specific Edge Config by ID.
Get Edge Config BackupTool to retrieve a specific backup version of an Edge Config.
Get Edge Config ItemTool to retrieve a specific item within an Edge Config.
Get Edge Config SchemaTool to retrieve the JSON schema of a specific Edge Config.
Get Edge Config TokenTool to retrieve details of a specific token associated with an Edge Config.
Get Firewall ConfigurationTool to retrieve firewall configuration for a Vercel project.
List Git NamespacesTool to list Git namespaces (organizations/users) by provider.
Find Project by ID or NameTool to find a project by ID or name with comprehensive details.
Get Project DomainTool to retrieve details about a specific domain attached to a Vercel project.
List Project DomainsTool to retrieve all domains attached to a Vercel project.
Get Project Environment VariableTool to retrieve the decrypted value of an environment variable from a Vercel project.
Get ProjectsTool to retrieve a list of projects from Vercel.
List Promote AliasesTool to get a list of aliases with status for the current promote operation.
Get Rolling ReleaseTool to retrieve active rolling release information for a Vercel project.
Get Rolling Release Billing StatusTool to retrieve the rolling release billing status for a Vercel project.
Get Rolling Release ConfigTool to get rolling release configuration for a Vercel project.
Get Shared Environment VariableTool to retrieve the decrypted value of a Shared Environment Variable by id.
List Shared Environment VariablesTool to list all shared environment variables for a team.
Get Team DetailsRetrieves detailed information about a specific Vercel team by its ID or slug.
Get All TeamsTool to list all teams accessible to the authenticated user with detailed information.
Get TLD InfoTool to get information about a specific top-level domain (TLD).
Get TLD PriceTool to get pricing information for a specific top-level domain (TLD).
List User EventsTool to list user events.
Get WebhookTool to retrieve details of a specific webhook by ID.
Invalidate Cache By Source ImagesTool to invalidate edge cache by source image URLs.
Invalidate Cache By TagsTool to invalidate edge cache by tags.
List Vercel AliasesTool to list aliases from Vercel API.
List Auth TokensTool to list authentication tokens.
List Deployment AliasesTool to list all aliases assigned to a specific deployment.
List Deployment ChecksTool to retrieve a list of checks for a specific deployment.
List Deployment FilesTool to list all files in a specific deployment.
List DNS RecordsTool to list existing DNS records for a domain.
Get DomainsTool to list all domains from Vercel.
Get Edge Config BackupsTool to retrieve backups for a specific Edge Config.
Get Edge Config ItemsTool to retrieve all items from a specific Edge Config.
Get Edge ConfigsTool to retrieve all Edge Configs for an account or team.
Get Edge Config TokensTool to get all tokens of an Edge Config.
Get Firewall Events by ProjectRetrieve firewall events and security actions for a specific Vercel project.
Get Integration Log DrainsRetrieves a list of Integration log drains for a team or account.
Get Project Custom EnvironmentsTool to retrieve custom environments for a Vercel project.
Get Project MembersTool to list all members of a Vercel project.
Get Supported TLDsTool to retrieve all TLDs (top-level domains) supported by Vercel for domain registration.
Get Team MembersTool to list all members of a Vercel team.
Get List of WebhooksTool to retrieve a list of all webhooks for the authenticated account or team.
Move Project DomainTool to move a domain from one Vercel project to another.
Pause Vercel ProjectTool to pause a Vercel project.
Read Firewall ConfigurationTool to read firewall configuration for a Vercel project.
Record Artifacts Cache EventsTool to record artifacts cache usage events.
Remove Domain from ProjectTool to remove a domain from a Vercel project.
Update Vercel Firewall ConfigurationTool to update firewall configuration for a Vercel project.
Request Delete User AccountTool to initiate user account deletion on Vercel.
Promote Deployment to ProductionTool to promote a deployment to production by pointing all production domains for a project to the given deployment.
Search Git RepositoriesTool to search and list Git repositories linked to a namespace by provider.
Test Drain ConfigurationTool to validate a drain delivery configuration by sending a test request.
Transfer In DomainTool to transfer a domain to Vercel from another registrar.
Unlink Shared Environment VariableTool to disconnect a shared environment variable from a Vercel project.
Unpause Vercel ProjectTool to unpause a specific project by its ID.
Update Attack Challenge ModeTool to update Attack Challenge mode for a Vercel project.
Update DNS RecordTool to update an existing DNS record.
Patch DomainTool to update or move an apex domain on Vercel.
Update Edge ConfigTool to update an Edge Config by changing its slug.
Update Edge Config ItemsTool to update items within a specific Edge Config.
Update Edge Config SchemaTool to update the JSON Schema for an Edge Config.
Update Firewall ConfigurationTool to incrementally update Vercel Firewall configuration for a project using PATCH.
Update Vercel Project (v2)Tool to update an existing Vercel project configuration.
Update Project Data CacheTool to update the data cache feature for a Vercel project.
Update Project DomainTool to update a project domain in Vercel.
Update Project Protection BypassTool to update protection bypass for automation on a Vercel project.
Update Shared Env VariableTool to update one or more shared environment variables.
Update Project Static IPsTool to configure Static IPs for a Vercel project.
Update TeamTool to update a Vercel team's configuration.
Update URL Protection BypassTool to update the protection bypass for a URL.
Upload Cache ArtifactTool to upload a cache artifact to Vercel.
Upload Deployment FileTool to upload deployment files to Vercel.
Verify Project DomainAttempts to verify a project domain by checking if DNS challenges are correctly configured.

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

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

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 Vercel through MCP.

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

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

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

Create a Tool Router session for Vercel

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

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

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 Vercel toolkit

Create the Mastra agent

typescript
const agent = new Agent({
    name: "vercel-mastra-agent",
    instructions: "You are an AI agent with Vercel 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

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: {
        vercel: 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 Vercel 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 Vercel 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: ["vercel"],
  });

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "vercel-mastra-agent",
    instructions: "You are an AI agent with Vercel 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: { vercel: 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 Vercel 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

How to build Vercel MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Vercel MCP with ChatGPT

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Vercel MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Vercel MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Vercel MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Vercel MCP with Claude Cowork

Codex logo

Codex

Use Vercel MCP with Codex

Cursor logo

Cursor

Use Vercel MCP with Cursor

OpenClaw logo

OpenClaw

Use Vercel MCP with OpenClaw

Hermes logo

Hermes

Use Vercel MCP with Hermes

CLI logo

CLI

Use Vercel MCP with CLI

Google ADK logo

Google ADK

Use Vercel MCP with Google ADK

LangChain logo

LangChain

Use Vercel MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Vercel MCP with Vercel AI SDK

LlamaIndex logo

LlamaIndex

Use Vercel MCP with LlamaIndex

CrewAI logo

CrewAI

Use Vercel MCP with CrewAI

OpenCode logo

OpenCode

Use Vercel MCP with OpenCode

VS Code logo

VS Code

Use Vercel MCP with VS Code

FAQ

What are the differences in Tool Router MCP and Vercel MCP?

With a standalone Vercel MCP server, the agents and LLMs can only access a fixed set of Vercel tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Vercel and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Mastra AI?

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 Vercel tools.

Can I manage the permissions and scopes for Vercel while using Tool Router?

Yes, absolutely. You can configure which Vercel 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 Vercel 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.

Get started for freeGet a demo↗