BrowserMCP exposes browser automation through 12+ dedicated MCP tools, each with its own schema and parameters. The agent must learn every tool's interface and the MCP client must load all their schemas into context.

Playwriter has one tool: execute. It runs any Playwright code. The agent already knows Playwright from its training data, so there's nothing new to learn.

Every MCP tool adds its schema to the system prompt. With 12+ tools, that's thousands of tokens the agent pays on every request just to know what's available. Playwriter's single execute tool uses minimal schema space. The agent writes Playwright code, which it already knows from training.

BrowserMCP tools are fixed. If you need to do something the tool authors didn't anticipate, you're stuck. Playwriter lets agents run any Playwright code, plus raw CDP commands for advanced workflows like debugging, performance profiling, and live code editing.

12345# BrowserMCP: limited to what the tools expose
# Playwriter: anything Playwright can do

playwriter -s 1 -e "page.evaluate(() => performance.getEntriesByType('navigation'))"
playwriter -s 1 -e "state.cdp = getCDPSession({ page }); state.cdp.send('Network.enable')"