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 use the browser as a sandboxed execution environment.

https://duckboard-webmcp.alexmnahas.workers.dev/ is an example of this, and I would love to see more.

Maybe instead of skills that require users to download arbitrary binaries to their computers, the skills could instead point to a domain that comes preloaded with that binary in Wasm and lets the agent interact with it over WebMCP?

The Apple standard-positions in this was a pretty good read, noting indeed that this is a parallel new way to define accessibility. https://github.com/WebKit/standards-positions/issues/670

I'd also throw in schema.org Potential Actions as longstanding precedent for declaring what is on offer from the page. https://schema.org/docs/actions.html

It does get a bit tricky though. WebMCP allows the page to respond to the agent. Where-as these other systems the page itself has to update and respond.