Vercel MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Vercel is adding deployment operations to its hosted MCP; monitor how consent and mutation controls evolve.

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Manage and troubleshoot authorized Vercel teams, deployments and resources from remote MCP.

What we know

Official Vercel remote MCP server. Users authorize a client through browser sign-in and team grants. Tools cover deployment inspection/logs and platform management areas including projects, domains, environment variables and other resources, subject to the official live tool list and existing user permissions.

Maintenance / activity evidence

Publisher MCP documentation updated 2026-09-15.

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Read deployments, logs, projects and execute enabled mutation tools across authorized resources. Writes: Modify projects/settings and environment variables where enabled; Manage domains and deployment/platform resources using available MCP tools.
OAuth user session, scoped by Vercel teams and existing permissions.
Sensitive access: Deployment logs and error data, Environment/configuration values, Private project assets

Vercel MCP is a full platform management interface; write tools may alter production settings or incur spend.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Have newly exposed deployment operations acquired clearer permission and human-confirmation boundaries?

The reviewed official source discloses account-level authority and consent controls; no specific material listing blocker was identified in this bounded assessment.

Vercel MCP is a full platform management interface; write tools may alter production settings or incur spend.
Read deployments, logs, projects and execute enabled mutation tools across authorized resources.
OAuth user session, scoped by Vercel teams and existing permissions.
Vercel logs, application metadata and protected deployment contents are returned to the authorized client.
Reviewed write actions: Modify projects/settings and environment variables where enabled; Manage domains and deployment/platform resources using available MCP tools
Sensitive access: Deployment logs and error data, Environment/configuration values, Private project assets
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Account-wide permissions and prompt injection remain operational risks; no runtime security certification.
exact version-dependent available tool set and token retention details
OAuth sign-in and team grant are required before accessing private resources.
Permissions do not exceed the signed-in user and granted teams.
The broad current official tool catalog includes mutating operations; cannot label the server read-only.
Do not assume all Vercel REST endpoints are MCP tools or that every action is always available.
Use official Vercel MCP tools documentation; do not infer universal ability from platform REST API.

Original activity observations

Publisher MCP documentation updated 2026-09-15.

Technical identity

public:vercel

Exact implementation source: https://vercel.com/docs/agent-resources/vercel-mcp ↗
Reviewed resource type: MCP Server
Service endpoint: https://mcp.vercel.com

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Evidence source ↗
vercel.com/docs/agent-resources/vercel-mcp
Source material retained for this review.
Evidence source ↗
vercel.com/docs/agent-resources/vercel-mcp/tools
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
mcp.vercel.com
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher-documented package/connection route; replace placeholders and verify host-specific syntax.
Publisher setup example · Claude Code only · Publisher instructions
claude mcp add --transport http vercel https://mcp.vercel.com
Configure / authenticate
MCP100 setup guide
Official remote OAuth endpoint; in Claude Code use /mcp; Codex `codex mcp add vercel --url https://mcp.vercel.com` and authorize in browser.
Use correct transport and published host config. Never paste secrets in chat; server registration is separate from software installation.
Previously reviewed configuration / prerequisites: Connect the remote URL then authorize the specific Vercel team(s).
Previously reviewed configuration / prerequisites: Vercel account and access to target teams
Check connection
Suggested check
Confirm Vercel documentation tools then check account scope; avoid deployment changes.
Remove / uninstall / revoke
MCP100 setup guide
Remove Vercel MCP registration from actual host (`claude mcp remove vercel` for Claude Code or `codex mcp remove vercel` for Codex), or remove custom connector via client Settings. This does not delete Vercel account or projects.
Conditional host / package cleanup · Claude Code only · MCP100 composed guide
claude mcp remove vercel

Official Documentation & Sources

https://vercel.com/docs/agent-resources/vercel-mcp ↗

What it does

Official Vercel remote MCP server. Users authorize a client through browser sign-in and team grants. Tools cover deployment inspection/logs and platform management areas including projects, domains, environment variables and other resources, subject to the official live tool list and existing user permissions.

Capability: Cloud & DevOps
Resource type: MCP Server
Best fit: Manage and troubleshoot authorized Vercel teams, deployments and resources from remote MCP.

Representative uses

List teams, projects and deployments
Inspect deployment status and runtime errors/logs
Read content on permitted protected deployment URLs
Manage selected Vercel resources where MCP tools and team permissions allow

Limitations

OAuth sign-in and team grant are required before accessing private resources.
Permissions do not exceed the signed-in user and granted teams.
The broad current official tool catalog includes mutating operations; cannot label the server read-only.
Do not assume all Vercel REST endpoints are MCP tools or that every action is always available.
Use official Vercel MCP tools documentation; do not infer universal ability from platform REST API.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: OAuth user session, scoped by Vercel teams and existing permissions.
Permissions: Read deployments, logs, projects and execute enabled mutation tools across authorized resources.
Data handling: Vercel logs, application metadata and protected deployment contents are returned to the authorized client.
Cost: plan_based
Risk and cautions: Vercel MCP is a full platform management interface; write tools may alter production settings or incur spend.

Access scope and cautions

Write actions: Modify projects/settings and environment variables where enabled Manage domains and deployment/platform resources using available MCP tools
Sensitive access: Deployment logs and error data Environment/configuration values Private project assets
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: List teams, projects and deployments; Inspect deployment status and runtime errors/logs; Read content on permitted protected deployment URLs; Manage selected Vercel resources where MCP tools and team permissions allow.

What setup and authentication are documented?

Recorded endpoint: https://mcp.vercel.com. Recorded transport: streamable_http. Prerequisites: Vercel account and access to target teams; Remote MCP client. Client notes: Connect the remote URL then authorize the specific Vercel team(s). These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Browser OAuth authorization and per-team client access grant.

Can it modify data or perform write operations?

Documented write actions include: Modify projects/settings and environment variables where enabled; Manage domains and deployment/platform resources using available MCP tools. Recorded permission boundary: Read deployments, logs, projects and execute enabled mutation tools across authorized resources.

What data-handling boundary should I consider?

Vercel logs, application metadata and protected deployment contents are returned to the authorized client. Recorded sensitive-access context: Deployment logs and error data; Environment/configuration values; Private project assets.

What limitations and risks should I check before use?

Vercel MCP is a full platform management interface; write tools may alter production settings or incur spend. OAuth sign-in and team grant are required before accessing private resources. Permissions do not exceed the signed-in user and granted teams. The broad current official tool catalog includes mutating operations; cannot label the server read-only. Do not assume all Vercel REST endpoints are MCP tools or that every action is always available. Use official Vercel MCP tools documentation; do not infer universal ability from platform REST API. Account-wide permissions and prompt injection remain operational risks; no runtime security certification.

What cost model is recorded?

The reviewed cost model is plan based. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.