what bothers me is, while CRDTS converge, the question is to what. in this case, it seems like there's a last-write-wins semantic. which is very problematic as an implicit assumption for code(or anything where this isn't the explicit invaraint)
WebMCP is a protocol for exposing tools the AI can call from your running web app.
the point isn't "consume API tokens", it's "let the AI do stuff in your app" (click buttons, fill forms, read DOM state). The Gemini integration is just the orchestrator for the example implementation. not the protocol
Yes, but in practice, how do you connect AI to WebMCP? What is the point of a protocol that speaks MCP inside the browser if it's not reachable outside the browser?
Many browsers now have AI agents built into them. For example, Chrome has Gemini-in-Chrome, and Atlas has ChatGPT. When a user is on a website and then opens the built-in browser AI agent, the AI agent will see the WebMCP tool calls for that website and be able to call them.
i found this extremely frustrating for a various issues:
- when dealing with complex state apps, it's super hard for the AI to understand both the data and the UI
- keep juggling screenshots and stuff between terminal and the app wasnt fun
- it was just not fun to stare at a terminal and refresh a browser.
reply