Available

Vercel MCP server

Inspect project configuration coverage and deployment state with Arc0’s Vercel tools. Agents can read build logs, request an approved preview rebuild, or cancel a build in progress. Connect through Arc0 to use the actions your identity is allowed to call.

Developer toolsAPI keyMCP + RESTvercel.com
AUDIT LOG · VERCELPOLICY: acme-support
09:41:07 · claude · u_8f2read
vercel.list_projects
List projects✓ allowed · 212ms
09:41:08 · claude · u_8f2read
vercel.get_project
Get project✓ allowed · 164ms
09:41:09 · claude · u_8f2write
vercel.redeploy
Redeploy as preview✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
vercel.cancel_deployment
Cancel deployment✕ blocked · policy: deny
ILLUSTRATIVE POLICY TRACE · NOT A LIVE RECEIPT

Working with Vercel

When a build fails, locate the project with vercel.list_projects and inspect its recent history with vercel.list_deployments. vercel.get_deployment returns state and URL for a selected deployment. Keep the deployment ID alongside the diagnosis so another engineer can compare the same build rather than a later attempt.

vercel.get_build_logs reads a bounded set of build events. Log text is not automatically redacted and may contain secrets, so choose what to include in a shared summary. vercel.list_env_vars can check whether variable names and targets are present, but deliberately discards their values. A truncated result is not a complete configuration inventory.

For an authorized rebuild, vercel.redeploy creates a preview deployment from a verified source project; it does not promote production. A forced new build can incur additional usage. vercel.cancel_deployment stops a queued or building deployment without refunding work already consumed. After an uncertain redeploy, list deployments before trying again, and after cancellation read the selected deployment’s state to confirm the result.

Official MCP reference: Vercel documentation.

01 · USE CASES

Agent workflows for Vercel.

01

Review recent deployments

Use vercel.list_projects and vercel.list_deployments to locate a project’s latest builds.

02

Diagnose a build failure

Use vercel.get_deployment and vercel.get_build_logs for deployment state and bounded build events.

03

Check configuration coverage

Use vercel.list_env_vars to inspect variable names and targets without exposing their values.

04

Control an approved rebuild

Use vercel.redeploy for a preview build or vercel.cancel_deployment to stop a queued or running build.

02 · ACTIONS

8 Vercel actions, graded by risk.

These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.

read

6

Look things up, subject to your permissions.

  • vercel.list_projects
    List projects

    List up to 100 projects with names and frameworks. Use when locating a project, not its deployment history. Pass next as from for another page; search matches project names.

  • vercel.get_project
    Get project

    Read project ID, name, framework and update time. Use when checking project metadata, not environment values or private integration settings.

  • vercel.list_deployments
    List deployments

    List up to 100 deployments for one project, newest first. Use when checking rollout status or reconciling an uncertain redeploy before retrying. Pass next as until for another page.

  • vercel.get_deployment
    Get deployment

    Read deployment state and URL by deployment ID. Use when checking build progress or reading back after cancellation. Private environment data, creator details and build configuration are excluded.

  • vercel.list_env_vars
    List environment variable names

    List up to 100 environment variable names and targets. Use when checking configuration coverage, not reading secret values. Values are always discarded. A truncated result is not a complete inventory.

  • vercel.get_build_logs
    Get build logs

    Read up to 100 build events with unredacted text capped at 4000 characters per line. Use when diagnosing builds, not runtime logs. For older events pass the oldest created as until; equal timestamps may overlap, so deduplicate. Output may contain secrets.

write

1

Create and change things. Allow, or ask the user first.

  • vercel.redeploy
    Redeploy as preview

    Create a preview build from a verified source project. Use when an authorized rebuild is needed, not to promote production. forceNew bypasses deduplication; retries can incur another build charge. After an uncertain response, list deployments before retrying.

destructive

1

Delete, cancel or archive. Ask first, or deny outright.

  • vercel.cancel_deployment
    Cancel deployment

    Cancel a queued or building deployment by ID. Use when an authorized build should stop; do not use for a deployment you want to finish. Already spent build usage is not refunded. Read back its state after an uncertain response before retrying.

03 · POLICIES AND AUDIT

Control access to Vercel.

Connect the intended Vercel account, authorize your AI client and set policies for its tools.

Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.

Configure policies and approvals

Example policy choices

  • Read actions: allow where authorized
  • vercel.redeploy: require approval
  • vercel.cancel_deployment: deny

Arc0 MCP endpoint: https://api.arc0.ai/mcp

04 · AUTH AND DATA

How Vercel connects.

Connect Vercel using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.

The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · AI CLIENTS

Use Vercel with your AI client.

Sign in to Arc0 and connect Vercel in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.

Vercel with Claude

Claude Desktop + Claude Code

  1. In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
  2. For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
  3. Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for Claude
Vercel with ChatGPT

ChatGPT on the web

  1. Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
  2. Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
  3. Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for ChatGPT
Vercel with OpenAI Codex

Codex app + CLI

  1. Run the registration command below. The app and CLI share ~/.codex/config.toml.
  2. Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
  3. Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for OpenAI Codex
Vercel with Cursor

Remote MCP setup

  1. Add Arc0 in your client’s remote MCP settings using the server URL below.
  2. Choose OAuth, sign in to Arc0, select the intended workspace and review access.
  3. Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for Cursor
Vercel with VS Code

Remote MCP setup

  1. Add a remote HTTP MCP server named Arc0 using the URL below.
  2. Use OAuth and finish Arc0 sign-in, workspace selection and consent.
  3. Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
Vercel with Any MCP client

Streamable HTTP

  1. Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
  2. For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
  3. Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting

After setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.

07 · FAQ

Vercel and Arc0, answered.

Q01

Is there an official Vercel MCP server, and how does Arc0 differ?

Yes. Vercel hosts an OAuth-based MCP server. Arc0’s current Vercel tools use REST with an access token and limit rebuilds to preview deployments.

Q02

Which permissions does Arc0 need for Vercel?

Use a Vercel access token with access to the configured team. This API-key lane does not request OAuth scopes. The team ID is bound to the connection; project and deployment access still depends on the token’s rights.

Q03

Does this work with Claude, ChatGPT, Codex and Cursor?

Yes, through Arc0 MCP when your Claude, ChatGPT, Codex, or Cursor client supports remote MCP and your account permits it. Connect the app in Arc0 and configure your client using the Arc0 setup guide. App permissions still apply.

Q04

How are credentials stored, refreshed and revoked?

Arc0 stores the access token encrypted without automatic refresh. Disconnect removes local access. Revoke the token in Vercel to invalidate it globally, or reconnect with a replacement when required.

Q05

What happens with rate limits or errors?

Vercel rate limits and build usage still apply. Arc0 reports throttling, authorization failures, and oversized responses. A repeated rebuild can create another billable build, so inspect deployment history after an unknown outcome.

Q06

What is the availability of these Vercel tools?

These tools are available. Connect the app in Arc0 and authorize your AI client. The action list describes the current implementation.

Get started

Plug Vercel into your agent.

Vercel MCP server: 8 actions including list projects, get project, list deployments. Connect through Arc0.

Free to build · MCP + REST · Audit log on every plan

Vercel and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by Vercel.