Vercel Profile

Vercel

Vercel is both a hosted MCP provider for project operations and a deployment platform for customer-owned MCP servers using Functions, OAuth, previews, firewall and rollback.

Interface hosts, builders & integration infrastructureInterface host and orchestration layerBYO-UI-ready platform

Representative source ↗Product site ↗Suggest a correction

System roleInterface host and orchestration layer

Access maturityBYO-UI-ready platform

MCP supportOfficial MCP server + 3rd Party MCP services

Reference updatedJun 26, 2026

BYO-UI reviewedJul 22, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Teams, projects, deployments, build and runtime logs, domains and registrant data, protected deployment URLs, documentation, local CLI context, and customer-owned MCP deployments.

02 · Data you can retrieve

Search public documentation; list teams, projects and deployments; inspect project metadata and build or runtime logs; check domain pricing; and fetch authorized protected deployment content.

03 · Actions and write paths

Deploy the current project, purchase a domain with registrant details, create a temporary shareable link to a protected deployment, and invoke the supported Vercel CLI path.

04 · Authentication and permissions

Vercel's hosted server uses OAuth and only supports reviewed clients. Authenticated tools receive the connected user's Vercel access; documentation search is available without authentication.

05 · Monitoring, approval, and recovery

Confirm domain price, renewal and registrant data; deployment project and environment; protected-link audience; and CLI action. Keep external MCP tools isolated against prompt-injection-driven data disclosure.

06 · Limits and caveats

Vercel MCP is Beta on all plans and accepts only reviewed clients. Public documentation search is unauthenticated; project, deployment, domain, access and CLI tools require Vercel authorization.

First-party MCP tool catalog

24 named MCP tools · Vercel remote MCP server

The exact tool names on Vercel's MCP tool reference for the remote server at mcp.vercel.com. Reviewed Jul 10, 2026. The server is beta on all plans and available through Vercel-reviewed clients. Documentation search is public; authenticated tools inherit the connected user's access. Domain purchase, deployment, temporary access links, Toolbar mutations, and the open-ended CLI surface require explicit confirmation.

First-party exact listComplete list on cited pageVercel remote MCP

Search this catalog

24 shown

Documentation and projects4

search_documentationreadlist_teamsreadlist_projectsreadget_projectread

Deployments and logs4

list_deploymentsreadget_deploymentreadget_deployment_build_logsreadget_runtime_logsread

Agent Runs observability4

list_agent_run_projectsreadlist_agent_runsreadget_agent_runreadget_agent_run_traceread

Domains and protected deployment access4

check_domain_availability_and_pricereadbuy_domainconsequential writeget_access_to_vercel_urlconsequential writeweb_fetch_vercel_urlread

Vercel Toolbar threads6

list_toolbar_threadsreadget_toolbar_threadreadchange_toolbar_thread_resolve_statuswritereply_to_toolbar_threadwriteedit_toolbar_messagewriteadd_toolbar_reactionwrite

CLI and deployment2

use_vercel_cliconsequential writedeploy_to_vercelconsequential write

Catalog evidence: Vercel MCP Tools · Vercel MCP

First-party connector catalog

9 named connectors · Vercel Connect dedicated connectors

The dedicated provider connectors named as currently available on the Vercel Connect product page; generic OAuth and API-key connectors and providers marked coming soon are excluded. Reviewed Jul 10, 2026. Vercel Connect is a delegated-credential layer for agent workflows, not the Vercel MCP server. Provider capabilities and token scopes vary by installation. The page separately marked Resend, Workday, and Microsoft Teams as coming soon, so they are not published here as available connectors.

First-party exact listVerified partial listVercel Connect

Dedicated provider connectors9

Slackread/writeGitHubread/writeLinearread/writeDiscordread/writeNotionread/writeSalesforceread/writeFigmaread/writeSnowflakeread/writeWorkOSread/write

Catalog evidence: Vercel Connect: Available connectors

First-party access

Documented surfaces

MCP / agent surface ↗Verified first-party provider and MCP deployment infrastructure API ↗Developer access Developer docs ↗SDKs and platform guidance Events / extensions ↗Webhooks, apps, or extensions Product ↗Native platform experience

Agent access

MCP support

Official MCP server + 3rd Party MCP servicesVercel-hosted remote MCP plus MCP deployment platformPublic beta on all plans

Support: Official MCP server + 3rd Party MCP services

Read scope: Expose public documentation or authenticated team, project, deployment, log, domain-price and protected-content reads while preserving team, project, deployment, environment and acting-user context.

Write scope: 8 of 24 reviewed named tools have a write, draft, or mixed action label, including buy_domain, get_access_to_vercel_url, change_toolbar_thread_resolve_status, reply_to_toolbar_thread, edit_toolbar_message, and others. Read each catalog boundary before enabling them.

Authentication: Vercel's hosted server uses OAuth with explicit consent for approved clients. Customer-owned servers implement their own bearer-token verification, required scopes and protected-resource metadata.

Approval boundary: Require confirmation before deployment, domain purchase or renewal, temporary protected-access creation, and CLI execution; show project, team, environment, price, registrant, URL and command context as applicable.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4

Action access4

Event access4

Identity4

Governance4

Agent access3

UI extensibility4

Portability4

Observability4

Documentation5

Proposed customer-shaped experiences

What customers could create on top.

The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Vercel ships them.

Single-platform patterns

Hosted BYO-UI and MCP application platform
BYO-UI application shell
Capability gateway
Agent and tool operations console

Use in the brief builder →

Multi-platform compositions

Vercel + systems of record: byo-ui application shell
Vercel + systems of production + systems of engagement: cross-system decision workspace

Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

8 recorded sources

MCPRepresentative source

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

Official Vercel documentation confirms an OAuth remote endpoint at mcp.vercel.com, a reviewed-client allowlist and public versus authenticated tools. The service is Beta, project and deployment actions can be…

Publisher updated: Jun 26, 2026
BYO-UI reviewed: Jul 12, 2026

Targeted first-party MCP/agent-role review; broader API inventory retained

DocumentationSource inventory

https://vercel.com/docs ↗

First-party platform documentation.

Publisher updated: Jun 30, 2026
BYO-UI reviewed: Jul 10, 2026