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.