Explore MCP tools that let AI agents control browsers, navigate pages, and automate web interactions.
MCP Browser Automation tools are AI-powered software designed to help developers and teams tackle mcp browser automation-related tasks more efficiently. These tools are typically published as open-source projects on GitHub and can be integrated into existing workflows via MCP (Model Context Protocol), Claude Skills, or standalone agent frameworks. On Agent Skills Hub, we index 10 quality-scored mcp browser automation tools across languages including TypeScript, Rust, Shell.
In 2026, the AI agent ecosystem is maturing rapidly. MCP Browser Automation tools can significantly boost development efficiency by automating repetitive tasks, reducing human error, and providing intelligent suggestions. The top 3 tools — mcp-server-browserbase, chrome-devtools-mcp, obscura — have earned an average of 10,076 GitHub stars, reflecting strong community validation. 10 of the listed tools come with clear open-source licenses, ensuring freedom to use and modify.
When choosing a mcp browser automation tool, consider these factors: 1) Community activity — GitHub stars and recent commit frequency indicate reliability; 2) Integration method — check if it supports MCP, Claude, or your preferred agent framework; 3) Language compatibility — the most common language in this list is TypeScript; 4) Quality score — Agent Skills Hub's composite score evaluates code quality, documentation completeness, and maintenance activity. Our recommendation: start with mcp-server-browserbase — it ranks highest in both star count and quality score.
Allow LLMs to control a browser with Browserbase and Stagehand
The headless browser for AI agents and web scraping
Stealth browser automation that actually works. Runs Camoufox (custom Firefox) in Docker with zero Chrome DevTools Protocol exposure, real OS-level mouse and keyboard input via PyAutoGUI, and a JSON HTTP API + MCP server to control it all remotely. Watch it live via noVNC.
Open-Source Chrome extension for AI-powered web automation. Run multi-agent workflows using your own LLM API key. Alternative to OpenAI Operator.
🔮 Platform-neutral Browser Use for AI agents: real Chrome automation with a CLI + SDKs, no lock-in, dead simple.
Operations substrate for AI agents that use real software: 311 sites/tools, logged-in browsers, desktop apps, local tools, MCP, policy, evidence, AgentEnvelope v2, and self-repair.
Coral is an open-source, local-first session bridge that lets AI agents borrow a user's already-authenticated browser sessions on a per-site, per-action, fully audited basis.
| Tool | Stars | Language | License | Score |
|---|---|---|---|---|
| mcp-server-browserbase | ★ 3.3k | TypeScript | Apache-2.0 | 51 |
| chrome-devtools-mcp | ★ 44.7k | TypeScript | Apache-2.0 | 61 |
| obscura | ★ 16.6k | Rust | Apache-2.0 | 58 |
| docker-stealthy-auto-browse | ★ 56 | Shell | WTFPL | 45 |
| stagehand | ★ 23.3k | TypeScript | MIT | 55 |
| bluebox | ★ 191 | Python | Apache-2.0 | 32 |
| nanobrowser | ★ 12.4k | TypeScript | Apache-2.0 | 38 |
| open-browser-use | ★ 104 | JavaScript | MIT | 43 |
| Uni-CLI | ★ 88 | TypeScript | Apache-2.0 | 41 |
| coral | ★ 59 | Python | Apache-2.0 | 34 |
The top mcp browser automation tools in 2026 are mcp-server-browserbase, chrome-devtools-mcp, obscura. Agent Skills Hub ranks 10 options by GitHub stars, quality score (6 dimensions including completeness, examples, and agent readiness), and recent activity. The list is rebuilt every 8 hours from live GitHub data.
mcp-server-browserbase (3.3k stars) is the most adopted choice for general mcp browser automation workflows, written in TypeScript. chrome-devtools-mcp (44.7k stars) is a strong alternative. Pick by your existing stack: match the language and runtime your team already uses to minimize integration cost. If unsure, start with mcp-server-browserbase — it has the deepest community and the most examples online.
Avoid pre-built mcp browser automation tools when (1) your use case requires deep customization that the tool's plugin system doesn't support, (2) you have strict compliance requirements that ban third-party dependencies, (3) the tool's maintenance is inactive (last commit >6 months ago), or (4) your data volume is small enough that a 50-line custom script is cheaper than learning the tool. For most production workflows above 100 requests/day, the time savings from a maintained tool outweigh the customization loss.
MCP Browser Automation focuses specifically on explore mcp tools that let ai agents control browsers, navigate pages, and automate web interactions. Web Scraping is a related but distinct category — see https://agentskillshub.top/best/web-scraping/ for those tools. The two often appear in the same agent pipeline but solve different problems: choose mcp browser automation when your primary goal is the specific task, and web scraping when the workflow is broader.
For most teams, yes. mcp-server-browserbase has 3.3k stars worth of community testing, handles edge cases you haven't thought of, and ships with documentation. Build your own only when (1) your requirements are deeply non-standard, (2) you have a security/compliance reason to avoid OSS dependencies, or (3) the maintenance burden is small enough (<200 lines of code) that you'll save time long-term. The break-even point is usually around 2-3 weeks of dev time saved.
Most mcp browser automation tools listed are open source under permissive licenses (MIT, Apache 2.0). A handful offer paid managed/cloud versions on top of free self-hosted core. Always check the LICENSE file on each tool's GitHub repository before commercial use — some use AGPL or non-commercial restrictions that may not fit your deployment model.