{"slug": "vercel-connect-is-now-generally-available", "title": "Vercel Connect is now generally available", "summary": "Vercel Connect is now generally available on all plans and in v0, allowing deployments to request short-lived, scoped tokens at runtime instead of storing long-lived provider secrets. The service includes 100+ preset connectors, fine-grained RBAC, audit logs, and token observability, with pricing starting at 500 token requests and 1,000 triggers per month free on Hobby, and $3 per 1,000 token requests and $0.95 per 1,000 triggers on Pro.", "body_md": "[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.\n\nRegister 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:\n\nConnect 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.\n\nRequest a token only when your code needs one, with `getToken`\n\n:\n\nSwitch the `subject`\n\nfrom the app to a named user and the token acts on that user's behalf, triggering the authorization flow when consent is needed.\n\nNew at GA:\n\n**Fine-grained RBAC **controls who can create and manage connectors\n\n**Audit logs **record authorization and connector activity\n\n[ Token and trigger observability](https://vercel.com/changelog/vercel-connect-adds-observability-support) shows how tokens are used across projects\n\nTogether 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.\n\nTriggers 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.\n\nConnect also manages private keys and the full credential lifecycle, so you get standards-compliant OAuth without building the infrastructure yourself.\n\nConnect 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:\n\n**Better Auth**: `@vercel/connect/betterauth`\n\n**Auth.js**: `@vercel/connect/authjs`\n\n**AI SDK**: `@vercel/connect/ai-sdk`\n\n**MCP clients**: `@vercel/connect/mcp`\n\n[ eve](https://eve.dev/integrations):\n\n`@vercel/connect/eve`\n\n[ Chat SDK](https://chat-sdk.dev/docs/vercel-connect):\n\n`@vercel/connect/chat`\n\nThe 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:\n\n[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`\n\nmap to Connect scopes automatically, so tokens carry only the permissions the toolset needs:\n\nVercel 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.\n\nRead 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:", "url": "https://wpnews.pro/news/vercel-connect-is-now-generally-available", "canonical_source": "https://vercel.com/changelog/vercel-connect-ga", "published_at": "2026-08-25 00:00:00+00:00", "updated_at": "2026-08-25 17:17:04.171671+00:00", "lang": "en", "topics": ["developer-tools", "ai-tools", "ai-agents"], "entities": ["Vercel", "v0", "Notion", "Workday", "Slack", "GitHub", "Linear", "Salesforce"], "alternates": {"html": "https://wpnews.pro/news/vercel-connect-is-now-generally-available", "markdown": "https://wpnews.pro/news/vercel-connect-is-now-generally-available.md", "text": "https://wpnews.pro/news/vercel-connect-is-now-generally-available.txt", "jsonld": "https://wpnews.pro/news/vercel-connect-is-now-generally-available.jsonld"}}