# How to connect Vercel MCP to Claude Cowork

```json
{
  "title": "How to connect Vercel MCP to Claude Cowork",
  "toolkit": "Vercel MCP",
  "toolkit_slug": "vercel_mcp",
  "framework": "Claude Cowork",
  "framework_slug": "claude-cowork",
  "url": "https://composio.dev/toolkits/vercel_mcp/framework/claude-cowork",
  "markdown_url": "https://composio.dev/toolkits/vercel_mcp/framework/claude-cowork.md",
  "updated_at": "2026-08-25T05:41:14.841Z"
}
```

## Introduction

Cowork is Anthropic's AI agent for knowledge work. Think of it as Claude Code for everything else. It works autonomously with your computer, local files, and applications to accomplish complex tasks.
This guide walks you through the easiest and most secure way to connect your Vercel account to Cowork via Composio Connect, enabling it to list recent deployments for your project, get deployment logs for commit abc123, create a new deployment from branch, and more such actions on your behalf without compromising your account security.

## Also integrate Vercel MCP with

- [ChatGPT Work](https://composio.dev/toolkits/vercel_mcp/framework/chatgpt)
- [Hermes](https://composio.dev/toolkits/vercel_mcp/framework/hermes-agent)

## Connect Vercel MCP to Claude Cowork

### Connecting Vercel to Claude Cowork
1. Open Customize
In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.
2. Add the Composio MCP server
Click Add custom connector and paste in the Composio MCP server URL:

```bash
https://connect.composio.dev/mcp
```

## What is Claude Cowork?

Claude Cowork is Anthropic's agent for general knowledge work. It can use your computer, files, and connected applications to complete longer-running tasks across your work tools.
With Composio Connect, Cowork can securely access apps like Vercel through MCP without you sharing account credentials directly with the agent.

## 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 so your agent can perform Vercel operations on your behalf.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `VERCEL_MCP_ADD_TOOLBAR_REACTION` | Add toolbar reaction | Add an emoji reaction to a message in a toolbar thread. |
| `VERCEL_MCP_BUY_ADDON` | Buy addon | Executes a Vercel add-on purchase (currently only "siem"), by integer quantity, previously quoted by get_purchase_quote — quoting first is REQUIRED; this tool rejects un-quoted calls. Get the quote, present it to the user for explicit approval (use a structured question tool such as AskUserQuestion when available), then call with confirm:true, the quote's idempotencyKey, and the same parameters. The team must be on the Flex plan. No price quote exists for add-ons; the charge is non-refundable. The quote returns required disclosures the assistant must relay before approval: the payment method (default card on file), that taxes/fees may apply on top of the price, the item terms (Flex plan required, billed on the next invoice), and a full-terms link. |
| `VERCEL_MCP_BUY_CREDITS` | Buy credits | Executes a prepaid Vercel credits purchase (v0, AI Gateway, or Vercel Agent) previously quoted by get_purchase_quote — quoting first is REQUIRED; this tool rejects un-quoted calls. Get the quote, present it to the user for explicit approval (use a structured question tool such as AskUserQuestion when available), then call with confirm:true, the quote's idempotencyKey, and the same parameters. When the user has not named an amount, offer quick-picks — $10, $25, $50, or $100 — or let them enter any custom amount ($1–$1000); do not just quote the range. Some credit types require a plan: Vercel Agent credits require the team to be on Vercel Pro (use buy_pro first), and v0 credits require a paid v0 plan (set up at v0.dev); AI Gateway credits have no plan prerequisite. If the required plan is missing the purchase is rejected (nothing is charged) with guidance. The charge is immediate and non-refundable. The quote returns required disclosures the assistant must relay before approval: the payment method (default card on file), that taxes/fees may apply on top of the base price, the item terms (credits expire in one year), and a full-terms link. |
| `VERCEL_MCP_BUY_DOMAIN` | Buy domain | Executes a single-domain registration previously quoted by get_purchase_quote (product:domain) — quoting first is REQUIRED; this tool rejects un-quoted calls. Get the quote, present it to the user for explicit approval (use a structured question tool such as AskUserQuestion when available), then call with confirm:true, the quote's idempotencyKey, the expectedPrice and years from the quote, and the full registrant contact to execute the non-refundable purchase. Vercel stores no reusable registrant profile, so contact details must be supplied each time. The quote returns required disclosures the assistant must relay before approval: the payment method (default card on file), that taxes/fees may apply on top of the price, the item terms (non-refundable), and, when auto-renew is on, the recurring-charge terms in disclosures.subscription (renews automatically each term at the then-current price until auto-renew is turned off), plus a full-terms link. |
| `VERCEL_MCP_BUY_PRO` | Buy pro | Executes a Vercel Pro upgrade previously quoted by get_purchase_quote — quoting first is REQUIRED; this tool rejects un-quoted calls. Get the quote, present it to the user for explicit approval (use a structured question tool such as AskUserQuestion when available), then call with confirm:true, the quote's idempotencyKey, and the same parameters. This starts RECURRING Pro billing immediately at the standard Pro price. The quote returns required disclosures the assistant must relay before approval: the payment method (default card on file), that taxes/fees may apply on top of the price, the subscription terms (recurring monthly charge, no trial, cancel anytime in billing settings), and a full-terms link. |
| `VERCEL_MCP_CHANGE_TOOLBAR_THREAD_RESOLVE_STATUS` | Change toolbar thread resolve status | Change the resolve status of a toolbar thread. Can be used to mark a thread as resolved or unresolve a previously resolved thread. |
| `VERCEL_MCP_CHECK_DOMAIN_AVAILABILITY_AND_PRICE` | Check domain availability and price | Check if domain names are available for purchase and get pricing information |
| `VERCEL_MCP_CREATE_GIT_PROJECT` | Create git project | Preferred when the intended source is pushed to an accessible remote repository's production branch. Create a Vercel project linked to that repository, or reuse the existing project already linked to it, to automatically deploy changes on every push. New projects have Vercel Authentication disabled. Creates a preview deployment from the production branch by default; do not ask for deployment confirmation. Use deploy_to_vercel only when no usable remote repository exists or the user explicitly requests a manual file deployment. This prevents new bare projects; it does not reconnect an existing unlinked project with the same name. |
| `VERCEL_MCP_DEPLOY_TO_VERCEL` | Deploy to vercel | Deploy files directly when no usable remote git repository exists or the user explicitly requests a manual file deployment. If the intended source is pushed to a repository's production branch, use create_git_project to automatically deploy changes on every push. Provide the file tree and an explicit target; Vercel auto-detects the framework and builds. |
| `VERCEL_MCP_EDIT_TOOLBAR_MESSAGE` | Edit toolbar message | Edit an existing message in a toolbar thread. |
| `VERCEL_MCP_GET_ACCESS_TO_VERCEL_URL` | Get access to vercel url | Creates a temporary shareable link that bypasses authentication for protected Vercel deployments. When you encounter a Vercel deployment URL (like https://myapp-abc123.vercel.app), you might receive a 403 (Forbidden) error when trying to access it. This tool generates a special URL with a '_vercel_share' parameter that allows temporary access without requiring login credentials. The shareable URL will expire in 23 hours. When you use the returned URL, that URL will redirect and set an auth cookie. If your fetch implementation does not support cookies, use the 'web_fetch_vercel_url' tool instead. |
| `VERCEL_MCP_GET_AGENT_RUN` | Get agent run | Get detailed metadata for a single Agent Run from an eve agent, including events, workflow metadata, usage, and subagent breakout data. Use list_agent_runs first if you need to discover a run ID. |
| `VERCEL_MCP_GET_AGENT_RUN_TRACE` | Get agent run trace | Get the trace for a single Agent Run from an eve agent, including turns, messages, reasoning, tool calls, token usage, and tool input/output when available. Use this for debugging exact agent behavior in production. |
| `VERCEL_MCP_GET_DEPLOYMENT` | Get deployment | Get a specific deployment by ID or URL. |
| `VERCEL_MCP_GET_DEPLOYMENT_BUILD_LOGS` | Get deployment build logs | Get the build logs for a deployment by ID or URL, to investigate why a build failed. Returns the most recent lines by default (where build errors appear). Use errorsOnly to see just the failing lines. Omit since and until for latest logs; use since to narrow the window and omit until when the end should be the current time. |
| `VERCEL_MCP_GET_DOMAIN_ORDER` | Get domain order | Get the status of a domain purchase order returned by buy_domain, to confirm whether the registration completed. |
| `VERCEL_MCP_GET_GIT_DEPLOYMENT_CONTEXT` | Get git deployment context | Lists every Vercel team authorized for the user, including its plan and linked Git projects. If linkedProjects is null, project listing failed for that team. |
| `VERCEL_MCP_GET_PROJECT` | Get project | Get a specific project in Vercel |
| `VERCEL_MCP_GET_PROJECT_DEPLOYMENT_PROTECTION` | Get project deployment protection | Get the effective password protection, Vercel Authentication, and Trusted IP settings for a Vercel project. Password values are never returned. |
| `VERCEL_MCP_GET_PURCHASE_QUOTE` | Get purchase quote | Read-only price quote for a Vercel purchase. NEVER charges. This is the ONLY way to obtain an idempotencyKey — the buy_* tools no longer quote and reject un-quoted calls, so this is the REQUIRED first step before any buy_* tool. It returns the cost (when Vercel exposes one) and an idempotencyKey to pass to the matching buy tool (buy_credits, buy_domain, buy_addon, buy_pro) with confirm:true within 5 minutes to execute the charge. Present the quote to the user for explicit approval (use a structured question tool such as AskUserQuestion when available) before confirming. Products with no API price (add-ons, Pro) return a priceNote and billing URL instead of a number. Every quote includes a disclosures object the assistant must relay to the user before approval: the payment method (default card on file), that taxes/fees may apply on top of the base price, the item terms, and a link to the full terms. |
| `VERCEL_MCP_GET_RUNTIME_ERRORS` | Get runtime errors | Get grouped runtime error clusters for a project (error name, occurrence count, affected routes, sample messages, first/last seen). Use this first to answer "why is production erroring" — it reads a pre-aggregated table and does not time out. For recent windows, pass since like "24h" or "7d" and omit until; until is only needed for historical end times. Max 7-day range. |
| `VERCEL_MCP_GET_RUNTIME_LOGS` | Get runtime logs | Get runtime logs for a project or deployment. Runtime logs show application output (console.log, errors, etc.) from serverless functions and edge functions during execution. Supports filtering by environment, log level, status code, source, time range, and full-text search. For recent windows, pass since like "30m" or "24h" and omit until; until is only needed for historical end times. For wide time ranges, scope to a deploymentId for speed, or use group_by to get counts instead of individual lines. To investigate production errors specifically, prefer get_runtime_errors. |
| `VERCEL_MCP_GET_TOOLBAR_THREAD` | Get toolbar thread | Get a specific toolbar thread by ID, including all messages and context. |
| `VERCEL_MCP_GET_WEB_ANALYTICS` | Get web analytics | Query Web Analytics for a Vercel project. Count mode returns total visitors and pageviews (or custom event count). Aggregate mode groups results over time or by dimensions such as route, requestPath, country, referrerHostname, deviceType, browserName, eventName, flags/, or eventData/. Web Analytics must be enabled for the project. |
| `VERCEL_MCP_IMPORT_CLAUDE_DESIGN_FROM_URL` | Import-claude-design-from-url | Import a design into Vercel from a publicly fetchable URL. The file is a self-contained HTML bundle with all images, fonts, and styles inlined. |
| `VERCEL_MCP_LIST_AGENT_RUN_PROJECTS` | List agent run projects | List projects in a Vercel team that have Agent Runs observability data for agents built with the eve framework, with run counts and average duration rollups. Use this to discover which projects have eve agent activity before drilling into a project. |
| `VERCEL_MCP_LIST_AGENT_RUNS` | List agent runs | List Agent Runs for a Vercel project. Agent Runs are the observability layer for agents built with the eve framework. The response includes summaries, status, model, trigger, token usage, time series, and pagination metadata. Use this to find recent or matching production eve agent runs before fetching detail or trace data. |
| `VERCEL_MCP_LIST_DEPLOYMENTS` | List deployments | List all deployments for a project |
| `VERCEL_MCP_LIST_PROJECTS` | List projects | List all Vercel projects for a user (with a max of 50). Use this to help discover the Project ID of the project that the user is working on. |
| `VERCEL_MCP_LIST_TEAMS` | List teams | List the user's teams. Use this to help discover the Team ID of the teams that the user is part of. |
| `VERCEL_MCP_LIST_TOOLBAR_THREADS` | List toolbar threads | List Vercel toolbar comment threads for a team. Returns unresolved threads by default. Use this to see feedback, comments, or discussions on deployments and previews. |
| `VERCEL_MCP_PAUSE_PROJECT` | Pause project | Pause a Vercel project. Its production deployment will stop serving traffic and return 503 DEPLOYMENT_PAUSED until the project is unpaused. |
| `VERCEL_MCP_REPLY_TO_TOOLBAR_THREAD` | Reply to toolbar thread | Add a reply message to an existing toolbar thread. |
| `VERCEL_MCP_SEARCH_VERCEL_DOCUMENTATION` | Search vercel documentation | Search the Vercel documentation. Use this tool to answer any questions about Vercel’s platform, features, and best practices, including: - Core Concepts: Projects, Deployments, Git Integration, Preview Deployments, Environments - Frontend & Frameworks: Next.js, SvelteKit, Nuxt, Astro, Remix, frameworks configuration and optimization - APIs: REST API, Vercel SDK, Build Output API - Compute: Fluid Compute, Functions, Routing Middleware, Cron Jobs, OG Image Generation, Sandbox, Data Cache - AI: Vercel AI SDK, AI Gateway, MCP, v0 - Performance & Delivery: Edge Network, Caching, CDN, Image Optimization, Headers, Redirects, Rewrites - Pricing: Plans, Spend Management, Billing - Security: Audit Logs, Firewall, Bot Management, BotID, OIDC, RBAC, Secure Compute, 2FA - Storage: Blog, Edge Config |
| `VERCEL_MCP_UNPAUSE_PROJECT` | Unpause project | Unpause a Vercel project so its production deployment can resume serving traffic and consuming metered resources. |
| `VERCEL_MCP_UPDATE_PROJECT_DEPLOYMENT_PROTECTION` | Update project deployment protection | Partially update password protection, Vercel Authentication, and Trusted IPs for a Vercel project. Omitted settings are preserved. Availability depends on the Vercel team plan and caller permissions. |
| `VERCEL_MCP_WEB_FETCH_VERCEL_URL` | Web fetch vercel url | Fetches a Vercel deployment URL and returns the response. This is useful if another web fetch tool returns 401 (Unauthorized) or 403 (Forbidden) for a Vercel URL. Supports accessing deployments protected with Vercel Authentication which the user of this MCP server has access to. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Vercel MCP server connects Claude Cowork to your Vercel account through Composio. Once connected, Cowork can use the available Vercel tools and triggers to complete tasks on your behalf.

## Complete Code

None listed.

## How to build Vercel MCP Agent with another framework

- [ChatGPT Work](https://composio.dev/toolkits/vercel_mcp/framework/chatgpt)
- [Hermes](https://composio.dev/toolkits/vercel_mcp/framework/hermes-agent)

## Related Toolkits

- [Supabase](https://composio.dev/toolkits/supabase) - 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](https://composio.dev/toolkits/codeinterpreter) - 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](https://composio.dev/toolkits/github) - 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.
- [1password](https://composio.dev/toolkits/_1password) - 1Password is a password manager and digital vault for storing logins, secrets, notes, and secure documents. It helps individuals and teams protect credentials, share access safely, and reduce password risk.
- [Ably](https://composio.dev/toolkits/ably) - 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.
- [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses.
- [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure.
- [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure.
- [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction.
- [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting.
- [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache.
- [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence.
- [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place.
- [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines.
- [Authyo](https://composio.dev/toolkits/authyo) - Authyo is a REST API service for passwordless authentication, OTP verification, session management, and transactional notifications. Use it to add secure login flows and user verification without building auth infrastructure from scratch.
- [AWS Marketplace MCP](https://composio.dev/toolkits/aws_marketplace_mcp) - AWS Marketplace MCP provides MCP access to AWS Marketplace's cloud software, data, and services catalog. Use it to discover, compare, and evaluate 30K+ AWS Marketplace listings faster.
- [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure.
- [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code.
- [Bench](https://composio.dev/toolkits/bench) - Bench is a benchmarking tool for automated performance measurement and analysis. It helps you quickly evaluate, compare, and track your systems or workflows.
- [Better stack](https://composio.dev/toolkits/better_stack) - Better Stack is a monitoring, logging, and incident management solution for apps and services. It helps teams ensure application reliability and performance with real-time insights.

## Frequently Asked Questions

### 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 Cowork?

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

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)