Vercel

com.pulsemcpPublished by pulsemcp.comv0.1.3Updated Oct 24, 2026

MCP server for Vercel — manage deployments and view build and runtime application logs.

The publisher's own server: Agent Permissions Index

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Local MCP server for Vercel that lets an assistant list, inspect, create, promote, roll back and delete deployments and read build and runtime logs.

What you can do
  • List and inspect deployments and projects, with filtering by project, target and state
  • Create, cancel, delete, promote and roll back deployments
  • Read build logs (events) for a deployment
  • Query runtime application logs with time range, search, level, source and status code filters
  • Limit the assistant to read-only or read-write tool groups
When to use it
Useful when you deploy to Vercel and want an assistant to check deployment status, debug failed builds or runtime errors, or promote and roll back releases without leaving the chat.
Requirements
Runs locally via npx with Node.js 18 or newer. Requires a Vercel account and an API token in VERCEL_TOKEN. Optional VERCEL_TEAM_ID or VERCEL_TEAM_SLUG scopes operations to a team, and VERCEL_ENABLED_TOOLGROUPS selects the readonly or readwrite tool groups. Network access to the Vercel REST API is needed.
Before you install
The token in VERCEL_TOKEN grants access to your Vercel account or team. Write tools can create, cancel, delete, promote and roll back deployments, and promotion or rollback changes what serves production traffic. Set VERCEL_ENABLED_TOOLGROUPS=readonly to block write operations. Runtime log retention depends on your plan.

Installation

In SourceWeft

  1. Open Vercel in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Vercel MCP Server

An MCP server for managing Vercel deployments and viewing application runtime logs through the Vercel REST API.

Highlights

  • Deployment Management - List, inspect, create, cancel, delete, promote, and rollback deployments
  • Build & Runtime Logs - View build logs (events) and runtime application logs for debugging
  • Fine-grained Access Control - Enable readonly or readwrite tool groups via environment variables
  • Team Support - Scope operations to a specific Vercel team

Capabilities

Tools

ToolGroupDescription
list_deploymentsreadonlyList deployments with filtering by project, target, and state
get_deploymentreadonlyGet detailed deployment information by ID or URL
list_projectsreadonlyList projects in the account/team
get_deployment_eventsreadonlyGet build logs for a deployment
get_runtime_logsreadonlyGet runtime application logs with filtering
create_deploymentreadwriteCreate a new deployment or redeploy
cancel_deploymentreadwriteCancel an in-progress deployment
delete_deploymentreadwriteDelete a deployment permanently
promote_deploymentreadwritePromote a deployment to production
rollback_deploymentreadwriteRollback to a previous deployment

Setup

Prerequisites

Configuration

VariableRequiredDescription
VERCEL_TOKENYesVercel API token
VERCEL_TEAM_IDNoTeam ID for team-scoped operations
VERCEL_TEAM_SLUGNoTeam URL slug (alternative to team ID)
VERCEL_ENABLED_TOOLGROUPSNoComma-separated tool groups: readonly, readwrite (default: all)

Manual Setup

bash
# Clone the repositorygit clone https://github.com/pulsemcp/mcp-servers.gitcd mcp-servers/experimental/vercel
# Install dependenciesnpm install
# Buildnpm run build
# Set environment variablesexport VERCEL_TOKEN="your-token-here"
# Runnpm start

Usage Tips

  • Use list_projects first to find project IDs needed by promote_deployment, rollback_deployment, and get_runtime_logs
  • Runtime log retention varies by plan: Hobby=1h, Pro=1d, Enterprise=3d (up to 30d with Observability Plus)
  • Use get_runtime_logs with since/until to query historical logs, search to find specific errors, and level/source to filter results
  • Set VERCEL_ENABLED_TOOLGROUPS=readonly to prevent any write operations
  • Use list_deployments with the state filter to quickly find failed or in-progress deployments

Examples

Check deployment status

"What's the status of my latest deployments?"

Uses list_deployments to show recent deployments with their states.

Debug a failed build

"Show me the build logs for deployment dpl_abc123"

Uses get_deployment_events to display the build output and error messages.

Promote a preview to production

"Promote deployment dpl_abc123 to production for project prj_xyz789"

Uses promote_deployment to make a preview deployment serve production traffic.

View runtime errors

"Show me the runtime logs for my-app's latest deployment"

Uses list_projects to find the project ID, then get_runtime_logs to show recent application logs.

Search for specific errors in logs

"Find all 500 errors in the last 24 hours for my-app"

Uses get_runtime_logs with statusCode: 500 and since set to 24 hours ago to filter server errors.

Debug edge function issues

"Show me warning and error logs from edge functions for dpl_abc123"

Uses get_runtime_logs with source: "edge-function" and level: "error" to narrow down issues.

Development

bash
# Install dependenciesnpm install
# Buildnpm run build
# Run functional testsnpm test
# Run integration testsnpm run test:integration
# Run manual tests (requires .env with VERCEL_TOKEN)npm run test:manual
# Lintnpm run lint

Source: experimental/vercel/README.md at commit 0ed34de

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.3LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Vercel integrations