WebMCP is on track to be a W3C spec, and I think it solves all of this in a very straightforward manner.
For frontend devs, this can be as simple as writing some new markup that exposes their controls as tools to the browser. Then when the LLM engages a registered tool, the UI hides navigation controls and expands the content. Not a ton of work, but huge payoff to stay relevant.
MCP tool descriptions aren't just functional, but ultimately the new hyperlinks in a new kind of SEO that digs into every facet of a site or app's design.
For frontend devs, this can be as simple as writing some new markup that exposes their controls as tools to the browser. Then when the LLM engages a registered tool, the UI hides navigation controls and expands the content. Not a ton of work, but huge payoff to stay relevant.
MCP tool descriptions aren't just functional, but ultimately the new hyperlinks in a new kind of SEO that digs into every facet of a site or app's design.
https://github.com/webmachinelearning/webmcp?tab=readme-ov-f...
TL;DR Imagine a web with less junk on the screen and more dynamic and accessible UI.