realPubkey
Joined 9 years ago
Joined 9 years ago
WebMCP is currently being incubated in W3C [1], so if it lands as a proper browser standard, this becomes a endpoint every website can expose.
I think browser agents/skills+WebMCP might actually be the killer app for local-first apps [2]. Remote APIs need hand-crafted endpoints for every possible agent action. A local DB exposed via WebMCP gives the agent generic operations (query, insert, upsert, delete) it can freely compose multiple steps of read and writes, at zero latency, offline-capable. The agent operates directly on a data model rather than orchestrating UI interactions, which is what makes complex things actually reliable.
For example the user can ask "Archive all emails I haven't opened in 30 days except from these 3 senders" and the agent then locally runs the nosql query and updates.
The goal is to let agents interact with apps through explicit tools instead of DOM scraping or visual navigation. This works nicely because agents can run operations directly on the local-first data the UI already uses.
https://rxdb.info/articles/websockets-sse-polling-webrtc-web...