Tools
The Vercel MCP server provides the following MCP tools. To enhance security, enable human confirmation for tool execution and exercise caution when using Vercel MCP alongside other servers to prevent prompt injection attacks.
| Name | Description | Parameters | Sample prompt |
|---|---|---|---|
| search_documentation | Search Vercel documentation for specific topics and information | topic (string, required): Topic to focus the documentation search on (e.g., 'routing', 'data-fetching')tokens (number, optional, default: 2500): Maximum number of tokens to include in the result | "How do I configure custom domains in Vercel?" |
| Name | Description | Parameters | Sample prompt |
|---|---|---|---|
| list_teams | List all teams that include the authenticated user as a member | None | "Show me all the teams I'm part of" |
| list_projects | List all Vercel projects associated with a user | teamId (string, required): The team ID to list projects 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 | "Show me all projects in my personal account" |
| get_project | Retrieve detailed information about a specific project including framework, domains, and latest deployment | projectId (string, required): The project ID to get project details 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 toolteamId (string, required): The team ID to get project details 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 details about my next-js-blog project" |
| Name | Description | Parameters | Sample prompt |
|---|---|---|---|
| list_deployments | List deployments associated with a specific project with creation time, state, and target information | projectId (string, required): The project ID to list deployments forteamId (string, required): The team ID to list deployments forsince (number, optional): Get deployments created after this timestampuntil (number, optional): Get deployments created before this timestamp | "Show me all deployments for my blog project" |
| get_deployment | Retrieve detailed information for a specific deployment including build status, regions, and metadata | idOrUrl (string, required): The unique identifier or hostname of the deploymentteamId (string, required): 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 details about my latest production deployment for the blog project" |
| 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 | idOrUrl (string, required): The unique identifier or hostname of the deploymentlimit (number, optional, default: 100): Maximum number of log lines to return. Defaults is 100teamId (string, required): 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 | "Show me the build logs for the failed deployment" |
| Name | Description | Parameters | Sample prompt |
|---|---|---|---|
| check_domain_availability_and_price | Check if domain names are available for purchase and get pricing information | names (array, required): Array of domain names to check availability for (e.g., ['example.com', 'test.org']) | "Check if mydomain.com is available" |
| buy_domain | Purchase a domain name with registrant information | name (string, required): The domain name to purchase (e.g., example.com)expectedPrice (number, optional): The price you expect to be charged for the purchaserenew (boolean, optional, default: true): Whether the domain should be automatically renewedcountry (string, required): The country of the domain registrant (e.g., US)orgName (string, optional): The company name of the domain registrantfirstName (string, required): The first name of the domain registrantlastName (string, required): The last name of the domain registrantaddress1 (string, required): The street address of the domain registrantcity (string, required): The city of the domain registrantstate (string, required): The state/province of the domain registrantpostalCode (string, required): The postal code of the domain registrantphone (string, required): The phone number of the domain registrant (e.g., +1.4158551452)email (string, required): The email address of the domain registrant | "Buy the domain mydomain.com" |
| Name | Description | Parameters | Sample prompt |
|---|---|---|---|
| get_access_to_vercel_url | Creates a temporary shareable link that grants access to protected Vercel deployments | url (string, required): The full URL of the Vercel deployment (e.g. 'https://myapp.vercel.app') | "myapp.vercel.app is protected by auth. Please create a shareable link for it" |
| web_fetch_vercel_url | Allows agents to directly fetch content from a Vercel deployment URL (with authentication if required) | url (string, required): The full URL of the Vercel deployment including the path (e.g. 'https://myapp.vercel.app/my-page') | "Make sure the content from my-app.vercel.app/api/status looks right" |
| Name | Description | Parameters | Sample prompt |
|---|---|---|---|
| use_vercel_cli | Instructs the LLM to use Vercel CLI commands with --help flag for information | command (string, optional): Specific Vercel CLI command to runaction (string, required): What you want to accomplish with Vercel CLI | "Help me deploy this project using Vercel CLI" |
| deploy_to_vercel | Deploy the current project to Vercel | None | "Deploy this project to Vercel" |
Was this helpful?