MCP field guide / Vercel
// mcp field guide · deploy platform
A platform MCP that breaks the usual pattern: it has no delete, rollback, or env-var tool at all. You can't tear down or reconfigure existing services through it — its design is "read everything, deploy net-new code." So the irreversibility here isn't a destroyed database; it's money (a recurring plan, a registered domain) and a production publish.
GUARD FIT · READ SURFACE
PASS-THROUGHDocs search, projects/deployments, build & runtime logs, analytics, agent-run traces. The majority of calls — no state change.
GUARD FIT · MONEY + PROD PUBLISH
STRONGbuy_pro/buy_domain (non-refundable), production deploy_to_vercel, and access-grant links — the consequential, hard-to-undo actions.
Overall fit: STRONG on a narrow subset (money + prod publish); weak everywhere else — and there are no deletes to guard.
Vercel MCP is Vercel's official hosted server (mcp.vercel.com, remote over Streamable HTTP with OAuth). It gives an AI assistant scoped access to a Vercel account: search docs, inspect projects/deployments/logs/errors, query Web Analytics, observe Agent Runs — and deploy. Vercel's own security docs note that connecting "grants the AI system the same access as your Vercel user account," and it recommends enabling human confirmation in the client.12
| Tier | Tools |
|---|---|
| read-only | search_vercel_documentation, list_projects/get_project, list_deployments/get_deployment, get_deployment_build_logs, get_runtime_logs/get_runtime_errors, get_web_analytics, list_agent_runs/get_agent_run_trace, get_purchase_quote, check_domain_availability_and_price |
| mutating | deploy_to_vercel (preview or production), import-claude-design-from-url, get_access_to_vercel_url (mints a link bypassing deployment protection), toolbar writes (reply/edit/resolve/react) |
| financial / irreversible | buy_pro (starts recurring billing), buy_credits, buy_addon, buy_domain (registers a domain — non-refundable); production deploy_to_vercel publishes live |
The notable absence: there is no delete-project, delete-deployment, remove-domain, rollback, or environment-variable tool — verified against Vercel's official tools reference and the live server. The high-blast-radius operations a guard usually targets simply aren't in the surface. So "it can nuke your infra" is false for this server; the real edges are money and production publish.
Debug a failing deploy. get_runtime_errors → get_runtime_logs/get_deployment_build_logs to find the crash, then deploy_to_vercel to ship the fix.
Ship generated UI. import-claude-design-from-url or deploy_to_vercel to publish to a preview URL, then promote to production.
Traffic Q&A. get_web_analytics for "top routes / countries / signups last week" — read-only.
Reads → pass through. They're the majority of calls and change nothing. (The one residual concern is data exfiltration via get_runtime_logs/web_fetch_vercel_url under prompt injection — a policy/observability concern, not an approval gate.)
Gate money and production publish — that's the whole case:
buy_pro (recurring), buy_credits, buy_addon, buy_domain. Non-refundable; a registered domain is effectively irreversible. Vercel already gates these with quote→confirm+idempotency, but they're the clearest human-approval case.deploy_to_vercel with target: production (and import-claude-design-from-url): publishes live, agent-authored code.get_access_to_vercel_url — grants access past deployment protection; approve because it widens exposure of protected environments.The honest inversion: most platform guards exist to catch a destructive delete. Here there are none — so the guard's job is to gate spend and publish. A charged card and a registered domain can't be un-bought; a production deploy is live the moment it ships. That's still compensation-is-not-undo — just with the irreversible edge on money and go-live, not on data loss.
ChronoMCP passes Vercel's read surface through and holds purchases, production deploys and access-grant links for a human.
Read the quickstart → More MCP profilesProfiles describe third-party software from its public sources; ChronoMCP is not affiliated with Vercel. The exact exposed tool set varies per connected client and purchase tools are "rolling out gradually"; risk groupings are our classification. Capabilities reflect sources current as of Aug 2026 — check the source links.