Shipping WebMCP in docs pages: 13 tools for the browser agent, plus Chrome 153 gotchas
DavidAntoon · reddit · 2026-10-27
The FrontMCP maintainer details running a WebMCP server inside docs pages: via document.modelContext, a site registers 13 tools (searchdocs, getpage, runinplayground, etc.) that browser agents call directly instead of screenshot-clicking. Loading is 3-phase (5.4KB manifest, 540KB on first agent call, 311ms first call then 1-4ms). Key Chrome 153 gotchas: tool error messages are hidden from agents (put info in results), consequentialHint isn't returned, and Chrome for Testing enables WebMCP by default, which broke Lighthouse scores until startup was deferred.
More from coding & agent
- Map of secure program synthesis: ruby-lean in Lean and the race to formally verify everything — burny_tech · 2026-10-27
- D3-Gym: first auto-constructed verifiable environments for data-driven scientific discovery, shown at EMNLP 2026 — hhsun1 · 2026-10-27
- If Your CLAUDE.md Is Longer Than Your README, Your Agent Gets Harder to Steer — Arindam_1729 · 2026-10-27
- When does checking an AI agent's work cost more than doing it yourself? — Live_Hedgehog8785 · 2026-10-27
- FrontierCS 2 launches on Kaggle with DeepMind: 48 tasks ask agents to beat published papers — lmoroney · 2026-10-27
- SkillHarm benchmark shows agent skill-poisoning attacks succeed up to 86.3% of the time — hhsun1 · 2026-10-27