How to integrate Vercel MCP with LlamaIndex

This guide walks you through connecting Vercel to LlamaIndex 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 LlamaIndex 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.

Get started for free Get a demo

Vercel

Api Key

Vercel is a platform for frontend frameworks and static sites, letting you host, deploy, and scale web projects with ease. It’s built for developers who want fast, automated deployments and minimal config.

131 Tools

Managed auth

Connect Vercel without auth hassles

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

Try for free

Introduction

This guide will help you understand how to give your LlamaIndex 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 Vercel AI SDK Mastra AI CrewAI

TL;DR

Here's what you'll learn:

Set your OpenAI and Composio API keys
Install LlamaIndex and Composio packages
Create a Composio Tool Router session for Vercel
Connect LlamaIndex to the Vercel MCP server
Build a Vercel-powered agent using LlamaIndex
Interact with Vercel through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

ReAct Agent: Reasoning and acting pattern for tool-using agents
MCP Tools: Native support for Model Context Protocol
Context Management: Maintain conversation context across interactions
Async Support: Built for async/await patterns

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.

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

Step by step10 STEPS

Prerequisites

Before you begin, make sure you have:

Python 3.8/Node 16 or higher installed
A Composio account with the API key
An OpenAI API key
A Vercel account and project
Basic familiarity with async Python/Typescript

Getting API Keys for OpenAI, Composio, and Vercel

OpenAI API key (OPENAI_API_KEY)

Go to the OpenAI dashboard
Create an API key if you don't have one
Assign it to OPENAI_API_KEY in .env

Composio API key and user ID

Log into the Composio dashboard
Copy your API key from Settings
- Use this as COMPOSIO_API_KEY
Pick a stable user identifier (email or ID)
- Use this as COMPOSIO_USER_ID

Installing dependencies

npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv

Create a new Typescript project and install the necessary dependencies:

@composio/llamaindex: Composio's LlamaIndex integration
@llamaindex/openai: OpenAI LLM integration
@llamaindex/tools: MCP client for LlamaIndex
@llamaindex/workflow: Workflow framework for LlamaIndex
dotenv: Environment variable management

Set environment variables

bash

OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

Authenticate with OpenAI's GPT-5 model
Connect to Composio's Tool Router
Identify your Composio user session for Vercel access

Import modules

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

Create a new file called vercel_llamaindex_agent.ts and import the required modules:

Key imports:

dotenv.config loads .env at runtime
readline gives us a simple CLI chat loop
Composio is the main Composio SDK client
mcp connects to an MCP endpoint
createAgent builds a LlamaIndex agent
openai configures the LLM backend

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

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

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

Create a Tool Router session and build the agent function

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["vercel"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Vercel actions." ,
    llm,
    tools,
  });

  return agent;
}

What's happening here:

We create a Composio client using your API key and configure it with the LlamaIndex provider
We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, vercel)
The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
LlamaIndex will connect to this endpoint to dynamically discover and use the available Vercel tools.
The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.

Create an interactive chat loop

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

We're creating a direct terminal interface to chat with Vercel
The LLM's responses are streamed to the CLI for faster interaction.
The agent uses context to maintain conversation history
The agent processes the request, selects appropriate Vercel tools, and returns a result
We extract the answer from the result data structure and display it to the user
You can type 'quit' or 'exit' to stop the chat loop gracefully
Agent responses and any errors are streamed in a clear, readable format

Define the main entry point

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();

What's happening here:

We're orchestrating the entire application flow
The agent gets built with proper error handling
Then we kick off the interactive chat loop so you can start talking to Vercel

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Vercel, then start asking questions.

Complete Code

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

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["vercel"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Vercel actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();

Conclusion

You've successfully connected Vercel to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:

Tool Router dynamically exposes Vercel tools through an MCP endpoint
LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
The agent becomes more capable without increasing prompt size
Async Python provides clean, efficient execution of agent workflows

You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.

TOOLS

Supported Tools

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

Add Environment Variable

Tool to add an environment variable to a Vercel project.

Add Domain to Project

Tool to attach a custom domain to a Vercel project.

Assign Alias to Deployment

Tool to assign an alias to a specific Vercel deployment.

Batch Remove Project Environment Variables

Tool to batch remove environment variables from a Vercel project.

Buy Domains

Tool to purchase multiple domains through Vercel's domain registrar.

Buy Single Domain

Tool to purchase a domain through Vercel's domain registrar.

Check Artifact Exists

Tool to check if a cache artifact exists by its hash.

Check Domain Availability

Tool to check if a domain is available for registration.

Check Domain Price

Check pricing for a domain including purchase, renewal, and transfer costs.

Create Auth Token

Tool to create a new authentication token.

Create DNS Record

Tool to create a new DNS record for a domain.

Create Edge Config

Creates a new Edge Config for storing key-value data at the edge.

Create Edge Config Token

Create a read access token for a specific Edge Config.

Create new deployment

Tool to create a new deployment.

Create or Transfer Domain

Tool 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 Request

Tool to create a project transfer request.

Create Shared Environment Variable

Tool to create one or more shared environment variables in Vercel.

Create Webhook

Tool to create a webhook for receiving notifications about Vercel events.

Dangerously Delete By Source Images

Tool to dangerously delete edge cache by source image URLs.

Dangerously Delete Cache By Tags

Tool to dangerously delete edge cache by tags.

Delete Vercel Alias

Tool to delete an alias from Vercel.

Delete Auth Token

Tool to delete an authentication token.

Purge All Data Cache

Tool 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 Record

Tool to delete a DNS record from a domain.

Delete Domain

Tool to remove a domain by name from Vercel.

Delete Edge Config

Tool 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 Variable

Tool to remove an environment variable from a Vercel project.

Delete Rolling Release Configuration

Tool to delete rolling release configuration for a project.

Delete Shared Env Variable

Tool to delete one or more shared environment variables.

Delete Vercel Webhook

Delete a webhook by its unique ID to stop receiving event notifications.

Download Cache Artifact

Download a cache artifact from Vercel's Remote Cache by its hash.

Edit Project Environment Variable

Tool to edit an environment variable in a Vercel project.

Filter Project Environment Variables

Tool to retrieve environment variables of a Vercel project by id or name.

Get Active Attack Status

Tool to read active attack data from Vercel Firewall for a specific project.

Get Vercel Alias

Tool to retrieve information about a Vercel alias by ID or alias name.

Query Artifact Information

Tool to query information about artifacts by their hashes.

Get Auth Token Metadata

Tool to retrieve metadata for an authentication token.

Get Authenticated User

Tool to get the authenticated user's profile.

Get Bulk Domain Availability

Tool to check availability for multiple domains at once.

Get Remote Caching Status

Tool to get the status of Remote Caching for the principal.

Get SSL/TLS Certificates

Tool to retrieve SSL/TLS certificates for the authenticated user or team.

Get Integration Configurations

Tool to get configurations for the authenticated user or team.

Get Contact Info Schema

Tool to retrieve the contact information schema for a domain's top-level domain (TLD).

Get Deployment by ID or URL

Tool to get a deployment by ID or URL.

Get Deployment Events

Tool to get deployment events for a specific Vercel deployment by ID or URL.

Get Deployment File Contents

Retrieve the contents of a specific file from a Vercel deployment.

Get Deployment Runtime Logs

Tool to retrieve runtime logs for a specific Vercel deployment by project and deployment ID.

Get Deployments

Tool to list deployments from Vercel.

Get Domain Information

Tool to retrieve complete information for a single domain.

Get Domain Configuration

Tool to get a domain's configuration details from Vercel.

Get Domain Transfer Info

Tool to get information required to transfer a domain to Vercel.

Get All Drains

Tool to retrieve a list of all drains.

Get Edge Config

Tool to retrieve detailed information about a specific Edge Config by ID.

Get Edge Config Backup

Tool to retrieve a specific backup version of an Edge Config.

Get Edge Config Item

Tool to retrieve a specific item within an Edge Config.

Get Edge Config Schema

Tool to retrieve the JSON schema of a specific Edge Config.

Get Edge Config Token

Tool to retrieve details of a specific token associated with an Edge Config.

Get Firewall Configuration

Tool to retrieve firewall configuration for a Vercel project.

List Git Namespaces

Tool to list Git namespaces (organizations/users) by provider.

Find Project by ID or Name

Tool to find a project by ID or name with comprehensive details.

Get Project Domain

Tool to retrieve details about a specific domain attached to a Vercel project.

List Project Domains

Tool to retrieve all domains attached to a Vercel project.

Get Project Environment Variable

Tool to retrieve the decrypted value of an environment variable from a Vercel project.

Get Projects

Tool to retrieve a list of projects from Vercel.

List Promote Aliases

Tool to get a list of aliases with status for the current promote operation.

Get Rolling Release

Tool to retrieve active rolling release information for a Vercel project.

Get Rolling Release Billing Status

Tool to retrieve the rolling release billing status for a Vercel project.

Get Rolling Release Config

Tool to get rolling release configuration for a Vercel project.

Get Shared Environment Variable

Tool to retrieve the decrypted value of a Shared Environment Variable by id.

List Shared Environment Variables

Tool to list all shared environment variables for a team.

Get Team Details

Retrieves detailed information about a specific Vercel team by its ID or slug.

Get All Teams

Tool to list all teams accessible to the authenticated user with detailed information.

Get TLD Info

Tool to get information about a specific top-level domain (TLD).

Get TLD Price

Tool to get pricing information for a specific top-level domain (TLD).

List User Events

Tool to list user events.

Get Webhook

Tool to retrieve details of a specific webhook by ID.

Invalidate Cache By Source Images

Tool to invalidate edge cache by source image URLs.

Invalidate Cache By Tags

Tool to invalidate edge cache by tags.

List Vercel Aliases

Tool to list aliases from Vercel API.

List Auth Tokens

Tool to list authentication tokens.

List Deployment Aliases

Tool to list all aliases assigned to a specific deployment.

List Deployment Checks

Tool to retrieve a list of checks for a specific deployment.

List Deployment Files

Tool to list all files in a specific deployment.

List DNS Records

Tool to list existing DNS records for a domain.

Get Domains

Tool to list all domains from Vercel.

Get Edge Config Backups

Tool to retrieve backups for a specific Edge Config.

Get Edge Config Items

Tool to retrieve all items from a specific Edge Config.

Get Edge Configs

Tool to retrieve all Edge Configs for an account or team.

Get Edge Config Tokens

Tool to get all tokens of an Edge Config.

Get Firewall Events by Project

Retrieve firewall events and security actions for a specific Vercel project.

Get Integration Log Drains

Retrieves a list of Integration log drains for a team or account.

Get Project Custom Environments

Tool to retrieve custom environments for a Vercel project.

Get Project Members

Tool to list all members of a Vercel project.

Get Supported TLDs

Tool to retrieve all TLDs (top-level domains) supported by Vercel for domain registration.

Get Team Members

Tool to list all members of a Vercel team.

Get List of Webhooks

Tool to retrieve a list of all webhooks for the authenticated account or team.

Move Project Domain

Tool to move a domain from one Vercel project to another.

Pause Vercel Project

Tool to pause a Vercel project.

Read Firewall Configuration

Tool to read firewall configuration for a Vercel project.

Record Artifacts Cache Events

Tool to record artifacts cache usage events.

Remove Domain from Project

Tool to remove a domain from a Vercel project.

Update Vercel Firewall Configuration

Tool to update firewall configuration for a Vercel project.

Request Delete User Account

Tool to initiate user account deletion on Vercel.

Promote Deployment to Production

Tool to promote a deployment to production by pointing all production domains for a project to the given deployment.

Search Git Repositories

Tool to search and list Git repositories linked to a namespace by provider.

Test Drain Configuration

Tool to validate a drain delivery configuration by sending a test request.

Transfer In Domain

Tool to transfer a domain to Vercel from another registrar.

Unlink Shared Environment Variable

Tool to disconnect a shared environment variable from a Vercel project.

Unpause Vercel Project

Tool to unpause a specific project by its ID.

Update Attack Challenge Mode

Tool to update Attack Challenge mode for a Vercel project.

Update DNS Record

Tool to update an existing DNS record.

Patch Domain

Tool to update or move an apex domain on Vercel.

Update Edge Config

Tool to update an Edge Config by changing its slug.

Update Edge Config Items

Tool to update items within a specific Edge Config.

Update Edge Config Schema

Tool to update the JSON Schema for an Edge Config.

Update Firewall Configuration

Tool 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 Cache

Tool to update the data cache feature for a Vercel project.

Update Project Domain

Tool to update a project domain in Vercel.

Update Project Protection Bypass

Tool to update protection bypass for automation on a Vercel project.

Update Shared Env Variable

Tool to update one or more shared environment variables.

Update Project Static IPs

Tool to configure Static IPs for a Vercel project.

Update Team

Tool to update a Vercel team's configuration.

Update URL Protection Bypass

Tool to update the protection bypass for a URL.

Upload Cache Artifact

Tool to upload a cache artifact to Vercel.

Upload Deployment File

Tool to upload deployment files to Vercel.

Verify Project Domain

Attempts to verify a project domain by checking if DNS challenges are correctly configured.

FRAMEWORKS

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

Vercel AI SDK

Use Vercel MCP with Vercel AI SDK

Mastra AI

Use Vercel MCP with Mastra AI

CrewAI

Use Vercel MCP with CrewAI

OpenCode

Use Vercel MCP with OpenCode

VS Code

Use Vercel MCP with VS Code

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

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.

Ably

Api Key

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.

FAQ

Frequently asked questions

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.

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

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.

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.

Start with Vercel.It takes 30 seconds.

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

Start building

Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREE BOOK A DEMO

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

Harsha Gaddipati

Co-founder, Slashy

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's immensely helped keep new users on the platform.

Abhi Arya

Co-founder, Opennote

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

Nirman Dave

CEO, Zams

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

Ryan Yu

Founder, Extra Thursday

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

Tomisin Jenrola

Founder & CEO, SwarmZero

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.

Jerome Leclanche

Co-Founder, Ingram Technologies