How to use Vercel with Cursor
You want Vercel inside Cursor so it can diagnose failed deployments, ship a reviewed production deployment, configure a new Vercel project, and check and fix project domains — without you copy-pasting between tabs. Here is the whole setup, once.
Create your Vercel gateway
The gateway is the thing Cursor connects to, and it is where you decide which Vercel tools an agent may use. You create it once and every client reuses it.
-
Create an Arcade account
Sign up and open the dashboard. The free tier is enough to follow this through.
-
Create an MCP Gateway and select your Vercel tools
In the dashboard, create a gateway and pick the Vercel tools you want to expose. The gateway is what your client connects to, and it is where tool access is decided.
-
Copy your gateway URL
Every client below needs it.
https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>
Connect the gateway to Cursor
Cursor does not refresh MCP OAuth tokens automatically. For a persistent connection, set Authorization to “Arcade Headers” on the gateway in the dashboard.
-
Open MCP settings
Command Palette (⌘⇧P / Ctrl+Shift+P) → Open MCP Settings, then click “New MCP Server”.
-
Add the gateway to mcpServers
{ "mcpServers": { "mcp-arcade": { "url": "https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>" } } } -
Try it out
Ask Cursor to use one of your Vercel tools.
Full Cursor guide in the docs steps verified 2026-08-13
Try these Vercel prompts
Cursor can now act on your Vercel account. Click a prompt to copy it.
Use a scoped Vercel credential and permissions to limit what the agent can do. Pair it with Contextual Access policies to require approval before it can create, promote, roll back, or delete production deployments.