Live in Chrome 146 Canary — MCPHubz Exclusive Coverage

Google's WebMCP:
The Complete Guide

WebMCP is the browser-native evolution of the Model Context Protocol. Every website becomes a structured AI tool — no server, no scraping, no API keys. Chrome ships it. We explain it first.

What is WebMCP?

WebMCP is a W3C browser standard that allows web pages to expose structured tools and resources directly to AI agents — natively, inside the browser, without any server infrastructure.

Proposed by Patrick Brosset (Google) and co-authored with Microsoft, WebMCP extends the Model Context Protocol into the browser through a new navigator.modelContext API.

The result: any website can become a first-class AI tool without building a separate MCP server. The AI agent uses the browser's existing session, auth, and DOM access.

W3C Standard
Co-authored by Google and Microsoft. Submitted to the W3C WebML Working Group.
Chrome 146 Canary
First browser implementation. Enable via chrome://flags/#webmcp
Browser-Auth Security
Uses existing browser sessions — no API keys exposed, no new auth flows.
Two APIs
Declarative HTML meta tags + Imperative JavaScript via navigator.modelContext

WebMCP Timeline

Jan 2026
Patrick Brosset (Google) proposes WebMCP to W3C WebML Working Group
Feb 2026
Microsoft joins as co-author. Spec published at webmachinelearning.github.io
Feb 19, 2026
Forbes covers WebMCP — "The Browser-Based Backbone for the Agentic Web"
Feb 23, 2026
Brosset publishes clarifications and next steps on his personal blog
Mar 2026
Chrome 146 Canary ships WebMCP behind a flag — first browser implementation
Q2 2026
Expected stable Chrome release. Edge and Firefox implementations in progress

MCP vs WebMCP

They are complementary, not competing. WebMCP extends MCP into the browser.

AspectMCP (Server)WebMCP (Browser)
Where it runsServer-side (Node.js, Python, etc.)Browser-native (client-side)
Setup requiredInstall server, configure clientZero setup — any webpage can expose tools
Transportstdio, SSE, HTTPBrowser APIs (navigator.modelContext)
AuthAPI keys, OAuth via serverBrowser session / existing login
ScopeDeveloper tools, APIs, databasesEvery website on the internet
AI access modelTool invocation via AI clientDeclarative HTML + Imperative JS
Chrome 146 Preview

Try WebMCP Today

WebMCP is available behind a flag in Chrome 146 Canary. Enable it today and start experimenting with the API.

  1. Download Chrome 146 Canary
  2. Navigate to chrome://flags/#webmcp
  3. Enable the WebMCP flag and restart Chrome
  4. Open DevTools Console and type navigator.modelContext
webmcp-register.js

// Declarative HTML approach

<meta name="mcp-tool" content="search_servers" />

// Imperative JS approach

await navigator.modelContext.registerTool(({

name: "search_servers",

description: "Search MCP directory",

execute: async (p) => searchAPI(p.query)

})

// MCPHubz is already WebMCP-ready ✓

What WebMCP Unlocks

E-commerce AI

Any shopping site can expose "add_to_cart", "search_products", "get_price" tools — no API key, no scraping.

Banking & Finance

Banks expose "get_balance", "transfer_funds", "pay_bill" directly to AI agents with full session auth.

SaaS Automation

Every SaaS app becomes natively AI-controllable without building a separate MCP server.

Content Publishing

CMS platforms expose "publish_post", "update_page", "get_analytics" to AI writing assistants.

Healthcare Portals

Patient portals expose "book_appointment", "get_results", "message_doctor" securely via browser auth.

Developer Tools

GitHub, Vercel, and Supabase dashboards become fully AI-navigable without separate integrations.

Stay Ahead of the WebMCP Curve

MCPHubz is the first platform to implement WebMCP. Subscribe for weekly updates as the spec evolves.