browser automation / debugging via MCP for AI agents
MCP server that lets AI coding agents control and inspect a live Chrome browser via Chrome DevTools, using Puppeteer for automation.
Same problem, same approach. Swapping one for another is a config change, not a rewrite.
Drop-in MCP server using Playwright; choose if you prefer Playwright's cross-browser support and tooling over Puppeteer.
Playwright Model Context Protocol Server - Tool to automate Browsers and APIs in Claude Desktop, Cline, Cursor IDE and More 🔌
MCP server with anti-bot stealth features; choose when you need to bypass bot detection while keeping MCP.
The only browser automation that bypasses anti-bot systems. AI writes network hooks, clones UIs pixel-perfect via simple chat.
Solves the same problem with a different architecture or at a different layer. Expect to rewrite the integration.
Python library approach for AI browser automation; choose when building agents in Python without MCP.
🌐 Make websites accessible for AI agents. Automate tasks online with ease.
Rust CLI for browser automation; choose when you want a lightweight terminal tool instead of an MCP server.
Browser automation CLI for AI agents
Turns websites into CLI commands using your logged-in browser; choose for CLI-style agent interaction.
Make Any Website into CLI & Use your logged-in browser by AI agent.
TypeScript SDK for browser agents; choose when you want programmable control rather than an MCP protocol.
The SDK For Browser Agents
Autonomous AI workflow automation for browsers; choose for task-level automation, not MCP-driven debugging.
Automate browser based workflows with AI
Autonomous browser toolkit for AI agents; choose if you prefer a direct agent API over MCP.
Let AI agents browse the web. An autonomous toolkit for browser-based AI agents.
Hosted open-source browser sandbox API; choose when you want managed browser infrastructure instead of local Chrome control.
🔥 Open Source Browser API for AI Agents & Apps. Steel Browser is a batteries-included browser sandbox that lets you automate the web without worrying about infrastructure.
CLI browser automation for AI agents with anti-bot and multi-session; choose when you need shell-level control instead of MCP.
Browser automation CLI built for AI agents. Break through anti-bot walls, hand off to humans across platforms when stuck. Parallel multi-task execution, independent multi-session operation, isolated multi-account browsing.
Vision-first browser agent; choose if you need visual reasoning rather than DevTools-based control.
Open-source, vision-first browser agent
Minimal Rust CLI driving browser via CDP for coding agents; choose for a tiny dependency-free CLI instead of MCP.
A tiny, fast Rust CLI that drives a real browser over the Chrome DevTools Protocol — built for coding agents.
Browser infrastructure for AI agents with token optimization; choose if you need cost-reducing browser automation patterns.
The Browser Infra that learns and cuts token spend by upto 90%
AI browser automation agent; choose for autonomous end-to-end tasks rather than interactive DevTools debugging.
AI Browser Automation
CLI + extension for using the real logged-in browser with AI agents; choose when you need to keep user sessions without MCP.
Let AI agents use your real, logged-in browser without interrupting your work. CLI + extension for browser automation across any shell-capable AI agent.
An earlier or more limited way to do the job. Still the right call when you need something small, proven, or CPU-only.
Narrow MCP server focused on JS reverse engineering and anti-detection; choose for that specialized debugging, not general DevTools work.
AI Agent-first JS 逆向 MCP Server：有头 Chrome 调试、断点、网络/WebSocket 分析、Patchright 反检测，可选 CloakBrowser。
These projects were analysed and named chrome-devtools-mcp among their alternatives. The relationship is not symmetric — how chrome-devtools-mcp rates them is a separate judgement, made when chrome-devtools-mcp is analysed in its own right.
calls chrome-devtools-mcp “When you need Chrome DevTools capabilities exposed via MCP for coding agents.”
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.
calls chrome-devtools-mcp “Choose this when coding agents need to inspect/debug a local Chrome through MCP, not Steel's remote managed browser service.”
🔥 Open Source Browser API for AI Agents & Apps. Steel Browser is a batteries-included browser sandbox that lets you automate the web without worrying about infrastructure.
calls chrome-devtools-mcp “Choose if you need Chrome DevTools debugging features via MCP, at the cost of launching a new browser instance rather than reusing your current session.”
MCP server that bridges clients to a real browser through CDP and a companion extension.