All integrations

Run agents with Vercel

Connect Vercel once, and every run that names it works in Vercel on the account you connected.

Connect VercelOpens Settings → Connections in the console.

What an agent can do in Vercel

Manage Vercel projects and deployments: list projects, read build and runtime logs, inspect deployments, and search the Vercel docs.

Jobs on Rush that use Vercel

How Vercel connects

Vercel is a remote MCP server, published by Vercel, at https://mcp.vercel.com. Connecting it signs in through the MCP OAuth flow on Vercel's side.

From Vercel: Vercel's MCP documentation.

Connect it once in the console under Settings → Connections, or from your server with POST /me/connections. The sign-in finishes in a browser signed in to the console as the same person, and a link not finished within 10 minutes expires.

After that, a run that names vercel in connections, or runs a saved agent that names it, gets it; your connections reach no run that does not name them.

POST https://api.phoenix.so/me/connections

{
  "type": "mcp",
  "name": "Vercel",
  "url": "https://mcp.vercel.com"
}

Whose Vercel account the agent uses

Your Vercel connection is personal: it belongs to the person who signed in. A run started in the console uses that person's Vercel, and a run started with an API key uses the Vercel of the member who created the key.

To act for your own app's users, make each user an agent from your template and show them, signed in to your app, the sign-in link POST /o/{org}/agents/{agent}/connections returns. They sign in to their own Vercel, and that agent's runs use their account and nothing else: never yours, never another user's.

More Cloud integrations

Frequently asked questions

How do I connect Vercel to Rush?

Open Settings → Connections in the console and connect Vercel, or send POST /me/connections with {"type":"mcp","name":"Vercel","url":"https://mcp.vercel.com"} and open the authorize_url it returns while signed in to the console. The connection reads pending until the sign-in finishes, then connected.

Does every run get my Vercel account?

No. A run gets your Vercel connection only when it names it in connections ("connections": ["vercel"]), or runs a saved agent that names it. A saved agent names its connections once, and every run of it gets them.

What can an agent do in Vercel?

Manage Vercel projects and deployments: list projects, read build and runtime logs, inspect deployments, and search the Vercel docs. 9 published jobs use it; this page lists them.

Can my app's users connect their own Vercel?

Yes. Make each user an agent from your template, and they sign in to their own Vercel through the link POST /o/{org}/agents/{agent}/connections returns. That agent's runs use their account alone.

Keep reading