Open-source browser automation and data collection tools for AI agents — browser-use, MediaCrawler, Scrapling, playwright-mcp, agent-reach, OpenCLI, AutoCLI, mcp-chrome and more. 5 派系完整对比.
Browser Automation tools are AI-powered software designed to help developers and teams tackle 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 30 quality-scored browser automation tools across languages including Python, TypeScript, JavaScript.
In 2026, the AI agent ecosystem is maturing rapidly. Browser Automation tools can significantly boost development efficiency by automating repetitive tasks, reducing human error, and providing intelligent suggestions. The top 3 tools — browser-use, MediaCrawler, Scrapling — have earned an average of 13,412 GitHub stars, reflecting strong community validation. 25 of the listed tools come with clear open-source licenses, ensuring freedom to use and modify.
When choosing a 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 Python; 4) Quality score — Agent Skills Hub's composite score evaluates code quality, documentation completeness, and maintenance activity. Our recommendation: start with browser-use — it ranks highest in both star count and quality score.
🌐 Make websites accessible for AI agents. Automate tasks online with ease.
小红书笔记 | 评论爬虫、抖音视频 | 评论爬虫、快手视频 | 评论爬虫、B 站视频 ｜ 评论爬虫、微博帖子 ｜ 评论爬虫、百度贴吧帖子 ｜ 百度贴吧评论回复爬虫 | 知乎问答文章｜评论爬虫
🕷️ An adaptive Web Scraping framework that handles everything from a single request to a full-scale crawl!
Give your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
Make Any Website & Tool Your CLI. A universal CLI Hub and AI-native runtime. Transform any website, Electron app, or local binary into a standardized command-line interface. Built for AI Agents to discover, learn, and execute tools seamlessly via a unified AGENT.md integration.
Make Any Website & Tool Your CLI. A universal CLI Hub and AI-native runtime. Transform any website, Electron app, or local binary into a standardized command-line interface. Built for AI Agents to discover, learn, and execute tools seamlessly via a unified AGENT.md integration.
The headless browser for AI agents and web scraping
AutoCLI is a Blazing fast, memory-safe command-line tool — Fetch information from any website with a single command. Covers Twitter/X, Reddit, YouTube, HackerNews, Bilibili, Zhihu, Xiaohongshu, and 55+ sites, with support for controlling Electron desktop apps, integrating local CLI tools (gh, docker, kubectl), now powered by AutoCLI.ai .
Chrome MCP Server is a Chrome extension-based Model Context Protocol (MCP) server that exposes your Chrome browser functionality to AI assistants like Claude, enabling complex browser automation, content analysis, and semantic search.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
A Claude Skill to give your agent the ability to use a web browser
Claude Agent SDK with a web browsing tool
```bash
$ npx skills add browserbase/skills
```Universal content grabber — fetch, normalize, and digest content from 7+ platforms (WeChat, XHS, X/Twitter, YouTube, Bilibili, Telegram, RSS)
The perfect companion for ClaudeCode/OpenClaw/Agent, Give your AI Agent the ability to reach information across the entire web, fetching real-time data from Bilibili, Zhihu, Twitter/X, YouTube, Weibo, Reddit, Facebook, Instagram, TikTok, Notion, Cursor and 55+ platforms with natural language — reusing your Chrome login session, no API keys needed.
Allow LLMs to control a browser with Browserbase and Stagehand
Open-Source Chrome extension for AI-powered web automation. Run multi-agent workflows using your own LLM API key. Alternative to OpenAI Operator.
Open source and self-hostable browser automation library for AI agents
AIPex: AI browser automation assistant, no migration and privacy first. Alternative to Manus Browser Operator、 Claude Chrome and Agent Browser
🌐Web Agent Protocol (WAP) - Record and replay user interactions in the browser with MCP support
QA Skills Directory QA Skills is a curated directory of testing-specific skills for AI coding agents (Claude Code, Cursor, Copilot, etc.).
An MCP server for parallel browser automation by AI agents with multiple cloud providers
A browser agent with a Google Chrome extension that can work in your browser. Based on Google Gemini 2.5 computer use model.
Browse the web, directly from Cursor etc.
Anti-detection browser server for AI agents — REST API wrapping Camoufox engine with OpenClaw plugin support
The only browser automation that bypasses anti-bot systems. AI writes network hooks, clones UIs pixel-perfect via simple chat.
MCP server for computer use & browser automation - screenshot, OCR, click, type, find_text, Chrome/Electron CDP, template matching. macOS, Windows & Android. Works with Claude, Cursor, and any MCP client.
| Tool | Stars | Language | License | Score |
|---|---|---|---|---|
| browser-use | ★ 93.4k | Python | MIT | 54 |
| MediaCrawler | ★ 49.5k | Python | — | 44 |
| Scrapling | ★ 48.8k | Python | BSD-3-Clause | 55 |
| playwright-mcp | ★ 32.4k | TypeScript | Apache-2.0 | 54 |
| Agent-Reach | ★ 19.3k | Python | MIT | 46 |
| OpenCLI | ★ 20.3k | JavaScript | Apache-2.0 | 52 |
| opencli | ★ 14.2k | TypeScript | Apache-2.0 | 54 |
| agent-browser | ★ 32.8k | Rust | Apache-2.0 | 50 |
| obscura | ★ 12.0k | Rust | Apache-2.0 | 52 |
| AutoCLI | ★ 2.6k | Rust | Apache-2.0 | 39 |
| stagehand | ★ 22.6k | TypeScript | MIT | 47 |
| mcp-chrome | ★ 10.7k | TypeScript | MIT | 39 |
| browser-tools-mcp | ★ 7.1k | JavaScript | MIT | 49 |
| firecrawl-mcp-server | ★ 6.3k | JavaScript | MIT | 57 |
| dev-browser | ★ 5.8k | TypeScript | MIT | 47 |
| skills | ★ 2.8k | JavaScript | — | 48 |
| feedgrab | ★ 357 | Python | MIT | 34 |
| autocli-skill | ★ 825 | — | — | 44 |
| mcp-server-browserbase | ★ 3.3k | TypeScript | Apache-2.0 | 51 |
| nanobrowser | ★ 12.4k | TypeScript | Apache-2.0 | 38 |
| browserable | ★ 1.2k | JavaScript | MIT | 30 |
| AIPex | ★ 1.1k | TypeScript | MIT | 40 |
| web-agent-protocol | ★ 492 | Python | MIT | 31 |
| qaskills | ★ 102 | TypeScript | — | 39 |
| parallel-browser-mcp | ★ 58 | TypeScript | Apache-2.0 | 45 |
| gemini-browser-agent | ★ 64 | JavaScript | — | 36 |
| browser-use-mcp-server | ★ 811 | Python | MIT | 35 |
| camofox-browser | ★ 199 | TypeScript | MIT | 42 |
| stealth-browser-mcp | ★ 619 | Python | MIT | 53 |
| native-devtools-mcp | ★ 77 | Rust | MIT | 37 |
The top browser automation tools in 2026 are browser-use, MediaCrawler, Scrapling. Agent Skills Hub ranks 30 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.
browser-use (93.4k stars) is the most adopted choice for general browser automation workflows, written in Python. MediaCrawler (49.5k 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 browser-use — it has the deepest community and the most examples online.
Avoid pre-built 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.
Browser Automation focuses specifically on open-source browser automation and data collection tools for ai agents — browser-use, mediacrawler, scrapling, playwright-mcp, agent-reach, opencli, autocli, mcp-chrome and more. 5 派系完整对比. 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 browser automation when your primary goal is the specific task, and web scraping when the workflow is broader.
For most teams, yes. browser-use has 93.4k 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 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.