Skip to main content
Glama
dreamsxin

browseros-mcp

by dreamsxin
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

browseros-mcp

Standalone browser automation MCP server — supports both BrowserOS and standard Chrome.

Features

  • 16 MCP tools: tabs, tab_groups, navigate, snapshot, diff, act, download, upload, read, grep, screenshot, pdf, wait, windows, evaluate, run

  • Dual backend: Works with both BrowserOS (custom CDP domains) and standard Chrome (Target.* CDP domain)

  • Auto-detection: Probes the connected browser to determine if it's BrowserOS or standard Chrome

  • Accessibility Tree first: Uses AX tree snapshots with [ref=eN] stable handles instead of CSS selectors

  • HTTP+SSE transport: MCP server exposed via HTTP StreamableHTTPTransport (Hono)

  • Auto-reconnect: WebSocket connection with keepalive and automatic reconnection

  • Auto-launch: Optionally start Chrome/BrowserOS automatically

Related MCP server: Chrome Profile MCP Server

Quick Start

# Install dependencies
npm install

# Start Chrome with remote debugging (if not already running)
chrome --remote-debugging-port=9222

# Start the MCP server (auto-detects backend)
npm start -- --cdp-port 9222 --mcp-port 3000

Or with auto-launch:

npm start -- --auto-launch --backend auto

Configuration

CLI Arguments

Argument

Default

Description

--cdp-port

9222

Chrome CDP port

--cdp-host

127.0.0.1

Chrome CDP host

--mcp-port

3000

MCP HTTP server port

--backend

auto

Backend mode: browseros, chrome, or auto

--chrome-path

(auto)

Chrome executable path (for auto-launch)

--auto-launch

false

Automatically start Chrome

--name

browseros-mcp

MCP server name

--version

0.1.0

MCP server version

Environment Variables

All CLI arguments can also be set via environment variables with BROWSEROS_MCP_ prefix:

BROWSEROS_MCP_CDP_PORT=9222
BROWSEROS_MCP_BACKEND=chrome
BROWSEROS_MCP_AUTO_LAUNCH=1

Backend Modes

browseros mode

Uses BrowserOS custom CDP domains:

  • Browser.getTabs, Browser.createTab, Browser.closeTab — tab management

  • Browser.getWindows, Browser.createWindow — window management

  • Browser.getTabGroups, Browser.createTabGroup — tab group management

All 16 tools are fully functional.

chrome mode

Uses standard Chrome CDP domains:

  • Target.getTargets, Target.createTarget, Target.closeTarget — tab management

  • tab_groups and windows tools return "unsupported" errors

  • 14 out of 16 tools are fully functional

auto mode (default)

Probes the connected browser's /json/version response:

  • If Browser field contains "BrowserOS" → browseros mode

  • Otherwise → chrome mode

MCP Tools

Tool

Description

BrowserOS

Chrome

tabs

List, create, close, activate tabs

✅ Full

✅ Adapted

tab_groups

Manage tab groups

✅ Full

❌ Unsupported

navigate

Navigate to URL, back, forward, reload

✅

✅

snapshot

Capture accessibility tree snapshot

✅

✅

diff

Show changes since last snapshot

✅

✅

act

Click, type, fill, press, hover, scroll, drag

✅

✅

download

Download files from clicked links

✅

✅

upload

Upload files to <input type=file>

✅

✅

read

Read page content as markdown/text/links

✅

✅

grep

Search accessibility tree or page content

✅

✅

screenshot

Capture page screenshot

✅

✅

pdf

Save page as PDF

✅

✅

wait

Wait for text, selector, or time

✅

✅

windows

Manage browser windows

✅ Full

❌ Unsupported

evaluate

Evaluate JavaScript on a page

✅

✅

run

Run JavaScript with browser SDK access

✅

✅

Usage with MCP Clients

Cursor / Claude Desktop

Add to your MCP client configuration:

{
  "mcpServers": {
    "browseros-mcp": {
      "url": "http://localhost:3000/mcp"
    }
  }
}

Direct HTTP

# Health check
curl http://localhost:3000/health

# MCP endpoint
POST http://localhost:3000/mcp
Content-Type: application/json

{"jsonrpc": "2.0", "method": "tools/list", "id": 1}

Architecture

┌─────────────────────────────────────────────────────────┐
│                    HTTP+SSE Server                        │
│                  (Hono + @hono/mcp)                      │
│                      /mcp endpoint                        │
├─────────────────────────────────────────────────────────┤
│                  MCP Tool Layer                           │
│            16 tools (framework + registry)               │
│          ToolContext { session, signal }                 │
├─────────────────────────────────────────────────────────┤
│                BrowserSession                             │
│    ┌────────────┬───────────┬──────────┐                │
│    │ PageManager │ Observer  │  Input   │                │
│    │ (dual-mode) │ (AX tree) │ (actions) │                │
│    └──────┬─────┴─────┬─────┴────┬─────┘                │
│           │     Navigation    Screenshot                  │
│           │    FrameRegistry  WindowManager               │
├───────────┴─────────────────────────────────────────────┤
│              CdpConnectionImpl                            │
│    WebSocket → /json/version → ws://devtools/browser     │
│    Proxy-based ProtocolApi (55+ CDP domains)             │
├─────────────────────────────────────────────────────────┤
│         Chrome / BrowserOS (CDP port 9222/9100)          │
└─────────────────────────────────────────────────────────┘

Development

# Install dependencies
npm install

# Run in dev mode (auto-reload)
npm run dev

# Type check
npm run typecheck

# Build
npm run build

License

MIT

This server cannot be installed

F
license - not found
-
quality - not tested
C
maintenance

How are these scores calculated?

Maintenance

–Maintainers
–Response time
–Release cycle
–Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dreamsxin/browseros-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server