WebMCP support now available in mcp-handler
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.
**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.
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.
**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. 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. 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.
This turns existing server-side MCP tools into an experimental browser-agent surface with relatively little duplication. It narrows the opportunity to explicitly selected tools and makes server-side identity and authorization decisive, since calls are proxied as the signed-in user. Because WebMCP is proposed and experimental, compatibility and real browser journeys still need direct testing.