Browser Gateway

AI browser tools with Chrome CDP. Navigate, screenshot, interact. Multi-provider failover.

Get it
LLM Mart 4 views 12 listing impressions
Transport
Not stated
Package
—
Registry id
io.github.browser-gateway/browser-gateway

No install snippet on purpose. A working MCP config is a command, its arguments and an environment block — the last two are where API keys live, so this catalogue never stores them and cannot publish them. Follow the link above for the authors' own instructions.

One endpoint that routes across every browser provider you use: automatic failover, persistent profiles, session replay, REST API, MCP server, dashboard.
Works unchanged with Puppeteer, Playwright, Stagehand, browser-use, and any MCP client.

npm version npm downloads MIT license Node.js GitHub stars

Deploy on Railway   Deploy to Render   Deploy to DigitalOcean   Deploy to Koyeb

Website  ·  Quick start  ·  MCP  ·  Profiles  ·  Replays  ·  REST API  ·  Dashboard  ·  Discord

browser-gateway routes traffic across multiple browser providers, filling them by priority and failing over when one is saturated

Overview

One endpoint. Multiple providers. Automatic failover when one is saturated or goes down.

Your app connects to ws://gateway:9500/v1/connect. The gateway picks the best available provider based on health, capacity, and your routing strategy. Providers can be cloud CDP services, Docker containers, or local Chrome instances.

Dashboard

A web dashboard ships with every install. Open http://localhost:9500/web after starting the gateway.

Overview. Active sessions, queue depth, provider health, connection endpoint, and a copy-paste quickstart for Puppeteer, Playwright, Stagehand, browser-use, and raw CDP.

Dashboard overview page showing active sessions, queue depth, provider health, masked connection endpoint, and a tabbed quickstart with Puppeteer code

From the project's README.