---
title: Vercel
description: "Manage Vercel projects, deployments, and logs through Vercel's MCP server."
url: "https://eve.dev/integrations/vercel"
docs_index: /llms.txt
type: connection
keywords:
  - mcp
  - projects
  - deployments
  - logs
  - oauth
  - connect
---

> For an index of all documentation, see [/llms.txt](/llms.txt).

Connection integration for eve. Manage Vercel projects, deployments, and logs through Vercel's MCP server.

## Install

Add the connection from eve's registry. This writes the initial definition under `agent/connections/` and installs its authentication dependency when needed:

```bash
eve add connection/vercel
```

## Quick start

### MCP · User

Create `agent/connections/vercel.ts`. The connection name is derived from the filename:

```ts
// agent/connections/vercel.ts
import { connect } from "@vercel/connect/eve";
import { defineMcpClientConnection } from "eve/connections";

export default defineMcpClientConnection({
  url: "https://mcp.vercel.com",
  description: "Vercel: manage projects and deployments, inspect logs, and search documentation.",
  auth: connect("vercel"),
});
```

Connect owns the OAuth flow, and each end-user authorizes in their own browser before their first tool call.

### MCP · App

Create `agent/connections/vercel.ts`. The connection name is derived from the filename:

```ts
// agent/connections/vercel.ts
import { connect } from "@vercel/connect/eve";
import { defineMcpClientConnection } from "eve/connections";

export default defineMcpClientConnection({
  url: "https://mcp.vercel.com",
  description: "Vercel: manage projects and deployments, inspect logs, and search documentation.",
  auth: connect({ connector: "vercel/your-connector", principalType: "app" }),
});
```

Connect authenticates as the agent itself through one shared installation, with no per-user consent.

## Configure

### MCP · User

Link your project, create the connector, and pull OIDC locally:

```bash
vercel link
vercel connect create vercel --name vercel
vercel env pull
```

Select None when prompted for a token authentication method. Each user completes OAuth when needed.

See the [Connections docs](/docs/connections) for principal types, headers, approval, and protocol-specific filters.

### MCP · App

Link your project, create the connector, and pull OIDC locally:

```bash
vercel link
vercel connect create api-key --name vercel
vercel env pull
```

Enter a team-scoped [Vercel token](https://vercel.com/kb/guide/how-do-i-use-a-vercel-api-access-token) when prompted, then copy the returned connector UID into the App example. This avoids per-user OAuth, though the Vercel token still belongs to the user who created it.

See the [Connections docs](/docs/connections) for principal types, headers, approval, and protocol-specific filters.

## Related resources

- [Build an incident response SRE agent with eve](https://vercel.com/kb/guide/eve-incident-sre-agent): Deploy a Slack-based investigation agent that connects to Datadog, GitHub, and Vercel, tests root-cause hypotheses, and posts evidence-linked findings in threads.
- [Build a software factory with eve](https://vercel.com/kb/guide/eve-software-factory): Deploy Foreman, an eve agent system that turns GitHub issues or Linear tickets into reviewed draft pull requests while leaving merge decisions to humans.
- [Manage Vercel projects with a software factory](https://vercel.com/kb/guide/software-factory-vercel-mcp): Add Vercel's hosted MCP server to the eve software factory so Foreman can read build logs, runtime errors, and deployment history through app-scoped Vercel Connect auth and a read-only tool allowlist.

[Read the full connection documentation](https://vercel.com/docs/agent-resources/vercel-mcp)

---

For a semantic overview of all documentation, see [/sitemap.md](/sitemap.md)

For an index of all available documentation, see [/llms.txt](/llms.txt)

For agent-facing discovery, including API and MCP surfaces, see [/agents.md](/agents.md)