Vercel
Trigger and inspect Vercel deployments and pull build or runtime logs from your agent while you ship previews and production.
Overview
com.pulsemcp/vercel is a MCP server for the Ship phase that manages Vercel deployments and surfaces build and runtime application logs to your agent.
What is this MCP server?
- Manage Vercel deployments and view build plus runtime application logs via MCP
- VERCEL_TOKEN required; optional VERCEL_TEAM_ID and VERCEL_TEAM_SLUG for team scope
- VERCEL_ENABLED_TOOLGROUPS toggles readonly vs readwrite tool groups
- npx vercel-platform-mcp-server stdio package (version 0.1.2)
- Experimental PulseMCP Vercel subfolder—not the official Vercel CLI alone
- Server version 0.1.2
- Environment toggles include VERCEL_ENABLED_TOOLGROUPS values readonly and readwrite
- npm package vercel-platform-mcp-server with stdio transport
What problem does it solve?
Shipping on Vercel means juggling the dashboard for deploy status and logs while the agent lacks live platform context.
Who is it for?
Indie devs deploying SaaS or APIs on Vercel who want agent-assisted deploy checks and log triage during launch week.
Skip if: Teams on Fly, Railway, or raw Kubernetes only, or environments that forbid API tokens in local MCP configs.
What do I get? / Deliverables
Your agent can query deployments and logs with your Vercel token, accelerating launch fixes and preview verification from the MCP client.
- Agent-visible Vercel deployment state and log excerpts
- Configurable readonly or readwrite MCP tool groups
- Faster launch debugging without leaving the MCP-enabled IDE
Recommended MCP Servers
Journey fit
Deployment control and first-pass log review belong in Ship when you are pushing builds and validating launch readiness on Vercel. Launch subphase covers go-live mechanics—promoting previews, checking failed builds, and reading runtime logs before users hit errors.
How it compares
Vercel platform MCP integration, not a local test runner skill or generic cloud Terraform assistant.
Common Questions / FAQ
Who is com.pulsemcp/vercel for?
Solo builders and small teams shipping on Vercel who use Claude Code, Cursor, or similar MCP hosts for deploy and log workflows.
When should I use com.pulsemcp/vercel?
Use it during Ship launch when you need deployment status, build failure logs, or runtime logs while iterating on a preview or production release.
How do I add com.pulsemcp/vercel to my agent?
Create a Vercel API token, set VERCEL_TOKEN (and team vars if needed), register npx -y vercel-platform-mcp-server as stdio MCP, optionally set VERCEL_ENABLED_TOOLGROUPS.