Google Chrome
WebMCP requires an eligible origin trial or the experimental testing flag. A compatible agent is also required.
Support detailsDiscover your tools, check compatibility, and find your next step.
Native WebMCP is emerging. A browser and its agent both need support.
WebMCP requires an eligible origin trial or the experimental testing flag. A compatible agent is also required.
Support detailsAvailable for experimentation through the Edge origin trial. Check trial eligibility and current expiry dates.
Support detailsExperimental Leo integration is reported by the specification project. Availability is not guaranteed for all users.
Support detailsPrototype work is tracked, but no native release is confirmed. Use standard browser automation or a remote MCP client.
Support detailsNative WebMCP cannot be assumed. Regular browser automation and separate remote MCP clients remain alternatives.
Support detailsCompatible agents can connect directly using a supported transport. Authentication and permissions still apply.
Support detailsRemote MCP is a separate route. A compatible agent can use a remote MCP server independently of the visitor’s browser. Browser automation can still use regular pages. This matrix describes platform support, not a cross-browser test of your website.
Token use and customer wait time, tailored to the page you scan.
We use the page size, visible controls, discovered tool schemas and observed request times. No savings are calculated until that evidence is available.
Search visibility, readable content and working tools are different things. Our 100-point rubric checks all three, and makes room for what a public scan can’t know.
Turn your website’s key journeys into tools AI agents can use. We’ll help you decide what to build, connect it, and measure the difference.
Let’s find your first agent-powered journey.