# Vercel Connect: Secure access to external services for your agents

DevFeed: [Vercel Connect: Secure access to external services for your agents](<https://devfeed.tech/articles/vercel-connect-secure-access-to-external-services-for-your-agents-1140.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/vercel-connect-secure-access-to-external-services-for-your-agents>)

Author: Hannah Hearth

Published: 2026-06-17T00:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Vercel](<https://devfeed.tech/topics/vercel.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [SDKs](<https://devfeed.tech/topics/sdks.md>), [API](<https://devfeed.tech/topics/api.md>), [API keys](<https://devfeed.tech/topics/api-keys.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Slack](<https://devfeed.tech/topics/slack.md>), [Model Context Protocol](<https://devfeed.tech/topics/model-context-protocol.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [apis](<https://devfeed.tech/tags/apis.md>), [cli](<https://devfeed.tech/tags/cli.md>), [connectors](<https://devfeed.tech/tags/connectors.md>), [external](<https://devfeed.tech/tags/external.md>), [github](<https://devfeed.tech/tags/github.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [slack](<https://devfeed.tech/tags/slack.md>)

## AI overview

Vercel Connect gives apps and agents secure, runtime access to external services through scoped, short-lived tokens. It supports connector management, automatic token refresh, environment isolation, revocation, provider webhooks, and dedicated or generic connectors.

## Source excerpt

Vercel Connect lets your apps and agents access external services like Slack, GitHub, Salesforce, and your own custom APIs without storing a long-lived provider secret in your environment. You register a connector once, and your code requests scoped, short-lived tokens at runtime, only when it needs them. You can create a connector from your dashboard or the Vercel CLI: Your agent can then request a token from it at runtime, only when it needs it. The SDK fetches and refreshes that token automatically, so there is no secret for you to store or rotate by hand: Scoped tokens Each token is scoped to the task in front of it, with granularity that depends on the provider. A GitHub token can be limited to a single repository and read-only, instead of your whole organization. An agent gets exactly the access a task needs, never broad standing access to everything. A token can also be tied to a specific user instead of the app. It then acts with that user's identity and inherits their permissions, so the agent can do only what that user is allowed to do: Isolation and revocation A connector only works in the environments you attach it to, so you can run separate connectors for development, preview, and production. This means if a token leaks in development, it cannot be used against production: Because access is issued as tokens, you can revoke it with a single command, either your own or every token a connector has issued across all users and installations: Triggers Events can also flow from a provider to your app. With triggers enabled on a connector, Vercel Connect verifies the provider's incoming webhooks and forwards them to the projects you choose, so a new Slack message can reach an agent that acts on it. Triggers support Slack, GitHub, and Linear in Beta, and a connector can forward to up to three projects: Connectors and adapters Dedicated connectors for Slack, GitHub, Linear, Discord, Notion, Salesforce, Figma, and Snowflake are available from the dashboard, along