vercel-connect

Obtain scoped OAuth tokens for third-party services via Vercel OIDC authentication.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/AarnavBaddam/skills --skill vercel-connect-aarnavbaddam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-connect
Source: https://github.com/AarnavBaddam/skills/tree/main/vercel-connect
Command: npx skills add https://github.com/AarnavBaddam/skills --skill vercel-connect-aarnavbaddam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @vercel/connect.

What problem does it solve? Applications and agents often need scoped OAuth tokens to call third-party APIs like Slack, GitHub, Linear, Snowflake, or MCP servers, but managing OAuth consent flows, token rotation, and credential storage is complex. Vercel Connect exchanges Vercel OIDC tokens for scoped third-party tokens so apps never handle raw provider credentials. ## Core Features & Use Cases - Token Exchange via CLI, SDK, or HTTP API: Use vercel connect CLI commands, the @vercel/connect JavaScript/TypeScript SDK, or direct HTTP calls authenticated with VERCEL_OIDC_TOKEN to obtain user-scoped, app-scoped, or JWT-bearer tokens. - Eve Agent Integrations: Helpers like connect, connectSlackCredentials, connectGitHubCredentials, and connectLinearCredentials wire token lifecycle and webhook verification into Eve connection and channel definitions without env vars. - Auth Framework Plugins: Plug connectors into Better Auth (@vercel/connect/betterauth) or Auth.js (@vercel/connect/authjs) as OAuth providers. - Use Case: An Eve agent needs to post Slack messages as a bot and receive verified Slack webhooks; registering a Slack connector and calling connectSlackCredentials("slack/myagent") handles both outbound tokens and inbound signature verification. ## Quick Start Run "vercel connect create slack" from your project folder, complete the browser registration, then use "vercel connect token <connector>" or the @vercel/connect SDK to get a token and call the Slack API.

Frequently Asked Questions about vercel-connect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get a Slack bot token with Vercel Connect?

Run "vercel connect create slack" from your project folder, complete the browser registration, then run "vercel connect token <connector> --subject app" for a bot token. In code, call getToken from @vercel/connect with subject type "app".

How do I connect an MCP server to my Vercel app?

Register the MCP server with "vercel connect create" passing the full endpoint URL, such as https://mcp.linear.app/mcp. The connector ID takes the form mcp.<host>/<name>, which you then pass to getToken or the Eve connect helper.

Does @vercel/connect work with Better Auth or Auth.js?

Yes, @vercel/connect/betterauth provides a connect helper for Better Auth's genericOAuth plugin, and @vercel/connect/authjs provides one for Auth.js OAuth2Config providers. Both require a providerId or id plus the connector UID.

Why must vercel connect commands run from the project folder?

Vercel Connect reads the local project context to auto-configure the connection, including connector naming, project access, and webhook setup. Running from an unrelated directory skips this auto-configuration and requires manual wiring.

What is the difference between user and app subject tokens?

User tokens act on behalf of a specific end user and require a user id, while app tokens act as the app itself with no consent flow and fail terminally if the connector is not installed. A third jwt-bearer mode supports RFC 7523 assertion-based exchange.