WebMCP Runs In Chrome. My 400 Daily Tool Calls Don't.

Short summary

WebMCP, announced at Google I/O 2026, is a browser-scoped tool protocol that exposes tools to agents from inside a Chrome tab using the user's active session — it is not a replacement for headless stdio/HTTP MCP servers. The key decision factor is whether a human is present: WebMCP works for in-browser tasks like form filling and dashboard exports, while server-side MCP handles cron-driven, headless workloads like inbox triage and invoicing. The author shares a production Gmail triage MCP server handling 400+ daily tool calls with zero browser involvement, illustrating why conflating the two patterns leads to costly architecture mistakes.

• •WebMCP is browser-scoped: tools live in a Chrome tab, use the user's session, and only run while the tab is open
• •stdio/HTTP MCP servers run headless 24/7 with their own credentials, triggered by cron/webhooks — WebMCP cannot replace them
• •Decision rule: if a human is looking at a screen, WebMCP applies; otherwise use server-side MCP

Generated with AI, which can make mistakes.