Vercel Connect is now generally available
By Steven Van ·
Vercel Connect is now generally available on all plans and in v0.
Vercel Connect is now generally available on all plans and in v0. Instead of storing long-lived provider secrets, code requests short-lived, scoped tokens at runtime, and deployments authenticate with their existing Vercel OIDC identity. Each token is scoped to the task, refreshes automatically, and expires on its own.
A connector for any service can be registered with one CLI command: passing a service name pre-populates its brand name, icon, auth type, and MCP or discovery URL, then prompts for any credentials it needs. Connect ships with 100+ preset connectors for tools like Notion and Workday, managed connectors for Slack, GitHub, Linear, Salesforce, Snowflake, and Microsoft, plus generic OAuth, API key authentication, and MCP servers. At runtime, getToken requests a token scoped to an app or to a named user, triggering an authorization flow if the user hasn't consented yet.
New at general availability:
- Fine-grained RBAC controlling who can create and manage connectors
- Audit logs for authorization and connector activity
- Token and trigger observability showing how tokens are used across projects
- Per-environment attachment, including Custom Environments, and one-command revocation
Triggers deliver provider events to a project without a stored webhook secret: Connect verifies signatures server-side and re-attests each event using an OIDC identity, even when Deployment Protection is enabled. Connect works wherever Vercel functions run, and is supported in v0, eve, and Chat SDK, with adapters for Better Auth, Auth.js, the AI SDK, MCP clients, eve, and Chat SDK.
Pricing is 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. Full details are in the announcement.
