vercel-connect

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

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/ridhijain709/AIPORSCHE --skill vercel-connect-ridhijain709
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-connect
Source: https://github.com/ridhijain709/AIPORSCHE/tree/main/.agents/skills/vercel-connect
Command: npx skills add https://github.com/ridhijain709/AIPORSCHE --skill vercel-connect-ridhijain709

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @vercel/connect.

What problem does it solve? Managing OAuth tokens, API credentials, and webhook secrets for third-party services like Slack, GitHub, Linear, and Snowflake requires manual app registration, env var juggling, and token rotation logic. Vercel Connect centralizes this by exchanging Vercel OIDC tokens for scoped third-party tokens, eliminating hand-managed secrets. ## Core Features & Use Cases - Scoped Token Issuance: Get user-scoped, app-scoped, or JWT-bearer tokens for Slack, GitHub, MCP servers, Snowflake, and generic OAuth providers via CLI, SDK, or HTTP API. - eve Agent Integration: One-line helpers (connectSlackCredentials, connectGitHubCredentials, connectLinearCredentials) wire outbound tokens and inbound webhook verification without SLACK_BOT_TOKEN or GITHUB_APP_PRIVATE_KEY env vars. - Auth Framework Support: Plug connectors into Better Auth or Auth.js as OAuth providers so credentials stay in Vercel Connect. - Use Case: You want your app to post Slack messages as a bot. Run vercel connect create slack, complete the browser consent, then call getToken(connector, { subject: { type: "app" } }) and use the token against the Slack API. ## Quick Start Ask the agent to set up a Vercel Connect connector for Slack and send a test message to a channel using the obtained token.

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-based Slack app installation, then call `getToken(connector, { subject: { type: "app" } })` from @vercel/connect or use `vercel connect token <connector>` in the CLI.

How do I connect my eve agent to an MCP server?

Register the MCP server with `vercel connect create https://mcp.linear.app/mcp`, then use `connect("mcp.linear.app/myagent")` from @vercel/connect/eve inside a `defineMcpClientConnection` definition. The helper handles the full token and authorization lifecycle.

Does Vercel Connect work with Better Auth or Auth.js?

Yes. Use `@vercel/connect/betterauth` with the genericOAuth plugin or `@vercel/connect/authjs` as an OAuth2Config provider. Both require passing a connector UID plus a providerId or id, and the respective framework as a peer dependency.

Can I use Vercel Connect outside JavaScript projects?

Yes. Make an authenticated POST to `https://api.vercel.com/v1/connect/token/<connector>` with your VERCEL_OIDC_TOKEN bearer token and a JSON subject body. The response contains a token field usable from any language, including Python.

Why should I run vercel connect commands from the project folder?

Vercel Connect reads the local project context to auto-configure the connector name, project access, webhooks, and triggers. Running from the repo root or an unrelated directory skips this auto-configuration and requires manual wiring afterward.

Do I still need SLACK_BOT_TOKEN or GITHUB_APP_PRIVATE_KEY env vars?

No, when using the eve helpers. `connectSlackCredentials` and `connectGitHubCredentials` return credential objects that fetch tokens server-side and verify inbound webhooks via Vercel OIDC, replacing hand-managed secrets entirely.