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.