oauth mcp tanstack-ai vercel-connect auth-flow

Vercel Connect adds TanStack AI OAuth support

`connectMCPTransport` lets TanStack AI agents call OAuth-protected MCP servers with token refresh handled by Connect, eliminating credential storage.

Summary

Removes credential management overhead from agent workflows and centralizes OAuth token lifecycle. Consent errors surface as redirects before model execution, not tool failures.

Why it matters

Removes credential management overhead from agent workflows and centralizes OAuth token lifecycle. Consent errors surface as redirects before model execution, not tool failures.

Implementation verdict

Replaces manual OAuth token handling in MCP client setup. Requires TanStack AI, Vercel Connect account, and MCP server endpoint. Ready now—code sample provided; integrate via `@vercel/connect/tanstack-ai` subpath.

Sources

1.Agents built with TanStack AI can now call OAuth-protected MCP servers through Vercel Connect, with no credentials for you to store or rotate
2.The provider is called before every MCP request, so the token is always fresh
3.If the user has not granted access, `createMCPClient` fails with a consent challenge before the model runs

Dev Signal

Get briefs like this in your inbox — free, every weekday.

100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.

Read the full issue →All briefs