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, Python.
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 — oya-browser, mcp-server-browserbase, chrome-devtools-mcp — have earned an average of 16,179 GitHub stars, reflecting strong community validation. 8 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 oya-browser — it ranks highest in both star count and quality score.
The browser control plane for AI agents. One API over Oya Cloud, Browserbase, Steel, Anchor, Browser Use and your own Chrome, with persistent personas, CAPTCHA and MFA handling, and live human takeover.
Allow LLMs to control a browser with Browserbase and Stagehand
The headless browser for AI agents and web scraping
A Fully free agentic browser driver for AI , few tools, full control, real stealth, top-tier token efficiency.
Python APIs for Browser Automation, E2E Testing, and Web Scraping. CDP Mode bypasses bot-detection and handles CAPTCHAs. Includes a Stealth mode for Playwright.
Model Context Protocol server for Playwright with Chrome DevTools Protocol support
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.
Anti-detect agentic stealth browser: undetected browsing, browser automation, Python AI web browsing agent, computer use, scraping, lead generation. No captchas.
Playwright MCP server undetected by anti-bots and captchas: AI agent browses the web on anti-detect stealth Firefox, Python, undetected browser automation, scraping, computer use.
| Tool | Stars | Language | License | Score |
|---|---|---|---|---|
| oya-browser | ★ 349 | TypeScript | — | 75 |
| mcp-server-browserbase | ★ 3.4k | TypeScript | Apache-2.0 | 73 |
| chrome-devtools-mcp | ★ 52.9k | TypeScript | Apache-2.0 | 84 |
| obscura | ★ 28.3k | Rust | Apache-2.0 | 77 |
| bladebro | ★ 291 | Rust | Apache-2.0 | 62 |
| SeleniumBase | ★ 13.0k | Python | MIT | 72 |
| mcp-playwright-cdp | ★ 52 | TypeScript | — | 59 |
| docker-stealthy-auto-browse | ★ 85 | Python | WTFPL | 68 |
| aihawk_mcp_server | ★ 31.6k | Python | MIT | 88 |
| invisible_playwright_mcp | ★ 31.8k | Python | MIT | 83 |
The top mcp browser automation tools in 2026 are oya-browser, mcp-server-browserbase, chrome-devtools-mcp. 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.
oya-browser (349 stars) is the most adopted choice for general mcp browser automation workflows, written in TypeScript. mcp-server-browserbase (3.4k 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 oya-browser — 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. oya-browser has 349 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.
Grades come from a rule-based scan built on the SlowMist agent-security taxonomy, covering 11 red-flag categories including credential harvesting, data exfiltration, and curl | sh installers. It is a first-layer scan, not a manual audit — we say so rather than overstate it.
The scale of the problem is documented independently: Liu et al. (2026), in a study of 31,132 agent skills, report that 26.1% contain security vulnerabilities. Our own full-catalog census is published as a citable open dataset.
Sources & who's responsible:
