Stack Gems
Menu
WorkbenchBestNewSkillsLogAboutSubmit

Alternatives · Browser Automation

Chrome DevTools MCP alternatives (2026)

Chrome DevTools MCP: The MCP browser for agents that need real DevTools, not just clicks.

Its Catch: chrome-devtools-mcp@1.8.0 engines: "^20.19.0 || ^22.12.0 || >=23".

Below: 8 free or free-tier tools from the same category (browser automation tools), free and open source first, then the closest match by shared tags. Each keeps its own Catch.

  1. 1.Playwright MCPOfficial Microsoft MCP server for Playwright browser automation

    Free / OSS · Apache-2.0 · 38.4k GitHub stars

    VerdictThe standard way to give MCP clients browser access.

    CatchIt is a control interface, not a complete solution. You still need browser infrastructure (local Chromium or Browserbase). No built-in session management, authentication, or scaling.

  2. 2.ScraplingBSD-3 adaptive scrape/crawl framework + MCP

    Free / OSS · BSD-3-Clause · 88.5k GitHub stars

    VerdictBSD-3 adaptive scrape/crawl + MCP. Self-run framework vs Firecrawl-shaped APIs.

    CatchVs Firecrawl-style hosted scrape APIs: Scrapling is a library/framework you run (plus MCP), not a metered scrape SaaS with a managed anti-bot fleet. You own proxies, blockers, and ops; MCP does not erase site ToS or legal risk. Not a general browser-agent product like Browser Use/Steel.

  3. 3.BrowserSkillAttach coding agents to a real logged-in browser without interrupting the session

    Free / OSS · OSS/MIT · 9.2k GitHub stars

    VerdictMIT live-session browser bridge. The no-second-login wedge is real; inherited cookies and permissions are the Catch.

    CatchA live logged-in browser is also a live blast radius: the agent inherits cookies, tabs, permissions, and whatever account is open. Vs Stagehand, Browser Use, and Playwright MCP (separate browser instances or contexts): BrowserSkill trades isolation for continuity. Treat the attached session as the trust boundary, not as a sandbox.

  4. 4.CuaOpen computer-use drivers, sandboxes, MCP, and CUA-S1 decision models

    Free / OSS · AGPL-3.0 · 30.2k GitHub stars

    VerdictMIT computer-use stack with CUA-S1. Reach for desktop/OS control and sandboxes; audit the AGPL omni extra and paid cloud fleet boundary.

    CatchVs BrowserSkill, Stagehand, and Browser Use: Cua is the broader computer-use driver/sandbox/model stack, not only browser automation or a browser-session attach bridge. Optional `omni` extras pull AGPL Ultralytics; cloud fleets are paid. Audit extras and treat a fleet as infrastructure spend, not as part of the MIT core.

  5. 5.Invisible Playwright MCPMIT stealth Firefox Playwright MCP — not plain Chromium MCP

    Free / OSS · AGPL-3.0 · 2.8k GitHub stars

    VerdictMIT stealth Firefox MCP when plain Playwright MCP dies on anti-bot — only with explicit ToS/abuse judgment, not as default browser MCP.

    CatchVs official Playwright MCP: plain Chromium control — this is stealth Firefox. Vs Browser Use / Steel / Cua: those are agent frameworks or browser APIs; this is the MCP-first stealth layer. Anti-detect purpose → site ToS / abuse risk even though the license is clean.

  6. 6.Chrome MCP ServerMIT Chrome extension MCP server for your own browser

    Free / OSS · OSS/MIT · 12.5k GitHub stars · quiet 180d+

    VerdictThe quickest way to let an agent work in your logged-in Chrome — use a separate profile and keep expectations early-stage.

    CatchBecause it uses your real browser session, an agent can act as you on every site you are logged in to — point it at a separate Chrome profile for anything sensitive. The README still calls it early-stage, and the last commit was January 2026, so momentum has slowed. The extension is installed from GitHub releases, not the Chrome Web Store. Vs chrome-devtools-mcp (official from the Chrome DevTools team): that one gives DevTools-grade traces, Lighthouse and heap snapshots; mcp-chrome is about reusing your logged-in profile for everyday browsing tasks.

  7. 7.StagehandAI-native browser automation that mixes code and natural language

    Free / OSS · OSS/MIT · 25.7k GitHub stars

    VerdictThe right abstraction for browser automation that needs to survive UI changes.

    CatchAI calls add latency and cost. The natural-language parts are only as reliable as the underlying model. Debugging AI-driven steps is harder than debugging selectors.

  8. 8.Browser UseOpen-source framework for LLM-driven browser agents

    Free / OSS · OSS/MIT · 118k GitHub stars

    VerdictThe open-source foundation for browser-based AI agents.

    CatchYou need browser infrastructure—Browser Use is a framework, not a managed service. Token consumption scales with page complexity. Anti-bot measures will block you without stealth tooling.

FAQ

What are the best free alternatives to Chrome DevTools MCP?
Playwright MCP, Scrapling, BrowserSkill, Cua, Invisible Playwright MCP. All are reviewed on Stack Gems in the same category (browser automation tools); 8 free or open source.
What is the catch with Chrome DevTools MCP?
chrome-devtools-mcp@1.8.0 engines: "^20.19.0 || ^22.12.0 || >=23".
Is there an open-source alternative to Chrome DevTools MCP?
Yes: Playwright MCP (Apache-2.0), Scrapling (BSD-3-Clause), BrowserSkill (OSS/MIT), Cua (AGPL-3.0).

More