Server Details
An MCP server for Vercel
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- vercel/vercel-mcp-overview
- GitHub Stars
- 0
Available Tools
11 toolscheck_domain_availability_and_priceTry in Inspector
Check if domain names are available for purchase and get pricing information
| Name | Required | Description | Default |
|---|---|---|---|
| names | Yes | Array of domain names to check availability for (e.g., ["example.com", "test.org"]) |
deploy_to_vercelTry in Inspector
Deploy the current project to Vercel
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_access_to_vercel_urlTry in Inspector
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.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The full URL of the Vercel deployment (e.g. "https://myapp.vercel.app"). |
get_deploymentTry in Inspector
Get a specific deployment by ID or URL.
| Name | Required | Description | Default |
|---|---|---|---|
| teamId | Yes | 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 | |
| idOrUrl | Yes | The unique identifier or hostname of the deployment. |
get_deployment_build_logsTry in Inspector
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.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of log lines to return. Defaults is 100. | |
| teamId | Yes | 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 | |
| idOrUrl | Yes | The unique identifier or hostname of the deployment. |
get_projectTry in Inspector
Get a specific project in Vercel
| Name | Required | Description | Default |
|---|---|---|---|
| teamId | Yes | 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 | |
| projectId | Yes | 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 |
list_deploymentsTry in Inspector
List all deployments for a project
| Name | Required | Description | Default |
|---|---|---|---|
| since | No | Get deployments created after this timestamp. | |
| until | No | Get deployments created before this timestamp. | |
| teamId | Yes | The team ID to list deployments for. | |
| projectId | Yes | The project ID to list deployments for. |
list_projectsTry in Inspector
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.
| Name | Required | Description | Default |
|---|---|---|---|
| teamId | Yes | 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_teamsTry in Inspector
List the user's teams. Use this to help discover the Team ID of the teams that the user is part of.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
search_vercel_documentationTry in Inspector
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
| Name | Required | Description | Default |
|---|---|---|---|
| topic | Yes | Topic to focus the documentation search on (e.g., 'routing', 'data-fetching'). | |
| tokens | No | Maximum number of tokens to include in the result. Default is 2500. |
web_fetch_vercel_urlTry in Inspector
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.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The full URL of the Vercel deployment including the path (e.g. "https://myapp.vercel.app/my-page"). |
FAQ
How do I claim this server?
To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:
The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.
What are the benefits of claiming a server?
- Control your server's listing on Glama, including description and metadata
- Receive usage reports showing how your server is being used
- Get monitoring and health status updates for your server
Your Connectors
Sign in to create a connector for this server.