Managed edition

Use Browser MCP without running your own server.

Use browser-mcp.click to connect your browser without running a server. Sign in with GitHub to manage browsers and MCP client tokens. The service is a preview without an uptime SLA.

Pair a browser

Install the native CLI, then run:

browser-mcp browser start --server https://browser-mcp.click --profile work

Open its approval URL, verify the hostname and browser name, sign in with GitHub, and explicitly approve. Requests expire after ten minutes. A separate runtime credential is delivered only to the proof-holding CLI. Create an expiring MCP token in the dashboard for your trusted client; never substitute one credential type for another.

GitHub login authenticates dashboard access, not a read-only browser scope. Paired clients can control signed-in pages broadly. Pause or stop locally and revoke unused tokens. See security.

Privacy and support

Use a dedicated profile containing only the accounts needed for your tasks. Browser content, files, and live-view pixels requested by your clients pass through the service; TLS does not hide them from the service operator. See privacy for data handling and your controls.

For help, contact [e-mail]. If you prefer to manage your own server and identity provider, use the community edition.