Every MCP Browser Tool Uses Chromium. That's a Problem.

The Model Context Protocol has a browser monoculture problem, and nobody's talking about it. I just searched the MCP server registry. There are at least 13 browser automation servers listed. Every single one requires Chromium -- Chrome DevTools Protocol, Puppeteer, Playwright with Chromium, or some wrapper around them. If your AI agent needs to interact with a web page, your only option has been "launch Chrome." This matters more than you think. Not because of some abstract browser diversity argument, but because Chrome is the single biggest resource drain in most developers' MCP setups -- and it's completely unnecessary for 95% of browser automation tasks. The Realization That Started This I run an automation business. My daily workflow involves Claude Code connected to 6-7 MCP servers simultaneously. One day I noticed my M2 MacBook Pro fans spinning up during what should have been a simple task -- the AI agent was just reading a dashboard and filling a form. I opened Activity Monitor