Superconductor Docs

Vercel

Connect Vercel so agents can deploy projects and investigate failed deployments.

The Vercel connector in Workspace Settings, for searching Vercel docs, deploying projects, and investigating deployments and their logs, with a Connect button

Vercel MCP lets agents work with your Vercel projects directly. Agents can deploy the code they just wrote, check the preview, and dig into a failed deployment, without you leaving the chat.

For use cases and example prompts, see Vercel for AI coding agents.

What is Vercel?

Vercel is a platform for building, deploying, and hosting websites and web apps.

What agents can do

Once you connect Vercel, agents can:

  • List your teams, projects, and deployments
  • Create projects and deploy files to them
  • Read a deployment's build logs
  • Open protected preview deployments to check that a page works
  • Pause and unpause projects
  • Search the Vercel documentation

Agents act with the permissions you approve on Vercel, which include deploying to production and buying domains. Tell agents when they should only read.

Setup

Vercel connects by signing in with your Vercel account. There's no access token to create.

Go to Workspace Settings → Connectors (or a project's Connectors page) and click Connect on the Vercel card (or Connect another to add another account).

Step 1: who the connection is for

Choose Me or Workspace as the owner, then choose where agents can use the connection. The default is Me, with In my private chats selected. Enable In projects separately and choose All projects, including future ones or Some projects. Anyone with access to those projects can use the connection, including in sessions they launch themselves. See connection options for what each choice means.

Click Continue.

Step 2: sign in with Vercel

Click Continue to Vercel and sign in to Vercel if you aren't already. Vercel shows the permissions the connection gets. Click each team agents should work in, choose Access to all current and future projects or pick its projects, and click Authorize. Then click Allow Access, and you land back on the Connectors page with Vercel connected.

Agents then act in Vercel as whoever signed in, in the teams and projects you authorized. If you enable In projects, anyone with access to those projects can use that account — so sign in with an account whose permissions you're happy to share.

Reconnecting and disconnecting

If Vercel stops accepting a connection, the Connectors page shows a Reconnect needed badge on it, and agents run without Vercel.

Click Manage next to the connection to fix it. There's no key to replace: the page shows Account connection: Connected and, when something's wrong, a Reconnect Vercel button. You can only reconnect a personal connection you own; for someone else's, Superconductor tells you who to ask.

Disconnect also revokes Superconductor's access at Vercel. If Vercel doesn't confirm the revocation, Superconductor tells you to remove Superconductor from the Tokens page of your Vercel account settings to finish the job.

Troubleshooting

Agents can't see a team

If agents report they aren't authorized for a team, it wasn't authorized when you connected. Disconnect, connect again, and on Vercel's screen click the team and Authorize before Allow Access.

When to use it

Ask agents to use Vercel when a ticket involves a failed deployment, a change you want to check on a preview, or a new project to deploy. For example:

Our latest Vercel deployment failed. Read the build logs, fix the build, and redeploy.
Open the preview deployment for the new landing page and list any copy that still says "Coming soon".

On this page