# Vercel Connect is now generally available > Source: > Published: 2026-08-25 00:00:00+00:00 [Vercel Connect](https://vercel.com/connect) is now generally available on all plans and in [v0](https://v0.app/vercel). 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. Register a connector [once from the CLI](https://vercel.com/changelog/vercel-cli-100-services). 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: Connect ships with [100+ preset connectors](https://vercel.com/changelog/vercel-connect-preset-connectors) for tools like [Notion](https://vercel.com/connect/notion) and [Workday](https://vercel.com/connect/workday), managed connectors for [Slack](https://vercel.com/connect/slack), [GitHub](https://vercel.com/connect/github), [Linear](https://vercel.com/connect/linear), [Salesforce](https://vercel.com/connect/salesforce), [Snowflake](https://vercel.com/connect/snowflake), and [Microsoft](https://vercel.com/connect/microsoft), plus generic OAuth, API key authentication, and MCP servers. Request a token only when your code needs one, with `getToken` : Switch the `subject` from the app to a named user and the token acts on that user's behalf, triggering the authorization flow when consent is needed. New at GA: **Fine-grained RBAC **controls who can create and manage connectors **Audit logs **record authorization and connector activity [ Token and trigger observability](https://vercel.com/changelog/vercel-connect-adds-observability-support) shows how tokens are used across projects Together with per-environment attachment, including [Custom Environments](https://vercel.com/changelog/vercel-connect-now-supports-custom-environments), and one-command revocation, external access becomes something your team can inspect, prove, and cut off in seconds. 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: **Better Auth**: `@vercel/connect/betterauth` **Auth.js**: `@vercel/connect/authjs` **AI SDK**: `@vercel/connect/ai-sdk` **MCP clients**: `@vercel/connect/mcp` [ eve](https://eve.dev/integrations): `@vercel/connect/eve` [ Chat SDK](https://chat-sdk.dev/docs/vercel-connect): `@vercel/connect/chat` 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: [GitHub Tools](https://github-tools.com/guide/vercel-connect), our open source tool layer for GitHub agents, plugs into eve through Connect via an [eve extension](https://vercel.com/changelog/vercel-connect-support-in-github-tools). Presets like `code-review` map to Connect scopes automatically, so tokens carry only the permissions the toolset needs: 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 [documentation](https://vercel.com/docs/connect) and the [launch blog post](https://vercel.com/blog/the-end-of-credential-sprawl-for-agents), or have your coding agent set up Vercel Connect for you with this prompt: