Playwriter vs BrowserMCP

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.

Comparison

	Playwriter	BrowserMCP
Tools	1 execute tool	12+ dedicated tools
API	Full Playwright	Limited actions
Context usage	Low	High (tool schemas)
LLM knowledge	Already knows Playwright	Must learn custom tools
CDP access	Yes	No
Debugger	Yes	No
Network interception	Full	No

Context usage

Every MCP tool adds its schema to the client's context. With 12+ tools, that's thousands of tokens the agent carries 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.

Capability ceiling

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 "state.page.evaluate(() => performance.getEntriesByType('navigation'))"
playwriter -s 1 -e "state.cdp = getCDPSession({ page: state.page }); state.cdp.send('Network.enable')"