mcp-browser-use vs Browser Automation
mcp-browser-use is a plugin bundle for AI coding tools published by Igor Tarasenko. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Browser Automation is an MCP server published by mindstone. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace saik0s/mcp-browser-use | Listed Version: 0.3.0 Forks (GitHub): 110 Stars (GitHub): 972 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.6 Downloads/month (npm): 1 449 Downloads/week (npm): 673 Forks (GitHub): 4 Stars (GitHub): 14 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | mcp-browser-use | Browser Automation |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 972 (better) | 14 (worse) |
| Forks (GitHub) (differs) | 110 (better) | 4 (worse) |
| Last release (differs) | Not published | 2026-11-06 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@mindstone/mcp-server-browser-automation) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | 4, secrets among them: 0 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/saik0s/mcp-browser-use | github.com/mindstone/mcp-servers |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-11-04 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
mcp-browser-use
Browser automation via MCP - AI-driven web interactions with Playwright
Browser Automation
Browser automation MCP server: navigate, fill forms, click, screenshot, and manage tabs
How to run each
mcp-browser-use As a Claude Code plugin
/plugin marketplace add saik0s/mcp-browser-use
/plugin install mcp-browser-use@browser-use
Browser Automation As a local MCP server: npm package
claude mcp add --transport stdio mcp-server-browser-automation -- npx -y @mindstone/mcp-server-browser-automation
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only mcp-browser-use asks for
PYTHONPATH
Only Browser Automation asks for
AGENT_BROWSER_AUTOSAVE_INTERVAL_MSAGENT_BROWSER_SESSION_NAMEAGENT_BROWSER_SHOW_WINDOWMCP_WORKSPACE_PATH
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: mcp-browser-use · What it can do: Browser Automation · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.