The end of credential sprawl for agents
By Steven Van ·
Every useful agent reaches beyond your codebase. It posts to Slack, opens pull requests, queries Snowflake, or calls an internal API.
Vercel Connect, the platform's system for giving agents access to outside services, is now generally available after a public beta. Instead of provisioning a long-lived token and storing it in a vault, an app requests a token at runtime, scoped to the task and expiring on its own. Every Vercel deployment carries an OIDC identity that proves who's asking, so there's no provider secret for the app to store or leak.
The connector catalog has grown past 100 presets, covering services like Slack, GitHub, Notion, Shopify, Salesforce and Workday, plus custom connectors via OAuth or API keys and any OAuth-capable MCP server. For GitHub specifically, requests can be scoped down to a single repository with read-only access rather than an org-wide grant. General availability also adds governance features for teams running Connect in production:
- Fine-grained RBAC controlling who can create and manage connectors
- Audit logs recording authorization and connector activity
- Token and trigger observability across projects
Connect supports per-environment attachment, including Custom Environments, and one-command revocation of a user's or all tokens. It works with eve agents and Chat SDK apps out of the box, with adapters for Better Auth, Auth.js, the AI SDK and MCP clients. Apps built in v0 get connectors wired up automatically during the build. Vercel Connect is available on all plans.
