← Back to all apps

Overview

Tools Available11
CategoryDeveloper_tools

Search docs and deploy apps

Available Tools

Vercel provides 11 tools that can be used to interact with its services.

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

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

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

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

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

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

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

List Deployments

list_deployments
Full Description

List all deployments for a project

Parameters

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

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.

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

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

Required
urlstring

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