WebMCP could kill much of browser automation: sites exposing functions instead of UI
thisiskp_ · x · 2026-08-31
The quoted thread argues that WebMCP might kill a surprising amount of browser automation if it takes off.
The logic: instead of teaching agents to see a button, understand it and click it, websites could just expose native functions like bookflight(), createlead(), sendmessage(), checkout(). We spent years making AI better at using websites like humans — maybe websites just needed to stop pretending the user is always human. The poster adds this as another possible side effect of WebMCP.
More from coding & agent
- Developer Switches Agent to OpenHands for Better Hackability — morgymcg · 2026-08-31
- Open Source video-use: Edit Videos with Claude Code Agents — Shruti_0810 · 2026-08-31
- Delete and Revalidate Agent Skills Often to Avoid Early Standardization — jdjohnson · 2026-08-31
- Teaching your agent how to use an app or OS is the perfect use for skills — BLUECOW009 · 2026-08-31
- BYOA: Websites Should Offer Skills, Not Agents — thisiskp_ · 2026-08-31
- Frontier coding agents lack self-knowledge, leading to bloated codebases — MinqiJiang · 2026-08-31