Vercel MCP

Explore your projects and deployments. Manage domains and environment variables with explicit write access.

1. Sign in

Use your invited email address. Your account and Vercel connection belong only to you.

Sign-in setup is pending. New accounts cannot connect yet. Return here once sign-in is available.

2. Connect your Vercel account

  1. Sign in to Vercel and open Account settings → Tokens.
  2. Create a token named “Vercel MCP,” choose the account or team you want to access, and set an expiration. Copy it into the Vercel access token field above.
  3. For a team, enter its ID from the team’s Settings → General, or its URL slug, as the default team. Leave this empty for your personal account. To allow switching teams, list their IDs or slugs under Allowed teams, including the default team.
  4. Optionally restrict access to project IDs or names. Writes require this list and the Allow writes checkbox. Leave writes off to browse safely.
  5. Select Verify and save connection. The Vercel token is encrypted and never displayed again. To replace an expired token, create another in Vercel and save it here.

The Vercel API documentation explains provider tokens and team access. Your Vercel token and the MCP token below are separate credentials.

3. Connect your MCP client

After connecting Vercel, create a named MCP token above. You generate this token here; you do not need one from the server owner.

Add a remote server using Streamable HTTP:

https://vercel-mcp.sherwoodcallaway.com/mcp

Choose bearer-token authentication and paste your new MCP token. If your client accepts custom headers, use:

Authorization: Bearer <YOUR_MCP_TOKEN>

For clients accepting a JSON server configuration with URL and headers:

{
  "mcpServers": {
    "vercel": {
      "url": "https://vercel-mcp.sherwoodcallaway.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_MCP_TOKEN>"
      }
    }
  }
}

Replace the placeholder locally. Do not paste credentials into chat. Use a client that supports remote HTTP and bearer headers; OAuth-only clients are not supported by this token flow. MCP Gateway is optional.

4. Verify and manage access

Reload your client’s tools. Ask it to search for getUser, then execute that operation. Confirm the returned Vercel account is yours. Then try listProjects.

401 Unauthorized: check that you used the MCP token, that it has not expired or been revoked, and that the URL ends in /mcp. Create a replacement if needed.

Provider request failed: verify your Vercel token’s expiration, selected team, and permissions. Save a replacement connection above. If a write is unavailable, enable writes on both the connection and a new MCP token.

Revoke an individual MCP token to remove one client. Disconnect removes your saved provider credentials and revokes all current MCP tokens. Already-running requests may finish. To revoke provider access everywhere, also revoke the Vercel token in Vercel settings.