Vercel MCP

Sign in and connect Vercel

On the account page, sign in with an allowed email. Open Vercel → Account Settings → Tokens, create a token, choose the account/team scope you need, set an expiry, then paste it into Connections. Use a Vercel token; do not paste an MCP token here. Choose only teams and projects you intend this assistant to access. The service encrypts the saved token.

For team access, copy the team ID from Vercel Team Settings → General (or use its team slug) and set it as the default team. Add any other permitted team IDs/slugs in Allowed teams. Project restrictions are optional, but writes require an explicit project list and the Allow writes setting. Leave writes disabled unless you need them.

Replace a provider token by creating a new one in Vercel and saving it in Connections. Revoke the old token in Vercel after confirming the replacement works.

Create a personal MCP token

In the account page’s Access tokens section, create a named token, choose read-only or read/write and an expiry, then copy it immediately. It is shown only once. This personal token authenticates your MCP client; it is separate from the Vercel access token. Revoke it from Access tokens if it is exposed or no longer needed.

Configure your MCP client

Add a remote server using Streamable HTTP at:

Set bearer-token authentication with your personal MCP token. Claude Code:

claude mcp add --transport http vercel https://vercel-mcp.sherwoodcallaway.com/mcp --header "Authorization: Bearer <YOUR_PERSONAL_MCP_TOKEN>"

For clients using JSON server configuration:

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

Replace the placeholder on your device; never include a real token in a URL, shared configuration, or chat. This service uses bearer tokens. OAuth-only clients cannot connect. MCP Gateway is optional.

Verify and manage access

Reload the tools in your client. Call search for getUser, then execute it; confirm the returned account is yours. Start with read operations such as listProjects.

• 401 Unauthorized: check the endpoint and bearer header; create a replacement if the MCP token expired or was revoked.
• Vercel authorization error: check that the Vercel token is active and scoped to the selected team/project. Save a replacement in Connections.
• Project not found: confirm the team ID/slug and allowed project list.
• Write rejected: enable writes for the connection and MCP token, and allow the target project. Provider access still applies.

Disconnect the Vercel connection and revoke MCP tokens from the account page to stop access. You can also revoke the provider token directly in Vercel.