@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.
⚡

Key Decision Metrics at a Glance

TL;DR Verdict
🏆 Benchmark RankRank
No model benchmark in this story · see current rankings
Full Leaderboard→
💰 Cost & PlansCompare
API & Subscription
Compare Plans↗
🛠️ Ecosystem & IDERules
Vercel · MCP handler · WebMCP
Setup IDE Rules↗
🧭

Turn your technical choice into a development budget

Compare 40 dev plans & simulate token costs vs $20/mo subscriptions

⚔️ Compare Model→💰 Compare plans & limits↗
Action HubReady to adopt this in production?

Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.

⚔️ Launch VS Compare→💳 View Plans↗
Up NextVercel CI enters beta: runs only the Turborepo tasks a change affects, 2-6x faster CI built for coding agents
Read Now→