← Back to all apps

Vercel

Developer toolsby Vercel
Open in ChatGPTOpen in ClaudeWebsite

Vercel MCP is Vercel’s official MCP server, allowing you to search and navigate documentation, manage projects and deployments, and analyze deployment logs—all in one place.

18ChatGPT Tools
7Claude Tools
VercelDeveloper
Developer toolsCategory

Use Cases

code

Available Tools

Add Toolbar Reaction

add_toolbar_reaction
Full Description

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

Parameters (4 required)
Required
emojistring

The emoji to add as a reaction (e.g. 👍)

messageIdstring

The message ID to react to

teamIdstring

The team ID to get the deployment events for. Alternatively the team slug can be used. Team IDs start with "team_". If you do not know the team ID or slug, it can be found through these mechanism: - Read the file .vercel/project.json if it exists and extract the orgId - Use the `list_teams` tool

threadIdstring

The thread ID containing the message

Change Toolbar Thread Resolve Status

change_toolbar_thread_resolve_status
Full Description

Change the resolve status of a toolbar thread. Can be used to mark a thread as resolved or unresolve a previously resolved thread.

Parameters (3 required)
Required
resolvedboolean

Set to true to resolve the thread, false to unresolve it

teamIdstring

The team ID to get the deployment events for. Alternatively the team slug can be used. Team IDs start with "team_". If you do not know the team ID or slug, it can be found through these mechanism: - Read the file .vercel/project.json if it exists and extract the orgId - Use the `list_teams` tool

threadIdstring

The thread ID to update

Check Domain Availability And Price

check_domain_availability_and_price
Full Description

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

Parameters (1 required)
Required
namesarray

Array of domain names to check availability for (e.g., ["example.com", "test.org"])

Deploy To Vercel

deploy_to_vercel
Full Description

Deploy the current project to Vercel

Edit Toolbar Message

edit_toolbar_message
Full Description

Edit an existing message in a toolbar thread.

Parameters (4 required)
Required
markdownstring

The updated message content in markdown format

messageIdstring

The message ID to edit

teamIdstring

The team ID to get the deployment events for. Alternatively the team slug can be used. Team IDs start with "team_". If you do not know the team ID or slug, it can be found through these mechanism: - Read the file .vercel/project.json if it exists and extract the orgId - Use the `list_teams` tool

threadIdstring

The thread ID containing the message

Get Access To Vercel Url

get_access_to_vercel_url
Full Description

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.

Parameters (1 required)
Required
urlstring

The full URL of the Vercel deployment (e.g. "https://myapp.vercel.app").

Get Deployment

get_deployment
Full Description

Get a specific deployment by ID or URL.

Parameters (2 required)
Required
idOrUrlstring

The unique identifier or hostname of the deployment.

teamIdstring

The team ID to get the deployment events for. Alternatively the team slug can be used. Team IDs start with "team_". If you do not know the team ID or slug, it can be found through these mechanism: - Read the file .vercel/project.json if it exists and extract the orgId - Use the `list_teams` tool

Get Deployment Build Logs

get_deployment_build_logs
Full Description

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.

Parameters (2 required, 1 optional)
Required
idOrUrlstring

The unique identifier or hostname of the deployment.

teamIdstring

The team ID to get the deployment events for. Alternatively the team slug can be used. Team IDs start with "team_". If you do not know the team ID or slug, it can be found through these mechanism: - Read the file .vercel/project.json if it exists and extract the orgId - Use the `list_teams` tool

Optional
limitnumber

Maximum number of log lines to return. Defaults is 100.

Default: 100

Get Project

get_project
Full Description

Get a specific project in Vercel

Parameters (2 required)
Required
projectIdstring

The project ID to get the deployment events for. Alternatively the project slug can be used. Project IDs start with "prj_". If you do not know the project ID or slug, it can be found through these mechanism: - Read the file .vercel/project.json if it exists and extract the projectId - Use the `list_projects` tool

teamIdstring

The team ID to get the deployment events for. Alternatively the team slug can be used. Team IDs start with "team_". If you do not know the team ID or slug, it can be found through these mechanism: - Read the file .vercel/project.json if it exists and extract the orgId - Use the `list_teams` tool

Get Runtime Logs

get_runtime_logs
Full Description

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.

Parameters (2 required, 10 optional)
Required
projectIdstring

The project ID to get runtime logs for.

teamIdstring

The team ID to get the deployment events for. Alternatively the team slug can be used. Team IDs start with "team_". If you do not know the team ID or slug, it can be found through these mechanism: - Read the file .vercel/project.json if it exists and extract the orgId - Use the `list_teams` tool

Optional
deploymentIdstring

Filter logs to a specific deployment ID or URL.

environmentstring

Filter by environment: "production" or "preview".

Options:productionpreview
levelarray

Filter by log level(s). Can specify multiple levels.

limitnumber

Maximum number of log entries to return. Defaults to 50, max 100.

querystring

Full-text search query to filter logs.

requestIdstring

Filter by specific request ID.

sincestring

Start time - ISO format or relative time (e.g., "1h", "30m", "7d"). Defaults to 24 hours ago.

sourcearray

Filter by source type(s). Can specify multiple sources.

statusCodestring

Filter by HTTP status code (e.g., "500", "4xx").

untilstring

End time - ISO format or relative time. Defaults to now.

Get Toolbar Thread

get_toolbar_thread
Full Description

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

Parameters (2 required)
Required
teamIdstring

The team ID to get the deployment events for. Alternatively the team slug can be used. Team IDs start with "team_". If you do not know the team ID or slug, it can be found through these mechanism: - Read the file .vercel/project.json if it exists and extract the orgId - Use the `list_teams` tool

threadIdstring

The thread ID to retrieve

List Deployments

list_deployments
Full Description

List all deployments for a project

Parameters (2 required, 2 optional)
Required
projectIdstring

The project ID to list deployments for.

teamIdstring

The team ID to list deployments for.

Optional
sincenumber

Get deployments created after this timestamp.

untilnumber

Get deployments created before this timestamp.

List Projects

list_projects
Full Description

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.

Parameters (1 required)
Required
teamIdstring

The team ID to get the deployment events for. Alternatively the team slug can be used. Team IDs start with "team_". If you do not know the team ID or slug, it can be found through these mechanism: - Read the file .vercel/project.json if it exists and extract the orgId - Use the `list_teams` tool

List Teams

list_teams
Full Description

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

List Toolbar Threads

list_toolbar_threads
Full Description

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.

Parameters (1 required, 7 optional)
Required
teamIdstring

The team ID to get the deployment events for. Alternatively the team slug can be used. Team IDs start with "team_". If you do not know the team ID or slug, it can be found through these mechanism: - Read the file .vercel/project.json if it exists and extract the orgId - Use the `list_teams` tool

Optional
branchstring

Filter by branch name

limitnumber

Maximum number of results to return. Defaults to 20.

offsetnumber

Pagination offset

pagestring

Filter by page path (e.g. /docs) or glob (e.g. /docs*)

projectIdstring

Filter by project ID

searchstring

Search text in comments

statusstring

Filter by status. Defaults to unresolved.

Options:resolvedunresolved

Reply To Toolbar Thread

reply_to_toolbar_thread
Full Description

Add a reply message to an existing toolbar thread.

Parameters (3 required)
Required
markdownstring

The message content in markdown format

teamIdstring

The team ID to get the deployment events for. Alternatively the team slug can be used. Team IDs start with "team_". If you do not know the team ID or slug, it can be found through these mechanism: - Read the file .vercel/project.json if it exists and extract the orgId - Use the `list_teams` tool

threadIdstring

The thread ID to reply to

Search Vercel Documentation

search_vercel_documentation
Full Description

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
Parameters (1 required, 1 optional)
Required
topicstring

Topic to focus the documentation search on (e.g., 'routing', 'data-fetching').

Optional
tokensnumber

Maximum number of tokens to include in the result. Default is 2500.

Default: 2500

Web Fetch Vercel Url

web_fetch_vercel_url
Full Description

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.

Parameters (1 required)
Required
urlstring

The full URL of the Vercel deployment including the path (e.g. "https://myapp.vercel.app/my-page").

Links

WebsitePrivacy PolicyTerms of Service