Frameworks and Adapters
Vercel Connect is available on all plans and is subject to the Vercel Connect terms
Vercel Connect integrations adapt connector tokens, consent, and webhook verification to the frameworks you already use. Choose an integration based on the task your application needs to perform.
| Integration | Package | Use it to |
|---|---|---|
| AI SDK and MCP | @vercel/connect/ai-sdk or @vercel/connect/mcp | Authenticate an MCP client, request user consent, and pass MCP tools to an AI SDK model |
| eve | @vercel/connect/eve | Authorize eve connections, supply channel credentials, and verify Connect OAuth gateway tokens |
| Chat SDK | @vercel/connect/chat | Supply adapter credentials and verify trigger-forwarded webhooks |
| Better Auth | @vercel/connect/betterauth | Sign users into an application through Connect with Better Auth |
| Auth.js | @vercel/connect/authjs | Add a Connect OAuth provider to Auth.js |
AI SDK and framework-agnostic MCP clients use the same
connectAuthProvider() implementation. Import it from the entry point that
matches your client.
Use the root @vercel/connect package when you need a provider token without a
framework adapter. Its APIs let you:
- Request app, user, federated, or exchanged tokens with
getToken()andgetTokenResponse() - Start an interactive authorization flow with
startAuthorization() - Select installations, scopes, audiences, resources, and authorization details
Follow the Quickstart to create and link a connector. See Tokens to choose a subject and scopes, and use the SDK Reference for the root API.
Every integration authenticates the calling project through Vercel OpenID Connect (OIDC). Link your local directory and pull a development token:
vercel link
vercel env pullVercel provides VERCEL_OIDC_TOKEN automatically after deployment. Your
connector must also have a project link
for each environment that requests credentials.
Was this helpful?
