Add the Browser Control MCP server in TypeScript

.gitattributes

@@ -0,0 +1,2 @@
+data/public_suffix_list.dat -text
+native/clipboard-guard/clipboard_guard.swift -text

.github/workflows/check.yml

@@ -16,7 +16,26 @@ jobs:
           version: 10.33.2
       - uses: actions/setup-node@v4
         with:
-          node-version: 22
+          node-version: 24
           cache: pnpm
       - run: pnpm install --frozen-lockfile
       - run: pnpm run check
+
+  browser:
+    runs-on: macos-14
+    steps:
+      - uses: actions/checkout@v4
+      - uses: pnpm/action-setup@v4
+        with:
+          version: 10.33.2
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 24
+          cache: pnpm
+      - run: pnpm install --frozen-lockfile
+      - run: pnpm exec playwright-core install chromium
+      - run: pnpm run build
+      - name: Verify disposable Chrome and native messaging
+        run: |
+          export BROWSER_CONTROL_SYNTHETIC_CHROME="$(node -p 'require("playwright-core").chromium.executablePath()')"
+          pnpm exec vitest run tests/security/private-input.browser.test.ts tests/server/packaging/live-browser.test.ts

.github/workflows/chrome-web-store.yml

@@ -43,7 +43,7 @@ jobs:
       - uses: actions/setup-node@v4
         if: ${{ inputs.action == 'upload' || inputs.action == 'submit' }}
         with:
-          node-version: 22
+          node-version: 24
           cache: pnpm
 
       - if: ${{ inputs.action == 'upload' || inputs.action == 'submit' }}

.github/workflows/release.yml

@@ -19,7 +19,7 @@ jobs:
           version: 10.33.2
       - uses: actions/setup-node@v4
         with:
-          node-version: 22
+          node-version: 24
           cache: pnpm
       - run: pnpm install --frozen-lockfile
       - run: pnpm run check

README.md

@@ -1,65 +1,69 @@
 # Browser Control
 
-Browser Control is a Chrome extension and native messaging host that let an AI agent on your own computer work in your browser tabs. The extension does nothing until you install the local host.
+Browser Control connects an AI agent to Chrome through an MCP server, a Chrome extension, and a native messaging host. It provides observed page actions, tab ownership, screenshots, and isolated Chrome for Testing leases.
 
-- Homepage: <https://browser-control.pages.dev/>
-- Privacy policy: <https://browser-control.pages.dev/privacy/>
-- Support: <https://browser-control.pages.dev/support/>
+## Install
 
-## Identifiers
+The npm package requires Node.js 24 or later on macOS or Linux. Isolated browser leases and private 1Password transfer require macOS and a separately installed cua-driver.
 
-| What | Value |
-| --- | --- |
-| Chrome Web Store item ID | `dcnjjnecbhipdbngkhjppkckpkellmld` |
-| Native messaging host name | `com.opzero.chrome` |
-| Host and page protocol | version 2 |
-| Unpacked extension ID | Derived by Chrome from the absolute path of the loaded folder. The manifest has no `key` field. |
+1. Install the extension from the [Chrome Web Store](https://chromewebstore.google.com/detail/dcnjjnecbhipdbngkhjppkckpkellmld).
+2. Install the native host:
+
+   ```sh
+   npx -y @op1/browser-control install
+   ```
 
-Chrome derives an unpacked extension's ID from its folder path, so every checkout or install location has its own ID. For example, the fast-chrome controller loads `~/.config/opencode/mcp/fast-chrome/op-chrome/dist/extension`, which gives the ID `pncpgnbanebkeopjghjleodgmphmmmcp`. The native host manifest must allow the ID of the extension that connects to it.
+3. Open the extension popup and click **Reload host**.
+4. Print the configuration for your MCP client:
 
-## Install for users
+   ```sh
+   npx -y @op1/browser-control config claude
+   ```
 
-1. Install Browser Control from the [Chrome Web Store](https://chromewebstore.google.com/detail/dcnjjnecbhipdbngkhjppkckpkellmld).
-2. Install the native host. It needs Node.js 18 or later on macOS or Linux:
+   Replace `claude` with `opencode`, `codex`, or `cursor` for another client. Add the printed configuration to that client.
+5. Check the installation:
 
    ```sh
-   mkdir -p ~/.config/opencode/skills/browser-control
-   curl -fsSL https://github.com/opzero1/browser-control/releases/latest/download/browser-control-skill.zip -o /tmp/browser-control-skill.zip
-   unzip -o /tmp/browser-control-skill.zip -d ~/.config/opencode/skills/browser-control
-   cd ~/.config/opencode/skills/browser-control
-   node scripts/install-native-host.js --extension-id dcnjjnecbhipdbngkhjppkckpkellmld
+   npx -y @op1/browser-control doctor
    ```
 
-3. Open the Browser Control popup and click **Reload host**. It shows **Connected**.
+The server command is `npx -y @op1/browser-control mcp`. Installation stores stable copies under `~/.local/state/browser-control`. Set `BROWSER_CONTROL_STATE_DIR` to use another directory. To install the three bundled skills, pass `--skills-dir <your-client-skills-directory>` to `install`; no skills directory is chosen automatically.
 
-The popup also has **Pause host**, which disconnects the host and ends every agent session until you click **Resume host**. The pause setting survives browser restarts. If the host exits, the extension reconnects automatically within about 30 seconds.
+See [installation and troubleshooting](docs/server/INSTALL.md) for flags, optional tools, and the isolated smoke check. The generated native-host wrapper uses the Node executable that ran `install`. Rerun `install` after removing or replacing that Node installation.
 
-To install the agent skill with one command instead:
+## Use
 
-```sh
-curl -fsSL https://raw.githubusercontent.com/opzero1/browser-control/main/scripts/install-browser-control-skill.sh | sh
-```
+Load the [browser-control skill](skills/browser-control/SKILL.md) in your agent. Start with `status` and `tabs`, then claim a tab or open one. Use `act_steps` to batch actions selected from observed controls. Release tabs before releasing a browser lease.
 
-## Verify
+The popup's **Pause host** disconnects the host and ends its agent sessions until **Resume host** is selected. The pause setting survives browser restarts. If the host exits, the extension retries within about 30 seconds.
 
-```sh
-node native-host/client.js ping
-node native-host/client.js getInfo
-```
+The [bundled native host scripts](skills/browser-control/references/native-host.md) also support the standalone release-zip installation. Use one installer per Chrome profile because both installers write the same native-messaging manifest.
 
-`ping` returns `pong` from the extension. `getInfo` reports `protocolVersion: 2`.
+## Identifiers
 
-## Development
+| Component | Value |
+| --- | --- |
+| npm package and CLI | `@op1/browser-control`, `browser-control` |
+| Chrome Web Store extension | `dcnjjnecbhipdbngkhjppkckpkellmld` |
+| Isolated-profile extension | `mpodnojmjjafgogldgieimgbmfhhknbe` |
+| Native messaging host | `com.opzero.chrome` |
+| Host and page protocols | Version 2 |
+
+The isolated copy has a public key that fixes its extension ID across paths and upgrades. The Web Store build has no injected key. A manually loaded unpacked build without a key gets an ID derived from its absolute path.
 
-See [docs/DEVELOPER.md](docs/DEVELOPER.md) to load an unpacked build and connect a local host.
+## Develop
 
 ```sh
 pnpm install
 pnpm run check
 ```
 
-`pnpm run check` builds the extension, native host and installable skill, then runs type checks, tests and the project checks. The headless-browser tests for private input run only when `BROWSER_CONTROL_SYNTHETIC_CHROME` names a Chrome for Testing binary.
+`check` builds the extension, native host, MCP server, and skill, then runs type checks, tests, project checks, and Python parity mapping checks. To include disposable headless-browser tests, set `BROWSER_CONTROL_SYNTHETIC_CHROME` to a Chrome for Testing executable.
+
+Repository guides: [development](https://github.com/opzero1/browser-control/blob/main/docs/DEVELOPER.md) and [release](https://github.com/opzero1/browser-control/blob/main/docs/RELEASE.md).
 
-## Release
+## Support and privacy
 
-See [docs/RELEASE.md](docs/RELEASE.md). The store listing text is in [store/listing.md](store/listing.md), the store images are in [store/assets](store/assets), and the website is in [site](site).
+- [Homepage](https://browser-control.pages.dev/)
+- [Privacy policy](docs/PRIVACY.md)
+- [Support](https://browser-control.pages.dev/support/)

data/README.md

@@ -0,0 +1,19 @@
+# Vendored data
+
+`public_suffix_list.dat` is the Public Suffix List, including ICANN and private rules, used to map hosts to
+cookie sites (`src/server/sites.ts`).
+
+- Source: https://publicsuffix.org/list/public_suffix_list.dat
+- Fetched: 2026-09-26 (2026-09-25T17:23Z)
+- `// VERSION: 2026-09-24_13-26-36_UTC`
+- `// COMMIT: a179a48c465e818cfd8d626691cb317985da87fb`
+- Size: 334,786 bytes
+- SHA-256: `257b298daca42f6d8ec964e238c2a55518e14f09d3117917ec8acee6f188503e`
+
+The server refuses a file with any other hash (`fast-chrome-public-suffix-list-mismatch`). To update it,
+replace the file, update `PSL_SHA256` in `src/server/sites.ts`, this README and the check in
+`scripts/check-project.js`, and rerun the site tests. The list is published under the Mozilla Public
+License 2.0.
+
+`../native/clipboard-guard/clipboard_guard.swift` is copied verbatim from the reference fast-chrome server.
+`browser-control install` builds it into `<state>/bin/clipboard-guard-<sha12>`.