Liberty Browser

Liberty Browser is a local Python MCP server and CLI that controls installed Google Chrome through Chrome DevTools Protocol (CDP), using a dedicated persistent profile.

Open-web focus

Liberty Browser supports navigation across HTTP and HTTPS sites without a built-in website allowlist. Websites retain their own sign-in, verification, and access requirements.

Related MCP server: devtools-fleet-mcp

How it works

1. Run liberty-browser login to open installed Google Chrome with a dedicated profile for manual sign-in.

2. Close the Chrome windows using that profile.

3. Call an MCP browser tool. Liberty Browser starts the same Chrome profile with loopback CDP, waits for readiness, verifies the process and profile, and connects.

Playwright provides the CDP connection API. All browser actions use installed Google Chrome. Cookies and signed-in state remain in the local profile outside this repository.

Requirements

• Windows

• Python 3.10 or newer

• Google Chrome installed

Install

py -m venv .venv
.\.venv\Scripts\python.exe -m pip install "git+https://github.com/andrey-barros-dev/liberty-browser.git"
.\.venv\Scripts\Activate.ps1

MCP configuration

{
  "mcpServers": {
    "liberty-browser": {
      "command": "liberty-browser-mcp",
      "args": []
    }
  }
}

Use the absolute path to .venv/Scripts/liberty-browser-mcp.exe when the command is not on PATH. liberty-browser-codex is a compatibility alias for the same persistent Chrome MCP runtime. MCP messages use stdio.

CLI

liberty-browser login
liberty-browser tabs list
liberty-browser navigate https://example.com
liberty-browser inspect
liberty-browser shell

Browser actions automatically launch or reconnect to the dedicated Chrome profile. Closing the MCP connection leaves Chrome running.

Configuration

Development

python -m pip install -e ".[test]"
python -m pytest -q

Tests use temporary Chrome profiles and local fixture pages. See Architecture, Contributing, and Security.

Privacy and security

The persistent profile contains browser session data. Keep it private and outside source control. A connected MCP client can act with that session's permissions. Website verification remains under the website's control.

License

MIT. See LICENSE.