How to integrate Vercel MCP with Claude Agent SDK

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Vercel Logo
Claude Agent SDK Logo
divider

Introduction

This guide walks you through connecting Vercel to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Vercel agent that can deploy latest changes to my project, add api key as production environment variable, check if mydomain.com is available for purchase, delete failed deployment by id through natural language commands.

This guide will help you understand how to give your Claude Agent 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.

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Vercel
  • Configure an AI agent that can use Vercel as a tool
  • Run a live chat session where you can ask the agent to perform Vercel operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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.
Check Cache 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 PriceTool to check the price for a domain before purchase.
Create Auth TokenTool to create a new authentication token.
Create Edge ConfigTool to create a new edge config for a vercel project.
Create Edge Config TokenTool to create a new token for a specific edge config.
Create new deploymentTool to create a new deployment.
Delete Auth TokenTool to delete an authentication token.
Delete DeploymentTool to delete a specific deployment by its unique id.
Delete Edge Config TokensTool to delete tokens associated with a specific edge config.
Delete Environment VariableTool to delete a specific environment variable from a project.
Delete Vercel ProjectTool to delete a specific project by its id or name.
Deploy Edge FunctionDeploy edge functions to vercel.
Get Auth Token MetadataTool to retrieve metadata for an authentication token.
Get deployment detailsTool to retrieve detailed information about a specific deployment.
Get Deployment EventsTool to retrieve events related to a specific deployment.
Get Deployment LogsTool to retrieve logs for a specific vercel deployment.
Get Domain Transfer InfoTool to get information required to transfer a domain to vercel.
Get Edge ConfigTool to retrieve details of a specific edge config.
Get Edge Config ItemTool to retrieve a specific item within an edge config.
Get Edge Config TokenTool to retrieve details of a specific token associated with an edge config.
Get Vercel ProjectTool to retrieve information about a vercel project by id or name.
List Vercel AliasesTool to list all aliases for the authenticated user or team.
List All DeploymentsTool to list all deployments.
List Auth TokensTool to list authentication tokens.
List Deployment ChecksTool to retrieve a list of checks for a specific deployment.
List Edge Config ItemsTool to retrieve a list of items within a specific edge config.
List Edge ConfigsTool to list all edge configs.
List Edge Config TokensTool to retrieve a list of tokens for a specific edge config.
List Environment VariablesTool to list environment variables for a specific project.
List All TeamsTool to list all teams accessible to the authenticated user.
Update Edge ConfigTool to update an existing edge config.
Update Edge Config ItemsTool to update items within a specific edge config.
Update Vercel ProjectTool to update an existing project.

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

What is Tool Router?

Composio's Tool Router 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 Tool Router

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

How the Tool Router works

The Tool Router 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:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Vercel account
  • Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • 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 dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The load_dotenv() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Vercel functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Vercel
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["vercel"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Vercel
  • The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Vercel tools via Composio.",
    max_turns=10
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Vercel
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

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

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Vercel
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["vercel"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Vercel tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Vercel through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Vercel MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Vercel MCP with OpenAI Agents SDK

Google ADK

Google ADK

Use Vercel MCP with Google ADK

LangChain

LangChain

Use Vercel MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Vercel MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Vercel MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Vercel MCP with LlamaIndex

CrewAI

CrewAI

Use Vercel MCP with CrewAI

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 Claude Agent SDK?

Yes, you can. Claude Agent SDK 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
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
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.

Book a call↗Get started for free