On February 10, 2026, Google shipped something quietly revolutionary: **Chrome 146** includes the first browser-native implementation of WebMCP, hidden behind a feature flag. It's not the full spec. It's not enabled by default. But it's real, it works, and it signals that the AI-agent web is no longer theoretical. Here's everything developers need to know. --- ## What Shipped in Chrome 146 ### The Feature Flag WebMCP is available as a **DevTrial** — meaning it's implemented but not enabled by default. To try it: 1. Open `chrome://flags` 2. Search for `web-mcp` or `model-context` 3. Set the flag to **Enabled** 4. Restart Chrome Once enabled, you'll have access to the `navigator.modelContext` API and the declarative HTML attributes (`toolname`, `tooldescription`, `toolautosubmit`). ### What's Implemented | Feature | Status in Chrome 146 | |---------|---------------------| | `navigator.modelContext.registerTool()` | ✅ Implemented | | `navigator.modelContext.unregisterTool()` | ✅ Implemented | | `navigator.modelContext.listTools()` | ✅ Implemented | | Declarative `toolname` attribute | ✅ Implemented | | Declarative `tooldescription` attribute | ✅ Implemented | | `toolautosubmit` attribute | ✅ Implemented | | `SubmitEvent.agentInvoked` | ✅ Implemented | | Tool annotations (`readOnlyHint`, etc.) | ⚠️ Partial | | `.well-known/webmcp` discovery | ❌ Not yet | | Cross-origin tool invocation | ❌ Not yet | ### What's NOT Included Yet - **No built-in AI agent**: Chrome 146 provides the *API* for tools, but doesn't ship a built-in agent that uses them. Google's Gemini integration is expected in a future release. - **No `.well-known/webmcp` discovery**: The automatic discovery file isn't parsed yet. - **No cross-origin support**: Tools can only be registered and invoked within the same origin. --- ## The Declarative API in Action The biggest win for developers is the Declarative API. If your site has forms, you can make them AI-accessible with **zero JavaScript**: ```html ``` Three attributes. That's the entire migration. --- ## The Imperative API For dynamic tools that don't map to forms, the JavaScript API gives you full control: ```javascript // Register a tool const tool = await navigator.modelContext.registerTool({ name: "checkOrderStatus", description: "Check the delivery status of an order by order number", inputSchema: { type: "object", properties: { orderId: { type: "string", description: "The order ID (e.g., ORD-12345)" } }, required: ["orderId"] }, handler: async ({ orderId }) => { const response = await fetch(`/api/orders/${orderId}/status`); const data = await response.json(); return { status: data.status, estimatedDelivery: data.eta, trackingUrl: data.trackingUrl }; } }); // Later: unregister when no longer needed tool.unregister(); ``` --- ## SubmitEvent.agentInvoked Chrome 146 introduces a new property on form submission events: `SubmitEvent.agentInvoked`. This boolean tells your code whether a form submission was triggered by an AI agent or a human user: ```javascript form.addEventListener('submit', (event) => { if (event.agentInvoked) { // Submitted by AI agent console.log('AI agent submitted this form'); // Maybe skip CAPTCHA, log differently, etc. } else { // Normal human submission } }); ``` This is powerful for: - **Skipping CAPTCHAs** for agent-invoked submissions - **Analytics**: Track AI vs human interactions separately - **A/B testing**: Different flows for agents vs humans - **Rate limiting**: Apply different limits to agent traffic --- ## What This Means for Developers ### Short Term (Now - Q2 2026) - **Prepare your forms**: Add `toolname` and `tooldescription` to your key forms - **Test with the flag**: Enable WebMCP in Chrome 146 and verify your tools register correctly - **Use `navigator.modelContext.listTools()`** in DevTools console to see what Chrome discovers - **Audit your score**: Run [WebMCP Verify](https://webmcpverify.com) to see where you stand ### Medium Term (Q3-Q4 2026) - Chrome enables WebMCP by default - Microsoft Edge follows (same Chromium engine) - AI agents start appearing in browser sidebars and extensions - Early-adopter websites get preferential agent interactions ### Long Term (2027+) - Safari and Firefox implement WebMCP - WebMCP becomes an expected standard (like HTTPS) - Websites without WebMCP are invisible to AI agents - SEO evolves to include "AI discoverability" as a ranking factor --- ## Testing Your WebMCP Implementation ### In Chrome DevTools With the flag enabled, open Chrome DevTools Console and run: ```javascript // List all registered tools on the page const tools = await navigator.modelContext.listTools(); console.log(tools); ``` This shows you what Chrome has discovered from your `toolname` attributes and `registerTool()` calls. ### With WebMCP Verify For a comprehensive check that goes beyond just tool registration, use [WebMCP Verify](https://webmcpverify.com). It checks: - ✅ Declarative tool forms - ✅ Imperative API usage - ✅ Input field quality - ✅ AI discoverability (Schema.org, llms.txt, meta tags) - ✅ Security (HTTPS, CSP, mixed content) - ✅ Best practices (naming, descriptions, schemas) --- ## FAQ ### Do I need to wait for the flag to be removed? No. You can add WebMCP attributes to your forms **today**. They're standard HTML attributes that won't affect browsers that don't support them. When support arrives, your site will be ready automatically. ### Will this work in other browsers? Microsoft Edge (Chromium-based) will inherit Chrome's implementation. Firefox and Safari have observers in the W3C group but haven't announced implementation timelines yet. ### Does this replace my existing search/SEO strategy? No. WebMCP complements traditional SEO. Think of it as adding a new channel: your site is discoverable by both search engines AND AI agents. ### Is there a performance impact? Negligible. The Declarative API adds no JavaScript overhead — it's just HTML attributes. The Imperative API's impact depends on your handler implementations, but registering tools is lightweight. --- ## Key Takeaways 1. **Chrome 146 includes WebMCP** behind a feature flag (`chrome://flags/#web-mcp`) 2. **Both APIs work**: Declarative (HTML) and Imperative (JavaScript) 3. **Add attributes now**: They don't affect unsupported browsers 4. **`SubmitEvent.agentInvoked`** lets you distinguish AI vs human submissions 5. **Full rollout expected Q3-Q4 2026** — prepare now to be ahead of the curve 6. **Check your readiness** at [webmcpverify.com](https://webmcpverify.com) The browser is becoming an AI platform. Chrome 146 is the first concrete step.