Browser Automationβ€’ MCP Alternatives Guide

Best Alternatives to BRYG

Looking for an alternative to BRYG? Whether you need a different runtime environment, custom authentication support, or alternative API integrations in the Browser Automation ecosystem, we have cataloged and compared the top alternative MCP servers below.

Browse all Browser Automation servers β†’View BRYG Specs β†’
BRYG logo
Target Reference Server

BRYG Overview

BRYG MCP server lets compatible AI clients operate a real Chromium-based browser on the local machine through a plain stdio MCP process. It supports tabs, navigation, accessibility snapshots, text and link extraction, mouse and keyboard actions, uploads, JavaScript evaluation, screenshots, OCR, QR decoding, and network observation. Reach for it when an agent needs to interact with websites as a visible browser user, including authenticated workflows and pages that require visual or coordinate-based actions. Chrome is supported on macOS, Windows, and Linux; Edge is available through the browser selection on supported setups, while Linux uses Chrome.

Primary Use Cases for BRYG:
  • Automate authenticated website workflows
  • Inspect and interact with dynamic web pages
  • Extract text, links, screenshots, or OCR results
  • Test forms, dialogs, uploads, and browser navigation

Specification Matrix: BRYG vs Alternatives

Direct comparison of key metrics, runtimes, authentication methods, and community popularity.

Server NameRuntimeAuthPricingGitHub StarsDownloadsAction
BRYG logoBRYG (Target)
npxβ€”Paidβ€”β€”Current
CDPM logoCDPMnpxNo auth requiredFree3β€”
Real Browser MCP logoReal Browser MCPnpxNo auth requiredFree58β€”
MCP Server Browser logoMCP Server BrowsernpxNo auth requiredFree39,582β€”
Ghostlight logoGhostlightnpxNo auth requiredFree1β€”
Weavetab logoWeavetabnpxNo auth requiredFree3β€”
Playwright MCP logoPlaywright MCPnpxNo auth requiredFree39,355β€”
Browserctl MCP logoBrowserctl MCPnpxNo auth requiredFreeβ€”β€”
Cloakbrowser MCP logoCloakbrowser MCPnpxNo auth requiredFree177β€”
MCP Server Playwright logoMCP Server PlaywrightnpxNo auth requiredFree297β€”
Invisible Playwright MCP logoInvisible Playwright MCPuvxAPI keyBring your own API key (usage-based cost)877β€”
Jev Browser logoJev BrowsernpxAPI keyBring your own API key (usage-based cost)130β€”
Browsermcp MCP logoBrowsermcp MCPnpxNo auth requiredFree7,318β€”

Detailed Evaluation of BRYG Alternatives

CDPM logo

CDPM

Runtime: npxBrowser Automation

Shares persistent numbered Chrome slots over CDP, letting multiple Claude Code sessions automate tabs and coordinate browser work.

Key Features:
Up to 30 persistent Chrome slots
Per-tab command queues for shared sessions
CDP-based mouse and keyboard automation
10 0 3
Real Browser MCP logo

Real Browser MCP

Runtime: npxBrowser Automation

Controls an existing Chrome session through MCP, preserving logged-in tabs, cookies, and SSO access.

Key Features:
Controls an existing Chrome session through a local extension
Preserves browser cookies, SSO state, and open tabs
Provides accessibility snapshots and screenshots
11 0 58
MCP Server Browser logo

MCP Server Browser

Runtime: npxBrowser Automation

Automates local or remote browsers through Puppeteer, accessibility data, optional vision mode, and MCP stdio or HTTP transports.

Key Features:
Puppeteer-based browser automation
Local and remote browser connections
Accessibility snapshots with optional vision mode
6 0 39,582
Ghostlight logo

Ghostlight

Runtime: npxBrowser Automation

Drive a real logged-in Chromium browser through MCP with tabs, forms, uploads, diagnostics, and policy controls.

Key Features:
Controls a visible logged-in Chromium browser
Supports semantic page inspection and interaction
Handles forms, uploads, dialogs, and child tabs
2 0 1
Weavetab logo

Weavetab

Runtime: npxBrowser Automation

Control local Chromium browsers and Electron apps through MCP with DOM mapping, interaction, scraping, credentials, and visual automation.

Key Features:
Semantic DOM maps with scoped queries and delta updates
Direct local CDP control for Chromium and Electron
Multi-action browser bursts for lower round-trip latency
0 0 3
Playwright MCP logo

Playwright MCP

Runtime: npxBrowser Automation
Verified

Automates web browsers through Playwright and accessibility snapshots, with MCP tools for navigation, interaction, inspection, and debugging.

Key Features:
Playwright browser automation over MCP
Structured accessibility snapshots
Navigation and multi-tab control
17 0 39,355
Browserctl MCP logo

Browserctl MCP

Runtime: npxBrowser Automation

Controls an existing Chrome, Edge, or Brave session through MCP, with navigation, page reading, form actions, screenshots, and on-demand tools.

Key Features:
Real Chrome, Edge, or Brave profile control
Reference-based page snapshots and element targeting
Navigation, tab management, form actions, and uploads
11 0
Cloakbrowser MCP logo

Cloakbrowser MCP

Runtime: npxBrowser Automation

Automates Chromium through Playwright-compatible MCP tools, with npm and Docker packaging plus stdio and Streamable HTTP transports.

Key Features:
Playwright-compatible browser automation
CloakBrowser Chromium runtime
npm and Docker distribution
5 0 177
MCP Server Playwright logo

MCP Server Playwright

Runtime: npxBrowser Automation

Automates browser navigation, interaction, screenshots, console access, and JavaScript execution through MCP.

Key Features:
URL navigation
CSS selector and text-based interactions
Full-page and element screenshots
4 0 297
Invisible Playwright MCP logo

Invisible Playwright MCP

Runtime: uvxBrowser Automation

Automates real web pages through MCP with browser navigation, interaction, reading, screenshots, profiles, proxies, and two browser identities.

Key Features:
MCP browser automation with Firefox
Persistent profiles and repeatable browser identities
Main and support browser sessions
5 0 877
Jev Browser logo

Jev Browser

Runtime: npxBrowser Automation

jev-browser automates browser tasks with Playwright while Jev selects actions and checks progress through an MCP interface.

Key Features:
Goal-driven browser automation
Playwright-based Chromium control
Focused page reading and snapshots
13 0 130
Browsermcp MCP logo

Browsermcp MCP

Runtime: npxBrowser Automation

Controls a user's Chrome from MCP clients through a local extension, with navigation, interaction, tabs, page reads, and screenshots.

Key Features:
Controls Chrome and Chromium tabs through an extension
Supports navigation, clicks, typing, forms, and keyboard input
Reads page content, metadata, values, and snapshots
6 0 7,318

Frequently Asked Questions: BRYG Alternatives

The top-rated alternatives to BRYG in the Browser Automation category include CDPM, Real Browser MCP, MCP Server Browser. These servers offer complementary or alternative capabilities depending on your deployment stack and authentication requirements.

BRYG and its alternatives vary by runtime requirement (Node.js/npx, Python/uvx, Docker, or remote HTTP/SSE endpoints). Check the specification comparison table above to verify command requirements before installing.

It varies by server. Pricing, auth and license are declared by each maintainer and shown in the comparison table where provided β€” a dash means nothing was declared, so check that project's own site before assuming it's free.

Click the "Compare side-by-side β†’" button on any alternative card to see an in-depth comparison matrix covering feature lists, stars, npm downloads, install configurations, and schema specifications.