Comment by DrScientist
6 hours ago
I guess I was asking - assuming that WebMCP isn't totally misguided - which of course is an assumption - is there anything that current accessibility standards can learn from WebMCP - ie why did they feel the need to create it?
I'm not aware of anything WebMCP could add that wouldn't be more useful as an improvement to accessibility tooling instead.
MCP is ultimately another solution to trying to make RPC(ish) situations more RESTful. I.e. they need self-documenting, discoverable APIs.
That's exactly what you can get from both HTML and the accessibility tree, though. We don't need another implementation for it. My guess (conjecture here) is that all the skills, MCP, WebMCP, etc talk is a manifestation of all the model providers and VCs backing them trying desperately to have others find ways to make LLMs worth the cost.