Back to the MCP Gateway catalog

MCP Gateway · Catalog

Vercel icon

Vercel MCP server

Official

Vercel MCP is the official Model Context Protocol server for Vercel, with OAuth and tools that let agents deploy projects, inspect deployments and logs, check domain availability, and search Vercel documentation. Connect it through the Speakeasy MCP Gateway and agents such as Claude, Cursor, and ChatGPT get one governed URL for it, with SSO, RBAC, and a full audit trail.

Developer tools18 toolsAuth: oauth

Behind the MCP Gateway

Run Vercel MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Vercel call inspected and logged.

Deploy on MCP Gateway

Tools · 18

Each tool below can be allowed or denied per team and role at the MCP Gateway, and every call is inspected and logged.

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

deploy_to_vercel

Deploy the current project to Vercel

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.

get_project

Get a specific project in Vercel

list_deployments

List all deployments for a project

get_deployment

Get a specific deployment by ID or URL.

get_deployment_build_logs

Get the build logs of a deployment by deployment ID or URL. Can be used to investigate why a deployment failed. It can work as an infinite stream of logs or as a JSON endpoint depending on the input parameters.

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. Useful for debugging runtime issues, monitoring application behavior, and investigating errors in production.

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.

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.

list_teams

List the user's teams. Use this to help discover the Team ID of the teams that the user is part of.

check_domain_availability_and_price

Check if domain names are available for purchase and get pricing information

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.

get_toolbar_thread

Get a specific toolbar thread by ID, including all messages and context.

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.

reply_to_toolbar_thread

Add a reply message to an existing toolbar thread.

edit_toolbar_message

Edit an existing message in a toolbar thread.

add_toolbar_reaction

Add an emoji reaction to a message in a toolbar thread.

Questions

What is a Vercel MCP server?
A Vercel MCP server exposes Vercel to AI agents as Model Context Protocol tools. Instead of a custom integration per agent, any MCP client can connect to the server and call tools such as search_vercel_documentation or deploy_to_vercel to work with Vercel. The server in this catalog is the official Vercel MCP server, which authenticates with OAuth.
What can you do with Vercel MCP?
Agents can deploy projects, inspect deployments and logs, check domain availability, and search Vercel documentation. The catalog lists 18 tools for this server, including search_vercel_documentation, deploy_to_vercel, and list_projects. The full list with descriptions is on this page.
Why put Vercel MCP behind an MCP gateway?
Connecting the Vercel MCP server directly to each client means a separate credential per developer, no inventory of who can reach Vercel through an agent, and no record of what agents did with it. An MCP gateway sits between every agent and the Vercel server, so sign-in runs through your identity provider, role-based access decides which teams can call which Vercel tools, and every call is inspected and logged in one place. The Speakeasy MCP Gateway applies those controls to Vercel and to every other server in your catalog.
How do you connect Vercel MCP through a gateway?
Add the Vercel server from the Speakeasy MCP catalog and every agent reaches it through one gateway URL, next to the rest of your approved servers. Authentication uses OAuth 2.1 with PKCE and dynamic client registration, sign-in runs through your identity provider, and role-based access controls decide which teams can use which Vercel tools. Every prompt, response, and tool call is inspected and logged at the gateway.
How is this different from an unofficial Vercel MCP?
Community-built Vercel MCP servers wrap the same Vercel surface but are not vendor-maintained, and most authenticate with a static credential that gives an agent everything the credential owner can touch. This catalog lists the official Vercel MCP server, which uses OAuth. Running it behind the Speakeasy MCP Gateway adds SSO, role-based access, and an audit trail of every call.

AI everywhere.

Control here.

Talk to usLearn more