Stack Gems
Menu
WorkbenchBestNewSkillsLogAboutSubmit

Alternatives · Browser Automation

Cua alternatives (2026)

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

Its Catch: Vs 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.

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.Chrome DevTools MCPOfficial Chrome DevTools as an MCP server for coding agents

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

    VerdictThe MCP browser for agents that need real DevTools, not just clicks.

    Catchchrome-devtools-mcp@1.8.0 engines: "^20.19.0 || ^22.12.0 || >=23". 20.16 and 20.17 fail; 20.19 LTS is in engines. “Node ≥ 22.12” and “Node 20 fails” are both too blunt — README “LTS” is marketing; engines is the catch. A CLI is provided for use without MCP; official CLI docs call it experimental. Complementary to Playwright MCP —DevTools-grade traces, Lighthouse, heap snapshots, and --autoConnect, not a generic scraper or a Playwright replacement. Officially supports Google Chrome and Chrome for Testing only. Exposes browser content to the MCP client—do not point it at sensitive sessions. Usage statistics on by default (opt out with --no-usage-statistics). Needs a current Chrome.

  3. 3.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.

  4. 4.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.

  5. 5.UI-TARS DesktopApache-2.0 vision/GUI-agent desktop stack (Agent TARS)

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

    VerdictApache-2.0 GUI-agent desktop when you want vision operators — budget a VLM path; do not expect the ended Remote Operator trial.

    CatchVs Browser Use: LLM-DOM browser agents; UI-TARS is vision/GUI-agent first. Vs Cua: Cua is computer-use drivers/sandboxes/models; UI-TARS ships the desktop GUI-agent product. Needs a VLM (HF Apache-2.0 weights or VolcEngine/Doubao cloud); Remote Operator free trial ended 2025-08-20.

  6. 6.agent-desktopApache-2.0 desktop computer-use CLI — OS a11y refs, not pixels

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

    VerdictApache desktop computer-use when agents must drive native macOS apps by a11y refs — not agent-browser’s web CDP lane; Win/Linux still catching up.

    CatchProduction a11y drive is macOS-first — Windows/Linux a11y and input still Planned in the support matrix (cdylib ships wider). Vs agent-browser (Vercel Labs browser CDP/a11y refs): agent-browser is the web/browser CLI; agent-desktop is native desktop apps via OS accessibility. Needs Accessibility (+ Screen Recording/Automation for some features); do not hand it a logged-in machine without a sandbox story.

  7. 7.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.

  8. 8.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.

FAQ

What are the best free alternatives to Cua?
Playwright MCP, Chrome DevTools MCP, Scrapling, Invisible Playwright MCP, UI-TARS Desktop. All are reviewed on Stack Gems in the same category (browser automation tools); 8 free or open source.
What is the catch with Cua?
Vs 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.
Is there an open-source alternative to Cua?
Yes: Playwright MCP (Apache-2.0), Chrome DevTools MCP (Apache-2.0), Scrapling (BSD-3-Clause), Invisible Playwright MCP (AGPL-3.0).

More