Vercel Connect is now generally available

Vercel Connect is now available on all plans and in v0, replacing the need to store long-lived provider secrets by issuing short-lived, scoped tokens at runtime. Deployments authenticate using existing Vercel OIDC identity, with tokens automatically refreshed and expiring independently. Users can register connectors once via the CLI, which pre-populates service details for over 100 preset connectors, including Notion, Workday, Slack, GitHub, and Salesforce, while supporting generic OAuth, API keys, and MCP servers.

The service allows switching tokens from app-level to user-level access, triggering consent flows as needed, and supports per-environment attachment, including Custom Environments. Teams can inspect, revoke, or cut off external access quickly. Triggers deliver provider events to applications without stored secrets, with server-side signature verification and OIDC re-attestation, even under Deployment Protection. Connect manages private keys and credential lifecycles, enabling standards-compliant OAuth without additional infrastructure.

Vercel Connect operates wherever functions run and is supported in v0, eve, and the Chat SDK. Adapters integrate with existing auth libraries and agent tooling, such as the AI SDK adapter for MCP client authentication and GitHub Tools for eve via a Connect extension. Preset connectors like code-review automatically map to minimal required scopes, ensuring tokens carry only necessary permissions.

Pricing for Vercel Connect is based on token requests and trigger events. The Hobby plan includes 500 token requests and 1,000 triggers per month at no extra cost. The Pro plan charges $3 per 1,000 token requests and $0.95 per 1,000 triggers, with custom pricing for Enterprise. Documentation and a launch blog post provide setup guidance, including a coding agent prompt for automated configuration.