mcp-browser-extension 0.9.25 → 0.9.27

package/README.md

@@ -1,14 +1,12 @@
 # MCP Browser Extension
 
-The unscoped distribution of `@mehmoodqureshi/chrome-mcp`, with the same implementation and version. Both package names remain supported.
-
 [![CI](https://github.com/Mehmoodqureshi/mcp-browser-extension/actions/workflows/ci.yml/badge.svg)](https://github.com/Mehmoodqureshi/mcp-browser-extension/actions/workflows/ci.yml)
 [![npm](https://img.shields.io/npm/v/mcp-browser-extension?label=npm)](https://www.npmjs.com/package/mcp-browser-extension)
 [![license](https://img.shields.io/npm/l/mcp-browser-extension?label=license)](LICENSE)
 
 **Website and docs:** [mcp-browser-extension.com](https://mcp-browser-extension.com) ·
 [Quickstart](https://mcp-browser-extension.com/docs/quickstart) ·
-[All 40 tools](https://mcp-browser-extension.com/docs/tools) ·
+[All 42 tools](https://mcp-browser-extension.com/docs/tools) ·
 [Install the extension from the Chrome Web Store](https://chromewebstore.google.com/detail/mcp-browser-extension/jelfhdlkhbfmlpbghoeaepijllcnplgh)
 
 **Let Claude use the Chrome you are already logged into.** Not a fresh
@@ -24,8 +22,7 @@ localhost WebSocket server and drives the browser you already have open, through
 other MCP host.
 
 MCP Browser Extension has two parts: the extension, and a small MCP server you run
-with `npx` (npm package `mcp-browser-extension`, command `chrome-mcp`; the
-names predate the rename and stay so existing setups keep working). The extension
+with `npx` (npm package and command: `mcp-browser-extension`). The extension
 comes from the
 [Chrome Web Store](https://chromewebstore.google.com/detail/mcp-browser-extension/jelfhdlkhbfmlpbghoeaepijllcnplgh)
 or loaded unpacked.
@@ -103,7 +100,7 @@ is the exact file the agent follows. The manual steps are below.
 <summary><b>Claude Code (terminal)</b> — one command, no config file to find</summary>
 
 ```bash
-claude mcp add chrome-mcp -s user -- \
+claude mcp add mcp-browser-extension -s user -- \
   npx -y mcp-browser-extension@latest \
   --allow-domain example.com --enable-mutations --persist-token
 ```
@@ -127,7 +124,7 @@ with `/mcp` inside a session — no restart needed.
 ```jsonc
 {
   "mcpServers": {
-    "chrome-mcp": {
+    "mcp-browser-extension": {
       "command": "npx",
       "args": ["-y", "mcp-browser-extension@latest",
                "--allow-domain", "example.com", "--enable-mutations",
@@ -155,8 +152,8 @@ stricter default described next.
 
 Without `--persist-token` a fresh token is minted every boot (the secure
 default), which means re-pairing the extension on each restart. With it, the
-token is stored 0600 at `~/.chrome-mcp/token` and reused; the extension's
-keepalive auto-reconnects with no manual step. `CHROME_MCP_TOKEN` pins the token
+token is stored 0600 at `~/.mcp-browser-extension/token` and reused; the extension's
+keepalive auto-reconnects with no manual step. `MCP_BROWSER_EXTENSION_TOKEN` pins the token
 explicitly (and is never written to disk).
 
 **2. Install the extension** — **required**; the server can drive nothing without it.
@@ -177,8 +174,8 @@ or paste.
 <summary>Developers: load it unpacked instead</summary>
 
 The extension also ships inside the npm package, and every time the server boots
-it copies it to `~/chrome-mcp-extension` (`%USERPROFILE%\chrome-mcp-extension` on
-Windows; `CHROME_MCP_EXTENSION_DIR` moves it). `chrome://extensions` → enable
+it copies it to `~/mcp-browser-extension` (`%USERPROFILE%\mcp-browser-extension` on
+Windows; `MCP_BROWSER_EXTENSION_EXTENSION_DIR` moves it). `chrome://extensions` → enable
 **Developer mode** → **Load unpacked** → pick that folder. It pairs itself from a
 `pairing.json` the server writes there, and the server refreshes the files on each
 boot (never with an older build) so it reloads itself within 30 seconds.
@@ -211,7 +208,7 @@ stays in the toolbar. Hover it for the status in words.
 Manual fallback (the helper is turned off with `--no-native-host`, or Connect
 reports a problem): run `npx -y mcp-browser-extension@latest --print-pairing`,
 open the extension's **Settings**, and paste the `port` + `token` from
-`~/.chrome-mcp/handshake.json`.
+`~/.mcp-browser-extension/handshake.json`.
 
 ### Extension missing after restarting Chrome
 
@@ -234,7 +231,7 @@ npx -y mcp-browser-extension@latest extension repair --apply
 ```
 
 The repair backs up the original preferences under
-`~/.chrome-mcp/extension-repair-backups/`, removes only the confirmed obsolete
+`~/.mcp-browser-extension/extension-repair-backups/`, removes only the confirmed obsolete
 registration, and preserves the current extension and its saved settings. It
 refuses to write while a Chromium browser is running. Reopen Chrome afterwards.
 Use `--user-data-dir <directory>` for a custom browser data location, or
@@ -280,7 +277,7 @@ at startup or the `profile_use` tool at runtime.
 Naming is automatic. Chrome won't tell an extension which profile it runs in, so
 each install keeps a random id and the server names it: the first browser is
 `default`, the next `profile-2`, then `profile-3`, and so on. Names are stored in
-`~/.chrome-mcp/profiles.json`, so a browser keeps its name across restarts.
+`~/.mcp-browser-extension/profiles.json`, so a browser keeps its name across restarts.
 `chrome_status` lists every paired browser (with its active tab as a hint), and
 `profile_rename` gives one a friendly name (`profile-2` → `work`). To pin a name
 yourself instead, type it into the extension's Options → Profile; that always wins.
@@ -299,7 +296,7 @@ start. Wrap it in `cmd /c`:
 ```jsonc
 {
   "mcpServers": {
-    "chrome-mcp": {
+    "mcp-browser-extension": {
       "command": "cmd",
       "args": ["/c", "npx", "-y", "mcp-browser-extension@latest",
                "--allow-domain", "example.com", "--enable-mutations",
@@ -309,14 +306,14 @@ start. Wrap it in `cmd /c`:
 }
 ```
 
-Or from Claude Code: `claude mcp add chrome-mcp -- cmd /c npx -y mcp-browser-extension@latest --allow-domain example.com`
+Or from Claude Code: `claude mcp add mcp-browser-extension -- cmd /c npx -y mcp-browser-extension@latest --allow-domain example.com`
 
 For normal use, install the extension from the Chrome Web Store as described
 above, then click **Connect**. Do not use **Load unpacked** as part of the normal
 Windows setup. The unpacked developer build has the same extension ID as the
 Store build, so loading it can replace the Store installation; Chrome may then
-disable the non-Store copy. If you are developing chrome-mcp, load
-`%USERPROFILE%\chrome-mcp-extension` in a separate Chrome profile.
+disable the non-Store copy. If you are developing mcp-browser-extension, load
+`%USERPROFILE%\mcp-browser-extension` in a separate Chrome profile.
 
 The tools cover tabs, navigation, interaction (`click`/`type`/`press`/`hover`/
 `scroll`/`select_option`), reads (`get_text`/`get_html`/`screenshot`/`eval`/`wait_for`),
@@ -349,7 +346,7 @@ It prints a connector URL like `https://<random>.trycloudflare.com/mcp/<key>`:
 - **Claude Code elsewhere / agents:** use `<url>/mcp` with `Authorization: Bearer <key>`;
   the exact `claude mcp add` line is printed too.
 
-The key (32 random bytes, kept in `~/.chrome-mcp/remote-key`) guards every
+The key (32 random bytes, kept in `~/.mcp-browser-extension/remote-key`) guards every
 request; a wrong or missing key gets a bare 404. Anyone holding the URL can drive
 your browser within the allowed sites, so keep it private and keep the allowlist
 tight. `--rotate-remote-key` cuts every client off. The quick-tunnel URL changes on
@@ -557,7 +554,7 @@ for a run that was never going to print a PDF or upload a file.
   `--unsafe-enable-eval`.
 - An unknown name fails at startup and prints the catalog, so a typo can never
   quietly drop `click` from the surface.
-- `chrome-mcp --help` prints the full catalog of 40 names to pick from.
+- `mcp-browser-extension --help` prints the full catalog of 42 names to pick from.
 
 ## Status
 
@@ -569,7 +566,7 @@ full-page and element capture), and focuses newly opened tabs by default. 111
 automated tests + a gated headed extension smoke.
 
 v0.2.0 — all six build phases complete and green. End-to-end working:
-`npx chrome-mcp` ⇄ bridge ⇄ extension ⇄ your real Chrome, with a Playwright CDP
+`npx mcp-browser-extension` ⇄ bridge ⇄ extension ⇄ your real Chrome, with a Playwright CDP
 fallback. v0.2 adds the accessibility `snapshot` + element refs, auto-wait,
 cookies/storage/`select_option`, trusted input (`chrome.debugger`), a toolbar
 status badge, and a stable pairing token (`--persist-token`).
@@ -616,11 +613,11 @@ status badge, and a stable pairing token (`--persist-token`).
 `eval` off, downloads off, mutating tools off. Opt in explicitly:
 
 ```
-chrome-mcp --allow-domain example.com --enable-mutations
-chrome-mcp --policy ./policy.json          # see policy.example.json
-chrome-mcp --unsafe-all-domains            # loud footgun
-chrome-mcp --enable-observers              # console/network/dialog capture (patches page globals)
-chrome-mcp --redact                        # scrub secret-shaped strings out of page reads
+mcp-browser-extension --allow-domain example.com --enable-mutations
+mcp-browser-extension --policy ./policy.json          # see policy.example.json
+mcp-browser-extension --unsafe-all-domains            # loud footgun
+mcp-browser-extension --enable-observers              # console/network/dialog capture (patches page globals)
+mcp-browser-extension --redact                        # scrub secret-shaped strings out of page reads
 ```
 
 **Allowing a site without a restart.** When a call is refused because its site
@@ -628,7 +625,7 @@ is not allowed, the extension's toolbar icon shows a `?`. Click it: the popup
 lists the blocked site with an **Allow** button, shows whether the site you are on
 is allowed (with its own Allow), and lists the allowed sites. The Options page
 (Settings in the popup) also has a box to allow any other site. An allowed site applies at once to every session sharing that Chrome, and
-is saved to `~/.chrome-mcp/allowed-sites.json` so it survives restarts. Sites
+is saved to `~/.mcp-browser-extension/allowed-sites.json` so it survives restarts. Sites
 allowed there can be removed there; sites from `--allow-domain` stay until the
 flags change. The catch-all `*` can only come from `--unsafe-all-domains`. The
 agent cannot approve a site itself: MCP Browser Extension never reads or drives the
@@ -656,12 +653,12 @@ policy verdict (`allowed`/`denied`), how long it took, how many bytes came back,
 and how many secrets were scrubbed — so "what did the agent do in my browser" has
 an answer after the fact.
 
-The per-boot 256-bit token in `~/.chrome-mcp/handshake.json` (mode 0600) is the
+The per-boot 256-bit token in `~/.mcp-browser-extension/handshake.json` (mode 0600) is the
 only trust boundary; it is never written to stdout/stderr. On POSIX the mode is
 re-verified after every write and the server **fails closed** if the file ends up
 group/other-accessible. Windows has no such bits — `chmod` there only toggles the
 read-only attribute — so the check is skipped and the token's confidentiality
-rests on the per-user ACL of `%USERPROFILE%\.chrome-mcp`.
+rests on the per-user ACL of `%USERPROFILE%\.mcp-browser-extension`.
 
 ## Updates
 
@@ -671,9 +668,9 @@ npm when it starts: if a newer version is published, it starts that version in
 its place, with the same arguments, so an MCP config written months ago still
 runs the newest release. The check gives up after 1.5 s when you are offline,
 and a copy run from a git checkout never updates itself. The new server also
-refreshes the unpacked extension in `~/chrome-mcp-extension`, which reloads
+refreshes the unpacked extension in `~/mcp-browser-extension`, which reloads
 itself; the Chrome Web Store copy updates through Chrome as usual. Turn it off
-with `--no-auto-update` or `CHROME_MCP_AUTO_UPDATE=0`.
+with `--no-auto-update` or `MCP_BROWSER_EXTENSION_AUTO_UPDATE=0`.
 
 ## Telemetry
 
@@ -681,7 +678,7 @@ The MCP Browser Extension **server** (not the extension) sends anonymous usage s
 project can see how many installs are active, which versions and platforms are
 in use, and which tools fail most. A notice is printed the first time it runs.
 
-What is sent: a random install id (kept in `~/.chrome-mcp/telemetry.json`), the
+What is sent: a random install id (kept in `~/.mcp-browser-extension/telemetry.json`), the
 server version, OS, CPU architecture and Node major version, whether the
 session owns the bridge port or shares it, how many browsers are paired, the
 paired extension's version and whether it is the store or an unpacked copy, and
@@ -709,7 +706,7 @@ The **browser extension sends nothing** — it only ever talks to `127.0.0.1`.
 Turn it off with any of:
 
 ```bash
-CHROME_MCP_TELEMETRY=0     # or false / off
+MCP_BROWSER_EXTENSION_TELEMETRY=0     # or false / off
 DO_NOT_TRACK=1
 --no-telemetry             # server flag
 ```
@@ -749,11 +746,11 @@ for local development; do not load this unpacked copy in the same Chrome profile
 as the Store extension. On Windows, Chrome may disable a non-Store build.
 
 `extension/` builds (esbuild) to `extension-dist/`, loaded via
-`chrome://extensions` → **Load unpacked** → select `~/chrome-mcp-extension`, the
+`chrome://extensions` → **Load unpacked** → select `~/mcp-browser-extension`, the
 mirror the server refreshes from `extension-dist/` on every boot (loading
 `extension-dist/` directly also works). It pairs itself from the `pairing.json`
 the server writes into that folder; the **Options** page paste of `port` +
-`token` from `~/.chrome-mcp/handshake.json` (run
+`token` from `~/.mcp-browser-extension/handshake.json` (run
 `npx -y mcp-browser-extension@latest --print-pairing` to get the path) is only
 the fallback.
 

package/SETUP.md

@@ -4,7 +4,7 @@
 machine and prove it works.** MCP Browser Extension lets an MCP client drive the human's
 real Chrome browser: real logins, real cookies, no separate Chromium. It has two
 halves that must be paired: a stdio MCP server (npm package
-`@mehmoodqureshi/chrome-mcp`) and a Manifest V3 extension that ships inside the
+`mcp-browser-extension`) and a Manifest V3 extension that ships inside the
 same package. Work autonomously; pause only for the two actions that must happen
 inside Chrome's own UI (loading the extension, pasting the pairing token).
 
@@ -40,10 +40,10 @@ extension to a plain folder directly under the home directory, and prints its
 path:
 
 ```
-npx -y @mehmoodqureshi/chrome-mcp@latest --extension-path
+npx -y mcp-browser-extension@latest --extension-path
 ```
 
-It prints `~/chrome-mcp-extension` (on Windows `%USERPROFILE%\chrome-mcp-extension`).
+It prints `~/mcp-browser-extension` (on Windows `%USERPROFILE%\mcp-browser-extension`).
 Verify with `ls` (or `dir`) that the folder holds `manifest.json` and
 `background.js`. Record the path; the human needs it in step 4. The install is
 small and downloads no browser: the server drives the Chrome the human already
@@ -62,14 +62,14 @@ unless they ask.
 **Claude Code** (registers for every project on this machine):
 
 ```
-claude mcp add chrome-mcp -s user -- \
-  npx -y @mehmoodqureshi/chrome-mcp@latest \
+claude mcp add mcp-browser-extension -s user -- \
+  npx -y mcp-browser-extension@latest \
   --allow-domain example.com --enable-mutations --persist-token
 ```
 
 Everything before `--` belongs to Claude Code. Everything after it is the
 server's own command line. Keep the `--` or `--allow-domain` gets read as a
-Claude Code option. Verify with `claude mcp list`: chrome-mcp should be listed.
+Claude Code option. Verify with `claude mcp list`: mcp-browser-extension should be listed.
 It will show as connected once the server boots, even before the extension has
 paired.
 
@@ -80,9 +80,9 @@ Code uses a top-level `servers` key instead of `mcpServers`).
 ```json
 {
   "mcpServers": {
-    "chrome-mcp": {
+    "mcp-browser-extension": {
       "command": "npx",
-      "args": ["-y", "@mehmoodqureshi/chrome-mcp@latest",
+      "args": ["-y", "mcp-browser-extension@latest",
                "--allow-domain", "example.com",
                "--enable-mutations",
                "--persist-token"]
@@ -92,13 +92,13 @@ Code uses a top-level `servers` key instead of `mcpServers`).
 ```
 
 **Windows:** the command must be `cmd` with args `["/c", "npx", "-y",
-"@mehmoodqureshi/chrome-mcp@latest", ...]`, or for Claude Code:
-`claude mcp add chrome-mcp -s user -- cmd /c npx -y @mehmoodqureshi/chrome-mcp@latest --allow-domain example.com --enable-mutations --persist-token`.
+"mcp-browser-extension@latest", ...]`, or for Claude Code:
+`claude mcp add mcp-browser-extension -s user -- cmd /c npx -y mcp-browser-extension@latest --allow-domain example.com --enable-mutations --persist-token`.
 
 Tell the human to restart the client (or run `/mcp` in Claude Code) so the
-server loads. The first boot writes `~/.chrome-mcp/handshake.json` (mode 0600)
+server loads. The first boot writes `~/.mcp-browser-extension/handshake.json` (mode 0600)
 holding the bridge port and the pairing token, and with `--persist-token` it
-also stores the token at `~/.chrome-mcp/token` for reuse.
+also stores the token at `~/.mcp-browser-extension/token` for reuse.
 
 ## Step 4 — Load the extension (human action inside Chrome)
 
@@ -106,7 +106,7 @@ You cannot do this step yourself. Give the human these exact instructions:
 
 1. Open `chrome://extensions` in Chrome.
 2. Turn on **Developer mode** (top right).
-3. Click **Load unpacked** and choose the `chrome-mcp-extension` folder in
+3. Click **Load unpacked** and choose the `mcp-browser-extension` folder in
    their home directory (the path from step 2).
 4. Confirm an extension named **MCP Browser Extension** now appears in the list.
 
@@ -149,7 +149,7 @@ retry the tool.
 ## Step 6 — Check the pairing
 
 Pairing needs no paste. Every time the server boots it writes `pairing.json`
-(mode 0600) into the same `chrome-mcp-extension` folder the human loaded in step 4.
+(mode 0600) into the same `mcp-browser-extension` folder the human loaded in step 4.
 The extension reads that file from its own folder and pairs itself. So make
 sure a server has booted at least once since step 2, in either of these ways:
 
@@ -157,13 +157,13 @@ sure a server has booted at least once since step 2, in either of these ways:
 - start one yourself in pairing mode and leave it running in the background:
 
   ```
-  npx -y @mehmoodqureshi/chrome-mcp@latest --print-pairing --persist-token
+  npx -y mcp-browser-extension@latest --print-pairing --persist-token
   ```
 
 Verify the file exists (do not print it):
 
 ```
-ls "$(npx -y @mehmoodqureshi/chrome-mcp@latest --extension-path)/pairing.json"
+ls "$(npx -y mcp-browser-extension@latest --extension-path)/pairing.json"
 ```
 
 Then tell the human where to look. The status badge is on the extension's
@@ -190,11 +190,11 @@ extension folder or a read-only global install): read the port without
 printing the token,
 
 ```
-node -e "console.log(require(require('os').homedir()+'/.chrome-mcp/handshake.json').port)"
+node -e "console.log(require(require('os').homedir()+'/.mcp-browser-extension/handshake.json').port)"
 ```
 
 then have the human open **Details** on MCP Browser Extension, then **Extension
-options**, enter that **Port**, open `~/.chrome-mcp/handshake.json` in a text
+options**, enter that **Port**, open `~/.mcp-browser-extension/handshake.json` in a text
 editor and paste its `token` into the **Token** field, leave **Profile** as
 `default`, and click **Save**. The status line should read **connected** within
 a few seconds. Values saved by hand take precedence over the bundled file.
@@ -225,7 +225,7 @@ not stick. Re-check the port and token before anything else.
 Summarize for the human:
 
 - Node and package versions installed.
-- The absolute `chrome-mcp-extension` path they loaded.
+- The absolute `mcp-browser-extension` path they loaded.
 - Which MCP client was configured, at which scope, with which domains and gates.
 - Whether the badge went green, and whether `tabs_list`, an allowed
   navigation, and a refused navigation each verified.
@@ -233,4 +233,4 @@ Summarize for the human:
 
 For any failure, name the exact symptom, what you tried, and the matching
 section of the README's troubleshooting notes at
-`https://github.com/Mehmoodqureshi/chrome-mcp#readme`.
+`https://github.com/Mehmoodqureshi/mcp-browser-extension#readme`.

package/dist/shared/protocol.d.ts

@@ -268,7 +268,7 @@ export type ServerFrame = CommandFrame | WelcomeFrame | UnauthFrame | PingFrame
 /** Frames the EXTENSION sends to the server. */
 export type ExtensionFrame = HelloFrame | ResultFrame | ErrorFrame | EventFrame | PongFrame | SiteGrantFrame;
 export type Frame = ServerFrame | ExtensionFrame;
-/** Shape of `$CHROME_MCP_DATA/handshake.json`. The token is a secret. */
+/** Shape of `$MCP_BROWSER_EXTENSION_DATA/handshake.json`. The token is a secret. */
 export interface HandshakeFile {
     v: ProtocolVersion;
     port: number;

package/dist/shared/tab-border.d.ts

@@ -1,5 +1,5 @@
 /**
- * shared/tab-border.ts — the pure half of the "chrome-mcp is working here"
+ * shared/tab-border.ts — the pure half of the "mcp-browser-extension is working here"
  * border: choosing its colour from the page's theme and writing the CSS.
  *
  * The extension paints the border with `chrome.scripting.insertCSS` on

package/dist/shared/tab-border.js

@@ -1,6 +1,6 @@
 "use strict";
 /**
- * shared/tab-border.ts — the pure half of the "chrome-mcp is working here"
+ * shared/tab-border.ts — the pure half of the "mcp-browser-extension is working here"
  * border: choosing its colour from the page's theme and writing the CSS.
  *
  * The extension paints the border with `chrome.scripting.insertCSS` on

package/dist/src/access.js

@@ -6,7 +6,8 @@ exports.requireAccess = requireAccess;
 const node_crypto_1 = require("node:crypto");
 const node_fs_1 = require("node:fs");
 const node_path_1 = require("node:path");
-const SITE = (process.env.CHROME_MCP_ACCESS_API ?? 'https://mcp-browser-extension.com/api/access').replace(/\/$/, '');
+const compat_1 = require("./compat");
+const SITE = ((0, compat_1.runtimeEnv)('ACCESS_API') ?? 'https://mcp-browser-extension.com/api/access').replace(/\/$/, '');
 let accessPollMs = 2_000;
 let accessWaitMs = 45_000;
 const EMAIL_SCHEMA = {

package/dist/src/auto-update.d.ts

@@ -1,7 +1,7 @@
 /**
- * src/auto-update.ts — keep every install on the latest chrome-mcp.
+ * src/auto-update.ts — keep every install on the latest mcp-browser-extension.
  *
- * Most people run chrome-mcp through `npx -y @mehmoodqureshi/chrome-mcp` in an
+ * Most people run mcp-browser-extension through `npx -y mcp-browser-extension` in an
  * MCP config. npx reuses whatever copy it cached first, so installs sat on old
  * versions for weeks (telemetry: three times as many sessions on 0.9.13 as on
  * the current 0.9.15) and never got the fixes. Nobody edits their MCP config to
@@ -9,7 +9,7 @@
  *
  * So at startup, before binding the port, the server asks the npm registry for
  * the latest version. If it is newer than this copy, it hands off: it runs
- * `npx -y @mehmoodqureshi/chrome-mcp@<latest>` with the same arguments, passes
+ * `npx -y mcp-browser-extension@<latest>` with the same arguments, passes
  * stdin/stdout/stderr straight through (the MCP host talks to the new version
  * directly), and exits when that does. The new copy's server also mirrors its
  * extension build into the unpacked folder, so the extension follows.
@@ -17,12 +17,12 @@
  * It never gets in the way: a dev checkout (not under node_modules) is left
  * alone, the check gives up after a short timeout when offline, a failed spawn
  * falls back to running this copy, and the child is marked so it never hands
- * off again. Off with CHROME_MCP_AUTO_UPDATE=0 or --no-auto-update.
+ * off again. Off with MCP_BROWSER_EXTENSION_AUTO_UPDATE=0 or --no-auto-update.
  */
 import { type ChildProcess, type SpawnOptions } from 'node:child_process';
-export declare const PACKAGE_NAME = "@mehmoodqureshi/chrome-mcp";
+export declare const PACKAGE_NAME = "mcp-browser-extension";
 /** Set on the handed-off child: it is already the latest, never hand off again. */
-export declare const HANDOFF_ENV = "CHROME_MCP_UPDATED_FROM";
+export declare const HANDOFF_ENV = "MCP_BROWSER_EXTENSION_UPDATED_FROM";
 export interface HandOffOptions {
     current: string;
     /** This copy's package directory: only an installed copy (under node_modules) updates. */

package/dist/src/auto-update.js

@@ -1,8 +1,8 @@
 "use strict";
 /**
- * src/auto-update.ts — keep every install on the latest chrome-mcp.
+ * src/auto-update.ts — keep every install on the latest mcp-browser-extension.
  *
- * Most people run chrome-mcp through `npx -y @mehmoodqureshi/chrome-mcp` in an
+ * Most people run mcp-browser-extension through `npx -y mcp-browser-extension` in an
  * MCP config. npx reuses whatever copy it cached first, so installs sat on old
  * versions for weeks (telemetry: three times as many sessions on 0.9.13 as on
  * the current 0.9.15) and never got the fixes. Nobody edits their MCP config to
@@ -10,7 +10,7 @@
  *
  * So at startup, before binding the port, the server asks the npm registry for
  * the latest version. If it is newer than this copy, it hands off: it runs
- * `npx -y @mehmoodqureshi/chrome-mcp@<latest>` with the same arguments, passes
+ * `npx -y mcp-browser-extension@<latest>` with the same arguments, passes
  * stdin/stdout/stderr straight through (the MCP host talks to the new version
  * directly), and exits when that does. The new copy's server also mirrors its
  * extension build into the unpacked folder, so the extension follows.
@@ -18,7 +18,7 @@
  * It never gets in the way: a dev checkout (not under node_modules) is left
  * alone, the check gives up after a short timeout when offline, a failed spawn
  * falls back to running this copy, and the child is marked so it never hands
- * off again. Off with CHROME_MCP_AUTO_UPDATE=0 or --no-auto-update.
+ * off again. Off with MCP_BROWSER_EXTENSION_AUTO_UPDATE=0 or --no-auto-update.
  */
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.HANDOFF_ENV = exports.PACKAGE_NAME = void 0;
@@ -28,17 +28,18 @@ exports.isInstalledCopy = isInstalledCopy;
 exports.maybeHandOff = maybeHandOff;
 const node_child_process_1 = require("node:child_process");
 const node_path_1 = require("node:path");
-exports.PACKAGE_NAME = '@mehmoodqureshi/chrome-mcp';
+const compat_1 = require("./compat");
+exports.PACKAGE_NAME = 'mcp-browser-extension';
 const REGISTRY_URL = `https://registry.npmjs.org/${exports.PACKAGE_NAME}/latest`;
 /** The registry answers in well under this; offline must not delay startup more. */
 const CHECK_TIMEOUT_MS = 1_500;
 /** Set on the handed-off child: it is already the latest, never hand off again. */
-exports.HANDOFF_ENV = 'CHROME_MCP_UPDATED_FROM';
+exports.HANDOFF_ENV = 'MCP_BROWSER_EXTENSION_UPDATED_FROM';
 /** Whether auto-update is off, by env, flag, or because this IS the handed-off copy. */
 function autoUpdateDisabled(env, disabledByFlag = false) {
-    if (disabledByFlag || env[exports.HANDOFF_ENV])
+    if (disabledByFlag || (0, compat_1.runtimeEnv)('UPDATED_FROM', env))
         return true;
-    const v = (env.CHROME_MCP_AUTO_UPDATE ?? '').trim().toLowerCase();
+    const v = ((0, compat_1.runtimeEnv)('AUTO_UPDATE', env) ?? '').trim().toLowerCase();
     return ['0', 'false', 'off', 'no'].includes(v);
 }
 /** True when `latest` is a plain release strictly newer than `current` (x.y.z). */

package/dist/src/bridge/auth.d.ts

@@ -3,7 +3,7 @@
  * drafts was deleted on purpose).
  *
  *   - Fresh 256-bit token EVERY boot by default, never persisted across restarts.
- *     Persistence is OPT-IN (`--persist-token` / `CHROME_MCP_TOKEN`) for hosts
+ *     Persistence is OPT-IN (`--persist-token` / `MCP_BROWSER_EXTENSION_TOKEN`) for hosts
  *     that want a stable token so the extension never has to re-pair.
  *   - Written atomically (tmp + rename) to `handshake.json` at mode 0600; the
  *     mode is re-verified after write and we FAIL CLOSED if it can't be set.
@@ -27,7 +27,7 @@ export declare function readPersistedToken(dir: string): string | null;
 export declare function writePersistedToken(dir: string, token: string): string;
 /**
  * Resolve the token for this boot:
- *   1. `CHROME_MCP_TOKEN` env — an explicit pin; used verbatim, never written to disk.
+ *   1. `MCP_BROWSER_EXTENSION_TOKEN` env — an explicit pin; used verbatim, never written to disk.
  *   2. `persist` on — reuse the on-disk token (creating + saving one on first run),
  *      so the extension stays paired across restarts.
  *   3. otherwise — a fresh per-boot token (the secure default; never persisted).
@@ -63,7 +63,7 @@ export declare function portIsListening(port: number, timeoutMs?: number): Promi
 /**
  * Should a hub on `port` leave `<extDir>/pairing.json` alone? Yes when the file
  * already points the extension at a DIFFERENT port that is still live: another
- * chrome-mcp (e.g. one started with its own CHROME_MCP_DATA / --ws-port) owns
+ * mcp-browser-extension (e.g. one started with its own MCP_BROWSER_EXTENSION_DATA / --ws-port) owns
  * that pairing, and overwriting it would silently steal the user's extension.
  * A file naming our own port, a dead port, or no file at all is fair game.
  */

package/dist/src/bridge/auth.js

@@ -4,7 +4,7 @@
  * drafts was deleted on purpose).
  *
  *   - Fresh 256-bit token EVERY boot by default, never persisted across restarts.
- *     Persistence is OPT-IN (`--persist-token` / `CHROME_MCP_TOKEN`) for hosts
+ *     Persistence is OPT-IN (`--persist-token` / `MCP_BROWSER_EXTENSION_TOKEN`) for hosts
  *     that want a stable token so the extension never has to re-pair.
  *   - Written atomically (tmp + rename) to `handshake.json` at mode 0600; the
  *     mode is re-verified after write and we FAIL CLOSED if it can't be set.
@@ -35,6 +35,7 @@ const node_crypto_1 = require("node:crypto");
 const node_net_1 = require("node:net");
 const protocol_1 = require("../../shared/protocol");
 const datadir_1 = require("./datadir");
+const compat_1 = require("../compat");
 /** A fresh 256-bit token, base64url. Generated once per server boot. */
 function generateToken() {
     return (0, node_crypto_1.randomBytes)(32).toString('base64url');
@@ -91,13 +92,13 @@ function writePersistedToken(dir, token) {
 }
 /**
  * Resolve the token for this boot:
- *   1. `CHROME_MCP_TOKEN` env — an explicit pin; used verbatim, never written to disk.
+ *   1. `MCP_BROWSER_EXTENSION_TOKEN` env — an explicit pin; used verbatim, never written to disk.
  *   2. `persist` on — reuse the on-disk token (creating + saving one on first run),
  *      so the extension stays paired across restarts.
  *   3. otherwise — a fresh per-boot token (the secure default; never persisted).
  */
 function resolveToken(dir, opts) {
-    const fromEnv = process.env.CHROME_MCP_TOKEN?.trim();
+    const fromEnv = (0, compat_1.runtimeEnv)('TOKEN')?.trim();
     if (fromEnv)
         return fromEnv;
     if (opts.persist) {
@@ -176,7 +177,7 @@ function portIsListening(port, timeoutMs = 500) {
 /**
  * Should a hub on `port` leave `<extDir>/pairing.json` alone? Yes when the file
  * already points the extension at a DIFFERENT port that is still live: another
- * chrome-mcp (e.g. one started with its own CHROME_MCP_DATA / --ws-port) owns
+ * mcp-browser-extension (e.g. one started with its own MCP_BROWSER_EXTENSION_DATA / --ws-port) owns
  * that pairing, and overwriting it would silently steal the user's extension.
  * A file naming our own port, a dead port, or no file at all is fair game.
  */

package/dist/src/bridge/datadir.d.ts

@@ -1,6 +1,6 @@
 /**
  * src/bridge/datadir.ts — the Electron-free data dir (the LinkedIn repo resolved
- * this via `app.getPath`; we use `$CHROME_MCP_DATA` || `~/.chrome-mcp`). Holds
+ * this via `app.getPath`; we use `$MCP_BROWSER_EXTENSION_DATA` || `~/.mcp-browser-extension`). Holds
  * the 0600 handshake and, later, the CDP-fallback profile.
  */
 /** Create (if needed) and return the data dir, 0700 so only the user can read it. */

package/dist/src/bridge/datadir.js

@@ -1,7 +1,7 @@
 "use strict";
 /**
  * src/bridge/datadir.ts — the Electron-free data dir (the LinkedIn repo resolved
- * this via `app.getPath`; we use `$CHROME_MCP_DATA` || `~/.chrome-mcp`). Holds
+ * this via `app.getPath`; we use `$MCP_BROWSER_EXTENSION_DATA` || `~/.mcp-browser-extension`). Holds
  * the 0600 handshake and, later, the CDP-fallback profile.
  */
 Object.defineProperty(exports, "__esModule", { value: true });

package/dist/src/bridge/evict.d.ts

@@ -1,9 +1,9 @@
 /**
- * src/bridge/evict.ts — take a pinned port back from a stale chrome-mcp.
+ * src/bridge/evict.ts — take a pinned port back from a stale mcp-browser-extension.
  *
- * A second session normally JOINS the chrome-mcp holding the port as a peer
+ * A second session normally JOINS the mcp-browser-extension holding the port as a peer
  * (see ./peer) and nobody is stopped. This is the fallback for when joining
- * fails: an older chrome-mcp that can't share the port, or a hung one. It will
+ * fails: an older mcp-browser-extension that can't share the port, or a hung one. It will
  * never release the port on its own, so rather than fail with EADDRINUSE and
  * make the user kill it by hand, we do that for them.
  *
@@ -12,13 +12,13 @@
  *   - the handshake names that port (so it describes *this* listener), and
  *   - the pid is not us, and
  *   - the pid is alive, and
- *   - its command line mentions chrome-mcp.
+ *   - its command line mentions mcp-browser-extension.
  * If any check fails we leave the process alone and let the caller surface the
  * plain-English port-busy error instead. Refusing to evict is always safe; a
  * wrong kill is not.
  */
-/** Does this command line belong to a chrome-mcp server? */
-export declare function looksLikeChromeMcp(cmdline: string): boolean;
+/** Does this command line belong to a mcp-browser-extension server? */
+export declare function looksLikeMcpBrowserExtension(cmdline: string): boolean;
 export interface EvictDeps {
     /** Injectable for tests; defaults to the real probes. */
     isAlive?: (pid: number) => boolean;
@@ -26,7 +26,7 @@ export interface EvictDeps {
     kill?: (pid: number, signal: NodeJS.Signals) => void;
 }
 /**
- * Try to free `port` by terminating the chrome-mcp that owns it.
+ * Try to free `port` by terminating the mcp-browser-extension that owns it.
  * Returns true only if an owner was found, killed, and confirmed gone.
  */
 export declare function evictPortOwner(dataDir: string, port: number, log: (message: string) => void, deps?: EvictDeps): Promise<boolean>;