@AverageAiBro notes Vercel mcp-handler 2.2.0 (github.com/vercel-labs/mcp-handler) ships experimental WebMCP: opt tools in under experimental_webMcp, load ?webmcp-script from your MCP endpoint, and in-browser agents reuse the same server tools proxied as the signed-in user—no second browser OAuth stack. Pin 2.2.0; the WebMCP path is still experimental.

Key Takeaways

  • One MCP endpoint plus ?webmcp-script lets in-browser agents call your existing tools.
  • Calls proxy as the signed-in user, so auth tools skip a second browser OAuth flow.
  • WebMCP is still experimental—pin mcp-handler 2.2.0 for now.
ADSponsored