Vercel Connect reaches GA with authenticated MCP for 100+ services

• Vercel Connect is now GA on every plan and exposes connectors for more than 100 services, according to the GA announcement.
• Agent code can request short-lived, task-scoped provider tokens at runtime rather than retain provider secrets in its own environment, as the GA announcement describes.
• A one-command connector can yield an MCP client that queries a service for an authenticated user, as rauchg's Notion example shows.
• v0 apps can attach Slack, GitHub, Notion, Salesforce, and other services through the same system, v0 said.
• The rollout also adds a managed Linq connector for iMessage, RCS, and SMS, while thelinqapp says it removes the need for a Linq API key in the deployment environment.

A deployment uses its existing Vercel OIDC identity to request a token through getToken, which can represent either the app or a named user. The same GA changelog describes a trigger path that verifies provider signatures server-side and re-attests events with OIDC, including for protected deployments.

Connect’s GA changelog specifies three properties for a provider grant:

• It is requested only when code needs it.
• It is scoped to the task and refreshes automatically.
• It expires on its own.

getToken('slack/acme-slack', { subject: { type: 'app' } }) mints an app credential; changing the subject to a named user makes the token act on that user’s behalf and initiates consent when needed. The connector creation flow still prompts for whatever credentials a provider requires, even though application code does not receive a persistent provider secret.

The CLI registers a connector once and fills in its auth type plus an MCP or discovery URL when the service preset has one. rauchg demonstrated the abbreviated path: vercel connect create notion, then an MCP client that can query Notion for the authenticated user.

Vercel’s AI SDK adapter wires the runtime grant into an MCP transport through connectAuthProvider. Its Linear example creates a client with a named-user subject and read scope, then exposes mcpClient.tools() to streamText.

v0 now exposes Connect directly for Slack, GitHub, Notion, Salesforce, and other services. A team sets up a connector once and reuses it across apps, according to Vercel’s v0 changelog.

GA adds a control plane around those reusable connections:

• Fine-grained RBAC for connector creation and management.
• Audit logs for authorization and connector activity.
• Token and trigger observability across projects.
• Per-environment attachments and one-command revocation.

Connect is available on all plans. The pricing details list 500 token requests and 1,000 triggers per Hobby month, then $3 per 1,000 token requests and $0.95 per 1,000 triggers on Pro.

Kernel’s integration gives an agent scoped, short-lived browser access on demand through Connect. Kernel separately keeps an authenticated browser profile and re-authenticates it when the session expires, usekernel said.

The Linq connector lets an agent receive a phone number and send or receive iMessage, RCS, and SMS; vercel_dev showed vc connect create linq --name my-agent as the setup command.

A Vercel deployment can use Linq without a Linq API key in its environment, thelinqapp said. The connector can also be added as an Eve channel with one command.