BRYG

What is BRYG?

BRYG implements the Model Context Protocol (MCP) as a plain stdio server, so any compatible client — Claude Code, Claude Desktop, Hermes, Cursor, and others — can control a Chromium browser on your machine. It gives your AI assistant 43 tools covering perception, action, and observation, designed from daily QA work rather than demos.

Note: This repository hosts BRYG's public documentation and issue tracker. The product itself is a single self-contained binary, distributed via the installer below and verified by SHA-256 checksum on download.

Get started

BRYG is a licensed product — you need a key to activate it. It takes about a minute:

1. Get a license key — start your 14-day free trial at bryg.pages.dev and pick how many devices you need ($3 per device/month). Your license key is emailed to you (billing, cancellation, and refunds are handled in the customer portal linked in that email).
2. Install — run the one-line installer for your OS (below).
3. Activate — the guided setup asks for your key during install, or run bryg activate <key> anytime.

Licensing more than one device

Each device gets its own license key, and each key activates one machine. Pick the number of devices at checkout — 3 devices is $9/month. Your own key is issued immediately; for every additional device you enter an email address, and the invitation link sent there issues that device its own key. All of your keys are listed together in the customer portal, and you can add or remove devices at any time with prorated billing.

Install

macOS / Linux

curl -fsSL https://bryg.pages.dev/install.sh | sh

Windows (PowerShell)

irm https://bryg.pages.dev/install.ps1 | iex

The installer downloads the right binary for your OS/architecture to ~/.bryg/bin/ (%USERPROFILE%\.bryg\bin\ on Windows), verifies its SHA-256 checksum, then runs a guided setup that registers BRYG with your MCP client(s), optionally installs OCR support, and activates your license key.

On Linux, BRYG drives Google Chrome (no Edge) and runs it headless automatically when there is no display — servers, SSH sessions. No root to install Chrome? Unpack Chrome for Testing into ~/.bryg/chrome-linux64/. See the Linux notes.

npm / npx — if you'd rather configure your MCP client directly (needs Node.js 18+):

{  "mcpServers": {    "bryg": { "command": "npx", "args": ["-y", "bryg-mcp"] }  }}

bryg-mcp is a launcher: on first run it downloads the BRYG engine for your platform into ~/.bryg/bin, verifies its checksum, and starts it — same engine, same license, same ~/.bryg as the installers above. Activate with npx bryg-mcp activate <key>; every other command works the same way.

Why BRYG

• Sees pages like structure — accessibility-tree snapshots with stable element refs ([ref=N]); compact and reliable for AI to act on, with coordinate fallback.
• OCR & QR built in — reads text from canvas, images, and games (multi-strategy OCR, any tesseract language) and decodes QR codes on the page.
• Network capture — record everything, keyword-filtered, or failures-only. Sensitive headers and password/token-like fields are masked by default.
• Credentials stay local — secrets never enter AI conversations.
• Headful by design — a dedicated browser instance you can watch and take over at any time (on display-less Linux it runs headless automatically).
• Zero telemetry — runs entirely on your machine; the only network calls are license validation and an anonymous update check.

Tools (43)

Perception — browser_snapshot · browser_read · browser_screenshot · browser_ocr · browser_qr Action — navigate · click · type · fill · scroll · press keys · drag · upload · select, and more Observation — network_start · network_stop · network_status

See the full tool reference.

CLI

Registering with an MCP client

bryg setup registers BRYG with Claude Code and Claude Desktop for you. For any other client, point it at the binary as a stdio server. Hermes, for example, takes a few lines in ~/.hermes/config.yaml followed by /reload-mcp:

mcp_servers:  bryg:    command: "${userHome}/.bryg/bin/bryg"    args: []    enabled: true

Documentation

Full documentation — installation, CLI, configuration, all 43 tools, licensing FAQ, and changelog — lives at bryg.pages.dev/docs.

Support

• 🐛 Found a bug or have a feature request? Open an issue.
• 💬 Questions? See the FAQ or reach out via the site.

License

BRYG is commercial software provided under its End User License Agreement. This repository's documentation content is © BRYG. The BRYG binary is not open source.