Vercel Connect now supports TanStack AI
TanStack AI agents can reach OAuth-protected MCP servers through Vercel Connect, with per-user token refresh and consent handled before model execution.
The **@vercel/connect/tanstack-ai** entry point adds **connectMCPTransport**, which attaches Vercel Connect authentication to a TanStack MCP transport and refreshes the token before each request.
Catch **getConsentChallenge** around createMCPClient and redirect to the supplied consent URL. Handling this before the model runs prevents authorization failures from becoming tool-error text in the conversation.
The **@vercel/connect/tanstack-ai** entry point adds **connectMCPTransport**, which attaches Vercel Connect authentication to a TanStack MCP transport and refreshes the token before each request. Catch **getConsentChallenge** around createMCPClient and redirect to the supplied consent URL. Handling this before the model runs prevents authorization failures from becoming tool-error text in the conversation. The material demonstrates an HTTP Linear MCP client with per-user identity, but does not describe support for other transport types, deployment environments, or failure recovery beyond consent.
This narrows remote MCP integration from generic connectivity to an explicit per-user authorization boundary: refresh credentials on every request and resolve consent before model execution. That prevents an authentication state from leaking into the agent’s conversational tool-error path. It is a concrete TanStack transport pattern, not yet evidence of portability across transports, deployments, or recovery scenarios.