Vercel Connect
Vercel Connect is Vercel's connector and credential broker for agents: it lets an agent call external services through short-lived, scoped credentials instead of storing provider tokens inside the app or exposing them to the model. Source: Vercel, 2026-06-17
Current Source Snapshot
As of 2026-07-04, @vercel/connect latest is 0.3.2, published on 2026-07-02. The package also has an alpha dist tag at 0.0.4-alpha.6. Treat integration details as fast-moving and version-check the SDK before adopting it in a production agent. Source: npm registry, 2026-07-04
Security Model
The important design shift is credential exchange at runtime. Connect moves provider authorization out of the agent prompt/tool code and into a platform-managed connector boundary:
- the app identity is established through OIDC
- provider tokens are not stored directly by the app
- access is scoped by project and environment
- credentials can be short-lived and revoked
- user-level authorization can be separated from agent-level capability
- MCP/OpenAPI tools can be exposed without teaching the model token plumbing
For Kevin's stack, this belongs with Agent Security Model and MCP Server Architecture because it turns "agent has a tool" into a typed permission boundary. The lesson is not Vercel-specific: agent tool access should have identity, scope, expiry, auditability, and revocation.
Product Fit
Connect is the missing piece that makes Vercel Eve and Personal Agent Template credible in real work surfaces. Linear, Slack, GitHub, Snowflake, Salesforce, and Notion-style integrations need account linking and permission scope before they need clever prompting. A personal agent that can message Slack, update Linear, and save memory needs visible connector state and revocation controls.
The public-beta bookmark frames the immediate scope as Slack, GitHub, Salesforce, and custom services reached through short-lived tokens scoped to each task. That makes Connect a task-scoped credential broker, not a generic secret manager. Source: X/@vercel_dev, 2026-06-17; Source: Vercel changelog, 2026-06-17
Adoption Rule
Before adopting Connect in Kevin's stack, record:
- the exact
@vercel/connectversion - which providers are enabled
- which scopes each provider receives
- whether credentials are user-scoped, app-scoped, or both
- how tokens are revoked
- how tool calls are logged in the agent run proof
Timeline
- 2026-06-17 | Vercel introduced Connect alongside Eve as the external-service credential boundary for agent apps. Source: Vercel blog, 2026-06-17
- 2026-07-01 | Verified
@vercel/connect@0.3.1as the current npm release while reviewing the Personal Agent Template bookmark. Source: npm registry, 2026-07-01 - 2026-07-04 | Source-reviewed the public-beta X bookmark and refreshed the package snapshot to
@vercel/connect@0.3.2; the key durable boundary is task-scoped short-lived tokens for external services. Source: X/@vercel_dev, 2026-06-17; Source: npm registry, 2026-07-04