{
  "schema_version": "1.1",
  "id": "s4:https://vercel.com/changelog/webmcp-mcp-handler",
  "slug": "webmcp-mcp-handler-12gs586",
  "url": "https://feed7.dev/p/webmcp-mcp-handler-12gs586",
  "title": "WebMCP support now available in mcp-handler",
  "why_included": "mcp-handler 2.2.0 can expose selected MCP tools to in-browser agents through one script, proxying calls as the signed-in user without separate browser OAuth.",
  "summary": "**mcp-handler 2.2.0** adds experimental **WebMCP** support. Developers opt tools into experimental_webMcp, then load a script from the MCP endpoint with the webmcp-script query parameter.",
  "practical_implication": "If you already maintain MCP tools, this offers a short path to reuse selected ones inside browser agents. The generated script registers them on the page and proxies calls to the existing server as the signed-in user.",
  "agent_context": "**mcp-handler 2.2.0** adds experimental **WebMCP** support. Developers opt tools into experimental_webMcp, then load a script from the MCP endpoint with the webmcp-script query parameter.\n\nIf you already maintain MCP tools, this offers a short path to reuse selected ones inside browser agents. The generated script registers them on the page and proxies calls to the existing server as the signed-in user.\n\nWebMCP remains a proposed standard and this integration is explicitly experimental. Tool exposure should therefore be narrow, with authentication and authorization checked at the server boundary.",
  "source": {
    "name": "Vercel",
    "url": "https://vercel.com/changelog/webmcp-mcp-handler",
    "published_at": "2026-09-18T18:00:00.000Z"
  },
  "source_class": "blog_post",
  "content_type": "Engineering Post",
  "layer": "context",
  "domains": [
    "coding"
  ],
  "topics": [
    "mcp",
    "tool-use"
  ],
  "verification": {
    "status": "official_source",
    "label": "Official Source",
    "method": "source_feed",
    "verified_at": null
  },
  "uncertainty": [
    "WebMCP remains a proposed standard and this integration is explicitly experimental. Tool exposure should therefore be narrow, with authentication and authorization checked at the server boundary."
  ],
  "connected_context": {
    "meaning": "This creates a direct reuse path from existing MCP servers into browser agents, reducing the need to rebuild selected tools for page contexts. Against the candidates, it advances discoverability beyond passive agent instructions but introduces a sharper authority boundary: calls execute through the existing server as the signed-in user. Because both WebMCP and the integration are experimental, narrow exposure and server-side authorization remain implementation requirements.",
    "corpus_size": 812,
    "generated_at": "2026-09-19T09:04:33.583Z",
    "connections": [
      {
        "title": "Rebuilding the web for agents — Liad Yosef, MCP Apps",
        "source_name": "AI Engineer",
        "source_url": "https://www.youtube.com/watch?v=waI44NP1abk",
        "feed7_url": "https://feed7.dev/p/rebuilding-the-web-for-agents-liad-yosef-mcp-apps-0c3fgjh",
        "reason": "WebMCP provides the callable, discoverable interface that the observed failure of passive llms.txt instructions suggests agent-ready sites need."
      },
      {
        "title": "Latest MCP spec now supported in mcp-handler",
        "source_name": "Vercel",
        "source_url": "https://vercel.com/changelog/latest-mcp-spec-now-supported-in-mcp-handler",
        "feed7_url": "https://feed7.dev/p/latest-mcp-spec-now-supported-in-mcp-handler-1kkt3s0",
        "reason": "The earlier mcp-handler upgrade defines runtime and protocol prerequisites that existing deployments may need to satisfy before adopting this newer browser-facing capability."
      },
      {
        "title": "ChromeDevTools/chrome-devtools-mcp",
        "source_name": "GitHub",
        "source_url": "https://github.com/ChromeDevTools/chrome-devtools-mcp",
        "feed7_url": "https://feed7.dev/p/chrome-devtools-mcp-0ow49x2",
        "reason": "Chrome DevTools MCP gives agents browser control from an external tool server, whereas WebMCP exposes selected site-owned tools on the page; together they clarify complementary automation and application-action surfaces."
      },
      {
        "title": "MCP Apps: Extending the Frontier — Ido Salomon & Liad Yosef",
        "source_name": "AI Engineer",
        "source_url": "https://www.youtube.com/watch?v=-jY2T2PiJBE",
        "feed7_url": "https://feed7.dev/p/mcp-apps-extending-the-frontier-ido-salomon-liad-yosef-1gtlsr9",
        "reason": "MCP Apps returns sandboxed interfaces under host control, while WebMCP registers page tools that proxy authenticated server calls, making authorization more central than UI rendering."
      }
    ]
  },
  "lifecycle": "Current",
  "published_at": "2026-09-18T18:00:00.000Z",
  "modified_at": "2026-09-18T18:00:00.000Z",
  "supersedes": [],
  "expires_at": null,
  "formats": {
    "html": "https://feed7.dev/p/webmcp-mcp-handler-12gs586",
    "json": "https://feed7.dev/p/webmcp-mcp-handler-12gs586.json",
    "markdown": "https://feed7.dev/p/webmcp-mcp-handler-12gs586.md"
  }
}