vercel-connect

Obtain scoped OAuth tokens for Slack, GitHub, MCP servers, and Snowflake via Vercel OIDC.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @vercel/connect.

What problem does it solve? Managing third-party API credentials (Slack bot tokens, GitHub OAuth tokens, MCP server access, Snowflake credentials) usually means juggling env vars, manual OAuth flows, and token rotation. Vercel Connect centralizes this by exchanging Vercel OIDC tokens for scoped third-party tokens on behalf of apps or users. ## Core Features & Use Cases - Scoped token issuance: Get user, app, or jwt-bearer subject tokens for Slack, GitHub, MCP servers, Snowflake, and generic OAuth providers via CLI, TypeScript SDK, or HTTP API. - eve agent integrations: One-line helpers (connect, 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. - Use Case: Send a Slack message from your app by running vercel connect create slack, then calling getToken(connector, { subject: { type: "app" } }) and posting to the Slack API. ## Quick Start Ask the agent to create a Vercel Connect connector for Slack and use the token to send a message to a channel.

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

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

Register the MCP endpoint with `vercel connect create https://mcp.linear.app/mcp`, then in your eve connection definition use `connect("mcp.linear.app/myagent")` from @vercel/connect/eve as the auth handler.

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 providerId or id alongside the connector UID.

Can I use Vercel Connect without the Vercel CLI?

Yes. Non-JavaScript languages can call the HTTP API directly at api.vercel.com/v1/connect/token/<connector>, authenticated with the VERCEL_OIDC_TOKEN environment variable pulled via `vc env pull`.

Why should I run vercel connect commands 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 the repo root or an unrelated directory skips this and requires manual wiring.

Do I still need SLACK_BOT_TOKEN or GITHUB_APP_PRIVATE_KEY env vars with eve channels?

No. The connectSlackCredentials, connectGitHubCredentials, and connectLinearCredentials helpers handle token rotation and verify inbound webhooks via Vercel OIDC signatures, replacing those manually managed secrets.