Vercel Connect is now generally available

is now generally available on all plans and in . Instead of storing long-lived provider secrets, your code requests short-lived, scoped tokens at runtime. Deployments authenticate with their existing Vercel OIDC identity. Each token is scoped to the task, refreshed automatically, and expires on its own.Vercel Connectv0

Register a connector . Pass the service name and the CLI pre-populates the brand name, icon, auth type, and MCP or discovery URL, then prompts for any credentials the service requires:once from the CLI

Connect ships with for tools like and , managed connectors for , , , , , and , plus generic OAuth, API key authentication, and MCP servers.100+ preset connectorsNotionWorkdaySlackGitHubLinearSalesforceSnowflakeMicrosoft

Request a token only when your code needs one, with :getToken

Switch the from the app to a named user and the token acts on that user's behalf, triggering the authorization flow when consent is needed.subject

New at GA:

Together with per-environment attachment, including , and one-command revocation, external access becomes something your team can inspect, prove, and cut off in seconds.Custom Environments

Triggers deliver provider events to your app without a stored secret. Vercel Connect verifies signatures server-side, re-attests each event using an OIDC identity, and forwards the event to your project, even when Deployment Protection is enabled.

Connect also manages private keys and the full credential lifecycle, so you get standards-compliant OAuth without building the infrastructure yourself.

Connect works wherever your functions run and is supported in v0, eve, and Chat SDK. Adapters are available for the auth libraries and agent tooling you already use:

The AI SDK adapter authenticates MCP clients with tokens minted at runtime. In this example, the agent gets read-only Linear access issued for a single user, so downstream actions carry that user's identity:

, our open source tool layer for GitHub agents, plugs into eve through Connect via an . Presets like map to Connect scopes automatically, so tokens carry only the permissions the toolset needs:GitHub Toolseve extensioncode-review

Vercel Connect is available on all plans, with pricing based on token requests and trigger events. Hobby includes 500 token requests and 1,000 triggers per month at no additional cost. Pro is billed at $3 per 1,000 token requests and $0.95 per 1,000 triggers, with custom pricing on Enterprise.

Read the and the , or have your coding agent set up Vercel Connect for you with this prompt:documentationlaunch blog post

Read more

Any service with one command

Tokens at runtime, not secrets at rest

Access your team can inspect and prove

Triggers without stored webhook secrets

Works with your stack

Pricing and availability

• controls who can create and manage connectorsFine-grained RBAC

• record authorization and connector activityAudit logs

• shows how tokens are used across projectsToken and trigger observability

• : Better Auth@vercel/connect/betterauth

• : Auth.js@vercel/connect/authjs

• : AI SDK@vercel/connect/ai-sdk

• : MCP clients@vercel/connect/mcp

• : eve@vercel/connect/eve

• : Chat SDK@vercel/connect/chat

Securely connect your AI SDK agents to MCP servers

Give your GitHub agents only the access they need