Playwright MCP
Microsoft's browser-automation server — agents drive a real browser through the accessibility tree instead of squinting at screenshots. Fast, deterministic, and a genuinely good idea.
What it actually does
Playwright MCP hands an agent a real browser it can navigate, click, type into, and read — but instead of feeding the model pixels, it exposes the page's accessibility tree as structured text. That makes interactions precise and cheap: no vision model, no guessing which blue rectangle is the submit button. It's built on Playwright, which has a decade of browser-automation scar tissue behind it, and ships as an npm package you can run with one command. The flip side of an agent with a browser is that the browser will happily visit anything, and every page it reads is untrusted input to your model.
Install
Read the source before you run this. Yes, actually.
From the desk
The Sunnyvale take
The accessibility-tree approach is the quiet engineering win here: everyone else screenshots the page and prays. This is what browser control for agents should look like — which is exactly why you should think twice before giving it your cookies.
Why it matters
A huge share of real-world tasks live behind a browser and have no API. This is currently the most credible way to let an agent at them.
In practice
Point Claude Code at a staging site and have it walk the signup flow, filing a bug with exact steps every time something doesn't match the spec.
The skeptic's note
Version numbers still start with 0.0 and the API moves. Treat it as a fast-improving tool, not settled infrastructure.
Use cases
- End-to-end testing driven by natural language
- Form filling and multi-step web workflows
- Scraping and verification on pages without APIs
Risks & caveats
The browser runs with whatever session state you give it. Web pages the agent reads are untrusted input — hostile page content can attempt prompt injection. Run it against a clean browser profile, never your logged-in daily driver.
Related tools
Full indexSame shelf, different trade-offs.
Fetch MCP Server
The reference web-fetch server: give an agent a URL, get back the page as readable markdown. Small, honest, and easier to misuse than it looks.
GitHub MCP Server
GitHub's official MCP server — lets an agent read repos, file issues, and push code with your credentials, which is exactly as useful and as dangerous as it sounds.