@mehmoodqureshi/chrome-mcp 0.9.8 → 0.9.9

package/README.md

@@ -108,6 +108,15 @@ explicitly (and is never written to disk).
 
 **2. Load the extension** — **required**; the server can drive nothing without it.
 
+Two ways to get it:
+
+- **[Install from the Chrome Web Store](https://chromewebstore.google.com/detail/mcp-extension-for-chrome/jelfhdlkhbfmlpbghoeaepijllcnplgh)** — one click, no
+  Developer mode, and Chrome keeps it updated. The Web Store build is reviewed
+  before each release, so it can trail the npm package by a version; it pairs
+  with any server and simply skips features it predates.
+- **Load the bundled folder** (below) — always matches the npm package you just
+  installed, and the right choice when you want the newest behaviour.
+
 The extension ships prebuilt inside the npm package, and every time the server
 boots it copies it to a plain folder right under your home directory:
 
@@ -558,6 +567,12 @@ RUN_EXT_SMOKE=1 node --test dist/test/extension-smoke.test.js   # live, headed
 
 ## The extension
 
+Published on the Chrome Web Store as
+**[MCP Extension for Chrome](https://chromewebstore.google.com/detail/mcp-extension-for-chrome/jelfhdlkhbfmlpbghoeaepijllcnplgh)**.
+Extension versions move only when `extension/` changes, so the listed build can
+sit a release behind the npm package; the two negotiate capabilities on
+connect, so an older extension loses features rather than breaking.
+
 `extension/` builds (esbuild) to `extension-dist/`, loaded via
 `chrome://extensions` → **Load unpacked** → select `~/chrome-mcp-extension`, the
 mirror the server refreshes from `extension-dist/` on every boot (loading

package/SETUP.md

@@ -112,6 +112,12 @@ You cannot do this step yourself. Give the human these exact instructions:
 
 Wait for the human to confirm before continuing.
 
+If the human would rather not enable Developer mode, they can install
+[MCP Extension for Chrome](https://chromewebstore.google.com/detail/mcp-extension-for-chrome/jelfhdlkhbfmlpbghoeaepijllcnplgh)
+from the Chrome Web Store instead and skip steps 1–3. Prefer the unpacked
+folder when following this guide: it matches the package just installed, while
+the Web Store build passes review separately and can trail it by a version.
+
 ## Step 5 — Pairing (automatic; verify it)
 
 Pairing needs no paste. Every time the server boots it writes `pairing.json`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mehmoodqureshi/chrome-mcp",
-  "version": "0.9.8",
+  "version": "0.9.9",
   "description": "Drive your real Chrome browser over MCP — real logins, real cookies. A stdio MCP server (CLI) plus an MV3 extension, driving Chrome via chrome.scripting/chrome.tabs. Multi-tab batch automation, accessibility snapshots, deny-all security by default.",
   "author": "Mehmood Ur Rehman Qureshi",
   "license": "MIT",