Vercel MCP Server

v2026.6-beta

Vercel

MCPdeploymentdevopshostingmcp

Strong

About This MCP

Vercel's official hosted MCP server at mcp.vercel.com. Provides Vercel documentation search and tools to inspect teams, projects, deployments, and deployment logs. Remote-only with OAuth 2.1, a client allowlist, and mandatory consent; deliberately read-only at initial launch. Currently in Public Beta.

Last Evaluated: June 10, 2026

Official Website

Trust Vector Analysis

Dimension Breakdown

🚀Performance & Reliability

api reliability

Endpoint stability analysis on Vercel platform infrastructure

Evidence

Vercel MCP Documentation — Hosted on Vercel's own platform infrastructure with a single managed endpoint at https://mcp.vercel.com

highVerified: 2026-06-10

operation success rate

Operation success testing across documented tools on real projects

Evidence

Vercel MCP Documentation — Read-oriented tools (projects, deployments, logs) are thin wrappers over the stable Vercel REST API and succeed consistently within granted scopes

mediumVerified: 2026-06-10

search accuracy

Relevance assessment of documentation search results for common platform queries

Evidence

Vercel MCP Documentation — Documentation search returns current Vercel docs, reducing hallucinated configuration answers in coding agents

mediumVerified: 2026-06-10

error recovery

Error handling testing across permission, scope, and session-expiry failures

Evidence

Vercel MCP Documentation — Returns structured errors for unauthorized scopes, unknown projects, and expired sessions; OAuth re-consent flow recovers expired grants

mediumVerified: 2026-06-10

rate limit handling

Rate limiting behavior observation; limited published detail during beta

Evidence

Vercel MCP Documentation — Inherits Vercel API rate limits per authenticated user; MCP-specific limits are not separately published during Public Beta

lowVerified: 2026-06-10

🛡️Security

authentication security

Review of OAuth 2.1 flow, consent screens, and token lifecycle

Evidence

Vercel MCP Documentation — OAuth 2.1 authorization with mandatory user consent on every connection; no static API tokens are placed in client configuration

highVerified: 2026-06-10

scope limitation

Permission boundary testing of the shipped tool surface for write capability

Evidence

Vercel MCP Documentation — Deliberately read-only at initial launch: tools inspect teams, projects, deployments, and logs but cannot mutate or trigger deployments

highVerified: 2026-06-10

token exposure risk

Token storage and exposure-surface analysis for the remote-only model

Evidence

Vercel MCP Documentation — Remote-only design means no locally stored long-lived secrets; OAuth tokens are short-lived and revocable from the Vercel dashboard

highVerified: 2026-06-10

unauthorized action risk

Threat modeling of agent misuse against the allowlisted, read-only tool surface

Evidence

Vercel MCP Documentation — A client allowlist restricts which MCP clients may connect, and the read-only launch surface means a confused or injected agent cannot modify infrastructure

highVerified: 2026-06-10

action auditability

Audit logging review of grant management and access attribution

Evidence

Vercel MCP Documentation — OAuth grants are visible and revocable per user; access activity is attributable to the granting account, though a dedicated MCP audit log is not yet exposed

mediumVerified: 2026-06-10

🔒Privacy & Compliance

deployment data exposure

Data flow analysis of tool results from Vercel to LLM providers

Evidence

Vercel MCP Documentation — Project metadata, deployment details, and log contents are returned to the LLM provider as tool results

highVerified: 2026-06-10

sensitive data protection

Assessment of redaction controls on log-reading tools

Evidence

Vercel MCP Documentation — Deployment logs can contain secrets, tokens, or PII printed by application code; the server does not redact log contents before returning them

mediumVerified: 2026-06-10

organization data control

Access control review against Vercel team RBAC

Evidence

Vercel Access Control Documentation — Access mirrors the authenticated user's team roles and project permissions; team admins govern membership and can revoke OAuth grants

mediumVerified: 2026-06-10

third party data sharing

Analysis of downstream data sharing once tool results leave Vercel

Evidence

Vercel Privacy Policy — Project and log data retrieved via MCP is shared with the user's chosen LLM provider under that provider's data policy

mediumVerified: 2026-06-10

👁️Trust & Transparency

documentation quality

Documentation completeness and accuracy review

Evidence

Vercel MCP Documentation — Clear official documentation covering endpoint, OAuth setup, supported clients, tool capabilities, and security model

highVerified: 2026-06-10

operation visibility

Logging and traceability assessment across client and dashboard

Evidence

Vercel MCP Documentation — Tool calls are visible in MCP client logs; connected integrations and grants are visible in the Vercel dashboard

mediumVerified: 2026-06-10

open source transparency

Source availability and independent verifiability review

Evidence

Vercel MCP Overview Repository — Server implementation is closed source; a public overview repository documents capabilities but the code cannot be independently audited

highVerified: 2026-06-10

api coverage clarity

Comparison of documented tool surface against observed server capabilities

Evidence

Vercel MCP Documentation — Documented tool surface (docs search; team, project, deployment management views; deployment logs) matches observed behavior, with read-only status stated explicitly

mediumVerified: 2026-06-10

⚙️Operational Excellence

ease of setup

Setup complexity assessment across allowlisted MCP clients

Evidence

Vercel MCP Documentation — Zero installation: add https://mcp.vercel.com in a supported client and complete the OAuth consent flow

highVerified: 2026-06-10

api performance

Latency observation across representative tool calls

Evidence

Vercel MCP Documentation — Hosted on Vercel's edge-adjacent infrastructure; typical tool responses return quickly, with log retrieval slowest for large deployments

mediumVerified: 2026-06-10

reliability

Uptime analysis combined with beta-status risk assessment

Evidence

Vercel Status — Rides on Vercel platform availability, which is historically strong, though the MCP product itself is in Public Beta

mediumVerified: 2026-06-10

feature coverage

Feature completeness assessment against the full Vercel API surface

Evidence

Vercel MCP Documentation — Read-only launch scope excludes deployment triggering, environment variable management, and domain configuration; coverage is intentionally narrow

highVerified: 2026-06-10

community adoption

Adoption analysis across the Vercel developer ecosystem and MCP clients

Evidence

Vercel MCP Overview Repository — First-party server promoted to Vercel's large developer base and supported by major MCP clients since the Public Beta announcement

mediumVerified: 2026-06-10

Strengths

+Notably strong security posture: OAuth 2.1, mandatory consent, client allowlist, and read-only launch scope
+Remote-only design eliminates locally stored long-lived secrets
+Live documentation search reduces hallucinated Vercel configuration answers
+Deployment log access enables fast AI-assisted debugging of failed builds
+Zero-install setup in supported MCP clients
+Backed by Vercel's reliable platform infrastructure

Limitations

!Read-only at launch: cannot trigger deployments or change configuration
!Closed source; implementation cannot be independently audited
!Deployment logs may contain unredacted secrets or PII that flow to the LLM provider
!Public Beta status means the tool surface and limits may change
!Client allowlist excludes unsupported or custom MCP clients
!No dedicated MCP-specific audit log exposed yet

Metadata

repository: https://github.com/vercel/vercel-mcp-overview

license: Proprietary (closed source; public overview repo)

maintained by: Vercel

status: Public Beta

remote endpoint: https://mcp.vercel.com

authentication: OAuth 2.1 with mandatory consent and client allowlist

transport types

0: streamable-http (remote only)

installation methods

0: Remote MCP endpoint

write access: Read-only at initial launch by design

mcp version: 1.0

Use Case Ratings

code generation

Docs search plus project and log context makes coding agents far more accurate on Vercel deployments

research assistant

Good for investigating deployment history, failures, and project configuration across teams

data analysis

Useful for inspecting deployment metadata and logs, but no aggregate analytics tooling

customer support

Helps internal support diagnose customer-facing deployment issues from logs

education

Safe read-only surface is well suited to teaching deployment and platform concepts

Similar MCPs

MCP GitHub Server

GitHub (formerly Anthropic)

Figma MCP Server

Figma

Stripe MCP Server

Stripe

MCP Linear Server

Community