No release verdicts yet. Scored jobs show how many tools were tested. The rest are not tested.

Queue

MCP2 · measured scores only

Browser Use vs Playwright MCP

For Let an agent control a browser.

Playwright MCP scored 91/100 and Browser Use scored 45/100. The gap is 46 points on the rubric. Nothing else is inferred.

Last tested:

Browser Use

45 / 100

Rank 4 on this job · tested 16 Oct 2026

Playwright MCP

91 / 100

Rank 2 on this job · tested 16 Oct 2026

Rubric breakdown

  • Job result (40)8 Browser Use40 Playwright MCP
  • Speed and effort (15)4 Browser Use13 Playwright MCP
  • Price and free tier (15)15 Browser Use15 Playwright MCP
  • Ease of start (10)5 Browser Use8 Playwright MCP
  • Reliability and trust (10)5 Browser Use8 Playwright MCP
  • Community signal (10)8 Browser Use7 Playwright MCP

Evidence · Browser Use

npm browser-use 0.9.0 (the package calls itself an unofficial TypeScript port) with --provider ollama. It opened http://127.0.0.1:8092/login, then failed: the model does not support multimodal requests. Login, the form, the table, and a screenshot were not completed. Killed at 70s. Evidence: evidence/2026-10-16/batch3/browser-use/task.err.

Evidence · Playwright MCP

Playwright MCP (server Playwright 1.64.0-alpha) logged into the demo, snapshotted the inventory table, saved note mcp-form-ok, and wrote page.png. Evidence: evidence/2026-10-16/batch3/playwright-mcp/.

Back to Let an agent control a browser · How we rank

Newsletter

The weekly ranking note

One email when a job gets a tested top five, a price changes, or a tool ships something we re-test. No sponsored placements.