WebMCP: Browser Standard for AI Agents to Interact with Websites
Google and Microsoft propose a W3C standard letting websites declare tools for AI agents instead of forcing agents to scrape and guess.
What to know
- WebMCP replaces brittle screen-scraping with declared tools: websites register what they offer (booking, filtering, checkout) so agents call them directly rather than guessing from HTML.
- The standard is a W3C Community Group draft co-developed by Google and Microsoft, live as a Chrome origin trial; now live in ChatGPT and Codex as well.
- Commenters debate whether this solves a real problem: some see efficiency gains for agent interactions, while others argue standard APIs or existing MCP already handle this, and question whether dual systems (human UI + agent API) will diverge.
The dispute Whether WebMCP is needed at all, or whether standard HTTP APIs and existing web standards already provide a cleaner, simpler solution. · positions read across 16 posts and comments
WebMCP addresses real inefficiency in agent-browser interaction and enables better use cases than screen-scraping.
-
“When I see Claude Code use Chrome via MCP, it's incredible to see just how inefficient the status quo is.”
suncemoje · Hacker News
Existing solutions (standard APIs, MCP, HTML forms) already solve this better without added complexity.
-
“We already have something better than WebMCP - i.e general APIs.”
dzonga · Hacker News
Pinning WebMCP to the browser is architecturally wrong and limits its utility.
-
“I think pinning WebMCP to the browser was the wrong choice. To list or call tools, you have to have access to the browser environment. This limits the utility of WebMCP to in-browser agents.”
shay_ker · Hacker News
WebMCP creates maintenance problems by requiring websites to maintain dual interfaces (human UI and agent API).
-
“If you maintain two versions of information, one for regular humans and one for agents, its just a matter of time before they start to diverge from each other.”
sandeepkd · Hacker News
“One way to think about WebMCP, as the article notes, is as web accessibility for agents. But since it functionally allows developers to expose any function on their website to an agent via RPC, the more interesting use cases are the ones that use the browser as a sandboxed execution environment.”
miguelspizza, HN commenter · Hacker News
Sreenath Menon WebMCP explainer and advocateGoogle Co-developer of WebMCP standardMicrosoft Co-developer of WebMCP standard
The record 1 articles and posts · last 30 days
What people are saying 15 voices from 1 site · best of 16 · verbatim
- Aug 27
-
Related. Others?WebMCP is available for early preview - https://news.ycombinator.com/item?id=47211249 - March 2026 (216 comments)Ask HN: What Is the Point of WebMCP? - https://news.ycombinator.com/item?id=47085076 - Feb 2026 (4 comments)WebMCP Proposal - https://news.ycombinator.com/item?id=47037501 - Feb 2026 (81 comments)WebMCP -…
- Aug 26
-
This is interesting, but instead of tying it to a specific JS library and all I’d prefer putting a list of options and their arguments into the .well-known tree.https://en.wikipedia.org/wiki/Well-known_URIThat way any user agent can get the data and make a call directly to the right endpoint with the right data. It could be an AI agent, a web…
-
IMO this relates to who the end consumer of websites ends up being. All the arguments for just using MCP ignore the reasoning that agents need based on contextual clues (e.g. if you're booking seats at a movie theaters, you'd want to choose based on personal preferences and taking the movie itself into account) and treat the website itself as the…
-
This is not a smart reply. Structure is always good otherwise why even create unit tests and compilers?
-
I agree it's not a good idea, but:> Remember this is the same information that every regular user is able to use.This is not true. The users don't see the HTML, CSS and JavaScript. If they would, even if they're frontend devs, they'll be just as confused as the agents.The user see images, and while you can make the agents see the image as well…
-
I think pinning WebMCP to the browser was the wrong choice. To list or call tools, you have to have access to the browser environment. "Declarative" WebMCP allows you to read the HTML, but to call tools you still need the JS execution env.This limits the utility of WebMCP to in-browser agents. In practice, what's the use case? Computer Use can…
-
I think it's an efficiency thing. And at scale, efficiency matters. Whether this is the right implementation idk, but when I see Claude Code use Chrome via MCP, it's incredible to see just how inefficient the status quo is.
-
It’s a nice idea but I don’t know if it will help.The history of the web is one big loop of:1. Nifty feature that’s suitable for a wide variety of user agents, from GUI browsers to screen readers to text interfaces to automation.2. Approximately 0.1% of web sites adopt it properly. The rest hack up something that mostly works for most of their…
-
This feels inverted and impractical in so many ways.On one hand the claims are being made that AI is smart enough to replace software engineers and on other hand the website owners are beings asked to provide information in a certain format to the Agents so they can do their job better. Remember this is the same information that every regular user…
-
This is going to sound incredibly silly but I have every HTMX component expose an AI summary with actions possible and then I have a small copy to AI button on the page which creates a new short-lived access token and copies into a prompt the token, and all the components as text.When I give this even to relatively small-model agents, they use…
-
It took me some time to wrap my head around why WebMCP even exists. I was thinking that regular MCP + SSE/Websockets could cover almost all of the uses cases.One interesting use case for WebMCP is cross-site activities that a browser agent might take. If the data-flow in question involves a heterogeneous set of websites.This feels like a lifeline…
-
Why would I want this client/browser side though?The only usecase I can image is if you have some terribly complicated legacy frontend and need to work around the logic built there. Otherwise just make an AI chat window or MCP which operates server side and let data sync back to UI from there.
-
Nice write-up. Btw, Codex and ChatGPT desktop support WebMCP in their integrated browser as of yesterday.One way to think about WebMCP, as the article notes, is as web accessibility for agents. But since it functionally allows developers to expose any function on their website to an agent via RPC, the more interesting use cases are the ones that…
-
> Here’s a book_table tool. It takes a date, a time, and a party size. Call it.Why not offer a simple form that humans and AI can use alike? <form action=book_table> <input type=date name=date> <input type=time name=time> <input type=number name=party_size> <input type=submit value="Book table"> </form>
-
we already have something better than WebMCP - i.e general APIs.more impactful work has to be done on the native legacy desktop app scene. that's where most of major companies big or small do their work.agents automating websites is kinda easy. automating legacy desktop apps that's another issue though there's RPA.