browser-harness
★ 19.1k
vs
Playwright MCP
★ 39.8k
browser-harness vs Playwright MCP
browser-harness: Browser Harness lets coding agents open pages, click, type, read and download in your real Chrome session over the DevTools Protocol. The agent writes any missing helper as it works, so the harness gains reusable abilities with each task.; Playwright MCP: Playwright MCP exposes browser operations to an MCP client through snapshots, actions and inspectable results. Our Chromium tests verified selected form, file and session workflows, while finding partial changes after a failed fill and a response-body timeout in one mixed workflow.
01
TL;DR
browser-harnessBrowser Automation · ★ 19.1k
When to choose:
- A coding agent needs browser actions in a deliberately chosen session or profile.
- You can review reusable helpers and implement visible outcome checks and error recovery.
When to skip:
- Your main requirement is deterministic CI testing of your own application with a clean browser.
- You expect the browser connection itself to enforce granular business permissions.
Playwright MCPBrowser Automation · ★ 39.8k
When to choose:
- You need structured controls and observable intermediate results for a browser workflow, and can implement snapshot refresh and checks after errors.
- You need to choose between isolated contexts and a dedicated persistent profile, and can manage browser binaries, profile paths and cookie lifetimes.
When to skip:
- Your requirement is proven model autonomy, visual-only canvas interaction, or compatibility with a real login provider; this review did not validate those.
- You require atomic form edits or fully verified response-body inspection across mixed error-recovery workflows; our measurements expose limits in those paths.
02
Side-by-Side Comparison
Field
Category
Browser Automation
Browser Automation
Stars
★ 19.1k
★ 39.8k
License
MIT
Apache-2.0
Install Command
uv tool install --python 3.12 'browser-harness[mcp]==0.1.13'
npx -y @playwright/[email protected]
Updated
1d ago
1d ago
Open Source
Yes
Yes
Tags
agent-framework, ai-agent, browser-agent
Playwright, Browser Automation, LLM Tools
03
Features
01Drives your running Chrome, logged in as you, over the DevTools Protocol
02Agents write missing helpers into a local workspace while the core source stays protected
03Set up by pasting one prompt into Claude Code or Codex
04Any MCP client can connect through browser-harness-mcp
01Accessibility snapshots and exact references for page controls
02Form fields, clicks, file choosers, downloads and dialog handling
03Default and named browser contexts, isolated sessions and profile directories
04Console messages, network request details and page screenshots
04
Use Cases
↳Have an agent complete tasks on sites where you are already logged in
↳Download your own content in bulk, such as your latest video posts on X
↳Give a coding agent browser actions such as uploading files
↳Inspect and complete labeled forms with state checks before retries
↳Verify file exchange and session boundaries in a local browser workflow
↳Explore a changed page using new snapshots and browser diagnostics
05
Best For
Most Popular
Most PopularEssentialTrending
FAQ
FAQ
What is the difference between browser-harness and Playwright MCP?
Both browser-harness and Playwright MCP are in the Browser Automation category. browser-harness has 19.1k stars, while Playwright MCP has 39.8k stars.
Which is better, browser-harness or Playwright MCP?
The best choice depends on your use case. Choose browser-harness if Have an agent complete tasks on sites where you are already logged in, and Playwright MCP if Inspect and complete labeled forms with state checks before retries.
Is browser-harness free or open source?
Yes, browser-harness is open source on GitHub (MIT).
Is Playwright MCP free or open source?
Yes, Playwright MCP is open source on GitHub (Apache-2.0).
Cloud Infrastructure
AdDeploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.
→