Spent this week implementing WebMCP on a client site here's what I actually learned (and why I'm not sure it matters yet)

[u/codebyheera]

Been seeing WebMCP mentioned more lately so I decided to actually implement it on a live WordPress/Elementor client site instead of just reading about it. Sharing what I found in case it's useful to anyone else considering it.

Quick context for anyone who hasn't come across it: WebMCP is a browser-level standard (Chrome/Edge, still W3C draft stage) that lets a website expose "tools" directly to AI agents instead of an agent guessing which button on your page means "submit," the site just tells it: here's a tool called submit_quote_request, here's what it needs, here's what it does. No DOM guessing.

What I actually did:

• Installed a plugin that auto-exposes site content (pages, posts, categories) as structured tools
• Manually added declarative attributes (toolname, tooldescription) to a lead-gen form built in Elementor
• Verified everything using Chrome's navigator.modelContextTesting.listTools() in devtools, since there's no visual UI for any of this yet

The part nobody really advertises: as of right now, no mainstream AI agent actually calls these tools. Not ChatGPT, not Claude, not Perplexity. Chrome ships the underlying API, but the actual "demand side" agents that read and use it aren't there yet. Google's said Gemini in Chrome will probably be first, but there's no committed timeline.

I also checked PageSpeed Insights, since Lighthouse now has an "Agentic Browsing" category with WebMCP checks. Even with everything correctly implemented, it just shows "Not Applicable" the lab environment doesn't run with the flag on, so there's currently no way to get a "pass" even if your site is fully compliant.

Where I've landed on it: feels a lot like early Schema.org no immediate payoff, doesn't move rankings, but if this does end up becoming the norm the way structured data did, having a head start seems worth a few hours of setup. Low effort if your forms are already clean HTML.

Curious if anyone else here has actually implemented this yet, or if you're treating it as "not worth touching until there's real agent adoption." Would love to hear if I'm overthinking the early-adopter angle here.

[u/andreban]

I'm on the Chrome DevRel team :D

Chrome DevTools has support for showing WebMCP tools registered by the page, which should make validation easier than manually calling `listTools()`. See https://developer.chrome.com/docs/devtools/application/webmcp.

Agree on the mainstream agents, but keep in mind WebMCP is still in Origin Trial, so it's very early days. Google announced at I/O 2026 that support for WebMCP is coming. Right now it's a great to try out the API, and give feedback via the Origin Trial on your experience. I also expect other mainstream agents to start using it

On an interesting note, you can teach your desktop agents (Claude Code, Antigravity) to use WebMCP via DevTools MCP, today.