Vercel with Vercel AI SDK

How to integrate Vercel MCP with Vercel AI SDK v6

Trusted by

GET STARTED FOR FREE GET A DEMO

30 min · no commitment · see it on your stack

Introduction Also integrate Vercel with TL;DR What is Vercel AI SDK What is the Vercel MCP server Supported Tools & Triggers Creating MCP Server - Stand-alone vs Composio SDK Step-by-step Guide Complete Code Conclusion How to build Vercel MCP Agent with another framework Explore Other Toolkits FAQ

Connect Vercel without Auth hassles

We manage OAuth, API Key, token refresh, and scopes, you just build.

Try for Free

Introduction

This guide walks you through connecting Vercel to Vercel AI SDK v6 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 Vercel AI SDK 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

ChatGPT OpenAI Agents SDK Claude Agent SDK Claude Code Claude Cowork Codex OpenCode Cursor VS Code OpenClaw Hermes CLI Google ADK LangChain Mastra AI LlamaIndex CrewAI

TL;DR

Here's what you'll learn:

How to set up and configure a Vercel AI SDK agent with Vercel integration
Using Composio's Tool Router to dynamically load and access Vercel tools
Creating an MCP client connection using HTTP transport
Building an interactive CLI chat interface with conversation history management
Handling tool calls and results within the Vercel AI SDK framework

What is Vercel AI SDK?

The Vercel AI SDK is a TypeScript library for building AI-powered applications. It provides tools for creating agents that can use external services and maintain conversation state.

Key features include:

streamText: Core function for streaming responses with real-time tool support
MCP Client: Built-in support for Model Context Protocol via @ai-sdk/mcp
Step Counting: Control multi-step tool execution with stopWhen: stepCountIs()
OpenAI Provider: Native integration with OpenAI models

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:

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

Step-by-step Guide

Prerequisites

Before you begin, make sure you have:

Node.js and npm installed
A Composio account with API key
An OpenAI API key

Getting API Keys for OpenAI and Composio

OpenAI API Key

Go to the OpenAI dashboard 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.
Navigate to your API settings and generate a new API key.
Store this key securely as you'll need it for authentication.

Install required dependencies

bash

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

First, install the necessary packages for your project.

What you're installing:

@ai-sdk/openai: Vercel AI SDK's OpenAI provider
@ai-sdk/mcp: MCP client for Vercel AI SDK
@composio/core: Composio SDK for tool integration
ai: Core Vercel AI SDK
dotenv: Environment variable management

Set up environment variables

bash

OPENAI_API_KEY=your_openai_api_key_here
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here

Create a .env file in your project root.

What's needed:

OPENAI_API_KEY: Your OpenAI API key for GPT model access
COMPOSIO_API_KEY: Your Composio API key for tool access
COMPOSIO_USER_ID: A unique identifier for the user session

Import required modules and validate environment

typescript

import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Composio } from "@composio/core";
import * as readline from "readline";
import { streamText, type ModelMessage, stepCountIs } from "ai";
import { createMCPClient } from "@ai-sdk/mcp";

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

if (!process.env.OPENAI_API_KEY) 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,
});

What's happening:

We're importing all necessary libraries including Vercel AI SDK's OpenAI provider and Composio
The dotenv/config import automatically loads environment variables
The MCP client import enables connection to Composio's tool server

Create Tool Router session and initialize MCP client

typescript

async function main() {
  // Create a tool router session for the user
  const session = await composio.create(composioUserID!, {
    toolkits: ["vercel"],
  });

  const mcpUrl = session.mcp.url;

What's happening:

We're creating a Tool Router session that gives your agent access to Vercel tools
The create method takes the user ID and specifies which toolkits should be available
The returned mcp object contains the URL and authentication headers needed to connect to the MCP server
This session provides access to all Vercel-related tools through the MCP protocol

Connect to MCP server and retrieve tools

typescript

const mcpClient = await createMCPClient({
  transport: {
    type: "http",
    url: mcpUrl,
    headers: session.mcp.headers, // Authentication headers for the Composio MCP server
  },
});

const tools = await mcpClient.tools();

What's happening:

We're creating an MCP client that connects to our Composio Tool Router session via HTTP
The mcp.url provides the endpoint, and mcp.headers contains authentication credentials
The type: "http" is important - Composio requires HTTP transport
tools() retrieves all available Vercel tools that the agent can use

Initialize conversation and CLI interface

typescript

let messages: ModelMessage[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log(
  "Ask any questions related to vercel, like summarize my last 5 emails, send an email, etc... :)))\n",
);

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

rl.prompt();

What's happening:

We initialize an empty messages array to maintain conversation history
A readline interface is created to accept user input from the command line
Instructions are displayed to guide the user on how to interact with the agent

Handle user input and stream responses with real-time tool feedback

typescript

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({ role: "user", content: trimmedInput });
  console.log("\nAgent is thinking...\n");

  try {
    const stream = streamText({
      model: openai("gpt-5"),
      messages,
      tools,
      toolChoice: "auto",
      stopWhen: stepCountIs(10),
      onStepFinish: (step) => {
        for (const toolCall of step.toolCalls) {
          console.log(`[Using tool: ${toolCall.toolName}]`);
          }
          if (step.toolCalls.length > 0) {
            console.log(""); // Add space after tool calls
          }
        },
      });

      for await (const chunk of stream.textStream) {
        process.stdout.write(chunk);
      }

      console.log("\n\n---\n");

      // Get final result for message history
      const response = await stream.response;
      if (response?.messages?.length) {
        messages.push(...response.messages);
      }
    } catch (error) {
      console.error("\nAn error occurred while talking to the agent:");
      console.error(error);
      console.log(
        "\nYou can try again or restart the app if it keeps happening.\n",
      );
    } finally {
      rl.prompt();
    }
  });

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

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});

What's happening:

We use streamText instead of generateText to stream responses in real-time
toolChoice: "auto" allows the model to decide when to use Vercel tools
stopWhen: stepCountIs(10) allows up to 10 steps for complex multi-tool operations
onStepFinish callback displays which tools are being used in real-time
We iterate through the text stream to create a typewriter effect as the agent responds
The complete response is added to conversation history to maintain context
Errors are caught and displayed with helpful retry suggestions

Complete Code

Here's the complete code to get you started with Vercel and Vercel AI SDK:

typescript

import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Composio } from "@composio/core";
import * as readline from "readline";
import { streamText, type ModelMessage, stepCountIs } from "ai";
import { createMCPClient } from "@ai-sdk/mcp";

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

if (!process.env.OPENAI_API_KEY) 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,
});

async function main() {
  // Create a tool router session for the user
  const session = await composio.create(composioUserID!, {
    toolkits: ["vercel"],
  });

  const mcpUrl = session.mcp.url;

  const mcpClient = await createMCPClient({
    transport: {
      type: "http",
      url: mcpUrl,
      headers: session.mcp.headers, // Authentication headers for the Composio MCP server
    },
  });

  const tools = await mcpClient.tools();

  let messages: ModelMessage[] = [];

  console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
  console.log(
    "Ask any questions related to vercel, like summarize my last 5 emails, send an email, etc... :)))\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({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    try {
      const stream = streamText({
        model: openai("gpt-5"),
        messages,
        tools,
        toolChoice: "auto",
        stopWhen: stepCountIs(10),
        onStepFinish: (step) => {
          for (const toolCall of step.toolCalls) {
            console.log(`[Using tool: ${toolCall.toolName}]`);
          }
          if (step.toolCalls.length > 0) {
            console.log(""); // Add space after tool calls
          }
        },
      });

      for await (const chunk of stream.textStream) {
        process.stdout.write(chunk);
      }

      console.log("\n\n---\n");

      // Get final result for message history
      const response = await stream.response;
      if (response?.messages?.length) {
        messages.push(...response.messages);
      }
    } catch (error) {
      console.error("\nAn error occurred while talking to the agent:");
      console.error(error);
      console.log(
        "\nYou can try again or restart the app if it keeps happening.\n",
      );
    } finally {
      rl.prompt();
    }
  });

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

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});

Conclusion

You've successfully built a Vercel agent using the Vercel AI SDK with streaming capabilities! This implementation provides a powerful foundation for building AI applications with natural language interfaces and real-time feedback.

Key features of this implementation:

Real-time streaming responses for a better user experience with typewriter effect
Live tool execution feedback showing which tools are being used as the agent works
Dynamic tool loading through Composio's Tool Router with secure authentication
Multi-step tool execution with configurable step limits (up to 10 steps)
Comprehensive error handling for robust agent execution
Conversation history maintenance for context-aware responses

You can extend this further by adding custom error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.

How to build Vercel MCP Agent with another framework

ChatGPT

Use Vercel MCP with ChatGPT

OpenAI Agents SDK

Use Vercel MCP with OpenAI Agents SDK

Claude Agent SDK

Use Vercel MCP with Claude Agent SDK

Claude Code

Use Vercel MCP with Claude Code

Claude Cowork

Use Vercel MCP with Claude Cowork

Codex

Use Vercel MCP with Codex

Cursor

Use Vercel MCP with Cursor

OpenClaw

Use Vercel MCP with OpenClaw

Hermes

Use Vercel MCP with Hermes

CLI

Use Vercel MCP with CLI

Google ADK

Use Vercel MCP with Google ADK

LangChain

Use Vercel MCP with LangChain

Mastra AI

Use Vercel MCP with Mastra AI

LlamaIndex

Use Vercel MCP with LlamaIndex

CrewAI

Use Vercel MCP with CrewAI

OpenCode

Use Vercel MCP with OpenCode

VS Code

Use Vercel MCP with VS Code

Explore Other Toolkits

Supabase

Oauth2Api Key

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

No Auth

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

Oauth2

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.

TOOLKIT MARKETPLACE

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 Vercel AI SDK v6?

Yes, you can. Vercel AI SDK v6 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

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 free Get a demo↗

Harsha GaddipatiCo-founder, Slashy

Karan skipped his own birthday party to fix our critical issue. It was 10 pm and he diverted his Waymo to help us instead. This really sets the bar, shows you the commitment you need to have when users rely on your software.

Abhi AryaCo-founder, Opennote

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it has immensely helped in keeping new users on the platform.

Nirman DaveCEO, Zams

We chose Composio over Pipedream because it delivered depth where it mattered. It supported niche tools and tricky edge cases that other platforms simply ignored. Giving us confidence to scale without compromising.

Ryan YuFounder, Extra Thursday

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down in the complexities of managing agent auth would have been a death sentence for Extra Thursday.

Tomisin JenrolaFounder & CEO, SwarmZero

Before partnering with Composio, adding tool integrations was a slow, resource-intensive process. Each integration could take weeks or months of engineering time, and maintaining them meant constantly keeping up with API changes.

Jerome LeclancheCo-Founder, Ingram Technologies

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

How to integrate Vercel MCP with Vercel AI SDK v6

Table of Contents

Connect Vercel without Auth hassles

Introduction

Also integrate Vercel with

TL;DR

What is Vercel AI SDK?

What is the Vercel MCP server, and what's possible with it?

Supported Tools & Triggers

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

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI and Composio

Install required dependencies

Set up environment variables

Import required modules and validate environment

Create Tool Router session and initialize MCP client

Connect to MCP server and retrieve tools

Initialize conversation and CLI interface

Handle user input and stream responses with real-time tool feedback

Complete Code

Conclusion

How to build Vercel MCP Agent with another framework

ChatGPT

OpenAI Agents SDK

Claude Agent SDK

Claude Code

Claude Cowork

Codex

Cursor

OpenClaw

Hermes

CLI

Google ADK

LangChain

Mastra AI

LlamaIndex

CrewAI

OpenCode

VS Code

Explore Other Toolkits

Supabase

Codeinterpreter

GitHub

FAQ

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

Can I use Tool Router MCP with Vercel AI SDK v6?

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

How safe is my data with Composio Tool Router?

Used by agents from

Never worry about agent reliability