pulsemcp avatar

Vercel

pulsemcp/mcp-servers

Connects to Vercel's platform APIs to manage deployments and monitor logs directly from your MCP client. You get build and runtime application log access without switching to the dashboard, plus deployment management operations. Built by PulseMCP with their focus on minimizing tool chain steps and conversational turns, which means fewer round trips to check deployment status or debug production issues. Reach for this when you're iterating on Vercel projects and want to monitor deploys or investigate errors without context switching. Uses stdio transport and requires Vercel API credentials.

tools
12
auth
Secret needed
transport
STDIO
env vars
4
last updated
Jun 14, 2026

Tools

12 tools

Public tool metadata for what this MCP can expose to an agent.

search_vercel_documentationSearch 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...2 params

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...

Parameters* required
tokensnumber
Maximum number of tokens to include in the result. Default is 2500.default: 2500
topicstring
Topic to focus the documentation search on (e.g., 'routing', 'data-fetching').
deploy_to_vercelDeploy the current project to Vercel

Deploy the current project to Vercel

No parameter schema in public metadata yet.

list_projectsList 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.1 params

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:...
get_projectGet a specific project in Vercel2 params

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...
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:...
list_deploymentsList all deployments for a project4 params

List all deployments for a project

Parameters* required
projectIdstring
The project ID to list deployments for.
sincenumber
Get deployments created after this timestamp.
teamIdstring
The team ID to list deployments for.
untilnumber
Get deployments created before this timestamp.
get_deploymentGet a specific deployment by ID or URL.2 params

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:...
get_deployment_build_logsGet 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.3 params

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.
limitnumber
Maximum number of log lines to return. Defaults is 100.default: 100
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:...
get_runtime_logsGet 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. Us...12 params

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. Us...

Parameters* required
deploymentIdstring
Filter logs to a specific deployment ID or URL.
environmentstring
Filter by environment: "production" or "preview".one of production · preview
levelarray
Filter by log level(s). Can specify multiple levels.
limitnumber
Maximum number of log entries to return. Defaults to 50, max 1000.
projectIdstring
The project ID to get runtime logs for.
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").
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:...
untilstring
End time - ISO format or relative time. Defaults to now.
get_access_to_vercel_urlCreates 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 specia...1 params

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 specia...

Parameters* required
urlstring
The full URL of the Vercel deployment (e.g. "https://myapp.vercel.app").
web_fetch_vercel_urlFetches 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.1 params

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").
list_teamsList the user's teams. Use this to help discover the Team ID of the teams that the user is part of.

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

No parameter schema in public metadata yet.

check_domain_availability_and_priceCheck if domain names are available for purchase and get pricing information1 params

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"])

Sponsors

Configuration

VERCEL_TOKEN*secret

Vercel API token for authentication.

VERCEL_TEAM_ID

Team ID for team-scoped operations.

VERCEL_TEAM_SLUG

Team URL slug for team-scoped operations.

VERCEL_ENABLED_TOOLGROUPS

Comma-separated list of tool groups to enable (readonly, readwrite).

Readme

PulseMCP's MCP Servers

We build reliable servers thoughtfully designed for MCP Client-powered workflows.

Design principles

You can have confidence that any Pulse-branded MCP server was built with these north stars in mind:


View the full README on GitHub

Details

Repository
github.com/pulsemcp/mcp-servers
Category
Cloud & Infrastructure
Package
vercel-platform-mcp-server
Transport
STDIO
Auth
Required
Registry
MCP registry, active

More from pulsemcp

Related Cloud & Infrastructure MCP servers

View all
1xenmcp avatarXenMCP Docker agentxenmcp/docker-agentRead-only MCP server for one Docker host: containers, inspect, logs, stats, events. No exec.4stars
2dsouzaanush avatarHeroku Code MCPdsouzaanush/heroku-code-mcpSearch and execute Heroku Platform API operations1stars
3helm-protocol avatarOpenttt Pothelm-protocol/openttt-mcpCryptographic audit trail for Claude Code workflows — tamper-proof timestamps, IETF TTTPS compliant.1stars
4ofershap avatarDockerofershap/mcp-server-dockerMCP server for Docker — manage containers, images, volumes, and compose services from your IDE1stars
5rog0x avatarDockerrog0x/mcp-docker-toolsDocker container management and Dockerfile analysis1stars
6gleaming-cassata-d41682 avatarLION - Trend Intent MCP + Marketplace Visibility Auditapp.netlify.gleaming-cassata-d41682/lion-mcpx402-paid MCP data: trend feed + visibility audit. USDC/Base. No API key. No PII.0stars