@raultov/browser-control-mcp 0.4.0-beta.7 → 0.5.0-beta.8

package/CHANGELOG.md

@@ -10,6 +10,68 @@ from a copy of its code: entries describe the differences from that release.
 
 ## [Unreleased]
 
+## [0.5.0-beta.8] - 2026-10-31
+
+Public **BETA**. Closes the rest of the Playwright MCP comparison: the new
+`network` tool group mocks requests (`mock_route`, `list_routes`,
+`remove_route`) and takes a tab offline (`set_offline`), `save_pdf` prints
+a tab to PDF, and `--secrets` keeps known values out of what the agent
+reads. Debugging a paused page works better: `evaluate_js` answers at once
+on Chrome, a pause names its script, and the input tools fail at once
+naming the pause instead of reporting a click or a text that has not
+happened (a behaviour change: they used to "succeed").
+
+### Added
+
+- `--secrets <file>` (dotenv): every tool result and error shows the
+  file's values as `<secret:NAME>` (as is or escaped in JSON), and
+  `fill_input` / `fill_form` type the value of a `<secret:NAME>` they are
+  given, so the agent can fill a password without reading it. A
+  convenience, not a security boundary: images are not masked and a page
+  can transform a value. Values never reach the logs. (#14)
+- `save_pdf`, in the `files` tool group: prints the tab to PDF
+  (`landscape`, `print_background`, `scale`, `page_ranges`) and writes it to
+  `path`, an absolute `.pdf` under the upload roots, answering `{path,
+  bytes, pages}`; without `path` the PDF comes back as an embedded
+  `application/pdf` resource (at most 5 MB). Chrome `Page.printToPDF`,
+  Firefox `browsingContext.print`. (#13)
+- `mock_route`, `list_routes`, `remove_route` and `set_offline`, in the new
+  `network` tool group (`--tool-groups network`). A route answers the tab's
+  requests whose URL matches a glob with a mocked status, body, content
+  type and headers, without reaching the network; the latest matching
+  route wins and `list_routes` counts its hits. Chrome uses the `Fetch`
+  domain (not while `enable_proxy_auth` is active), Firefox a
+  `beforeRequestSent` network intercept. `set_offline` takes the tab
+  offline or back online (Chrome still serves its HTTP cache). (#12)
+
+### Fixed
+
+- The input tools (`click_element`, `hover`, `fill_input`, `fill_form`,
+  `press_key`) fail at once, naming the pause, when the page is already
+  paused in the debugger, and send nothing: the page handles input events
+  only once it resumes. Chrome reported a click or a key as done, and
+  both browsers blamed the field ("rejected the text") or, on Firefox, a
+  covering `html` element. (#17)
+- On Chrome `evaluate_js` answers at once while the page is paused in the
+  debugger: it waited 10 s and failed with "no result after 10 s", even
+  for `1 + 1`, because Chrome cannot await an evaluation while no
+  microtask runs. It now evaluates without awaiting, reads a settled promise from
+  its state, and fails at once on a pending one, saying to `resume` or use
+  `evaluate_on_call_frame`. (#16)
+- On Chrome a pause's location names its script: `resume`, `step_over`,
+  the `{paused, location}` of `click_element` and `press_key`, and the
+  "The page paused in the debugger at ..." message of an interrupted call
+  gave `url: null`, because Chrome leaves the deprecated
+  `callFrames[].url` empty. The URL now comes from the tab's parsed
+  scripts, and the location also carries `script_id` (what
+  `set_breakpoint` takes). (#10)
+
+### Changed
+
+- The package description (crates.io, npm, Homebrew `desc`) is 79
+  characters instead of 213, within Homebrew's 80, so `brew style` no
+  longer flags the formula's `desc` line as too long.
+
 ## [0.4.0-beta.7] - 2026-10-31
 
 Public **BETA**. Closes the gaps a comparison with Playwright MCP showed:

package/README.md

@@ -11,7 +11,7 @@ It is the successor of
 from a copy of its code) and complements Playwright MCP or
 chrome-devtools-mcp with runtime JavaScript debugging on both browsers.
 
-> **Status: BETA (0.4.0-beta.7).** This version contains known bugs and differences
+> **Status: BETA (0.5.0-beta.8).** This version contains known bugs and differences
 > between Chrome and Firefox (see [Limitations and TODO](#limitations-and-todo))
 > and parts that have not been verified (see [Untested](#untested)). Tool
 > replies may change in incompatible ways before 1.0. Please report problems
@@ -37,10 +37,11 @@ tools are off by default and listed only with `--tool-groups`:
 | Group | Tools | Why it is opt-in |
 | --- | --- | --- |
 | `storage` | `cookies`, `web_storage` | reads and changes session tokens |
-| `files` | `upload_file` | hands a page files of the machine |
+| `files` | `upload_file`, `save_pdf` | reads and writes files of the machine |
 | `raw` | `send_cdp_command`, `send_bidi_command`, `send_rdp_request`, `get_custom_events` | anything the protocol allows |
 | `perf` | `get_performance_metrics`, `profile_page_performance` | niche |
 | `emulation` | `emulate` | niche |
+| `network` | `mock_route`, `list_routes`, `remove_route`, `set_offline` | changes what the page receives |
 
 `--tool-groups all` lists every group. The page, input, observation and
 debugger tools are always listed (33 tools), plus `enable_proxy_auth` with
@@ -73,6 +74,7 @@ see the note.
 | `inspect_dom` | ✓ | ✓ | includes open shadow roots and same-origin iframes (cross-origin ones are noted); at most 100 000 characters without `query` (cut in the page) |
 | `snapshot` | ✓ | ✓ | outline of the page: role, name, states, value and a ref (`e12`) per element, through open shadow roots and same-origin iframes; at most 50 000 characters (`selector` and `depth` narrow it); the same JavaScript on both browsers |
 | `find_in_snapshot` | ✓ | ✓ | `text` (case-insensitive) or `regex` over the whole outline; matching lines under their ancestors, at most 20 |
+| `save_pdf` | ✓ | ✓ | `files` group; prints the tab as the browser's print does (`landscape`, `print_background`, `scale` 0.1–2, `page_ranges` like `1-3, 5`); with `path` (an absolute `.pdf` under the upload roots) writes the file and answers `{path, bytes, pages}`, else returns the PDF as an embedded `application/pdf` resource (at most 5 MB); Chrome `Page.printToPDF`, Firefox `browsingContext.print` |
 | `capture_screenshot` | ✓ | ✓ | `format` `png`, `jpeg` (or `jpg`) or `webp`; `full_page` at most 16 384 px per side (a text note says when cut) |
 | `click_element` | ✓ | ✓ | scrolls the element into view; `button` (left/right/middle), `click_count` (2 = double click) and `modifiers`; fails without clicking when it is hidden or covered; `host >>> inner` selectors reach open shadow roots and same-origin iframes (also in `fill_input`, `scroll`, `wait_for`); a dialog or debugger pause the click causes is noted in a successful reply (`{dialog}` or `{paused, location}`) |
 | `fill_input` | ✓ | ✓ | picks `<select>` options; fails without typing on elements that cannot take the text; types key by key on both (key handlers run; newlines and tabs inserted as text), about 1 ms per character; `change` on leaving the field, or at the end when the window has no focus |
@@ -86,6 +88,10 @@ see the note.
 | `web_storage` | ✓ | ✓ | `storage` group; `get` / `set` / `delete` / `clear` on the page's `localStorage` or `sessionStorage`; values hidden unless `show_values: true` |
 | `get_console_logs` | ✓ | ✓ | a message keeps at most 10 000 characters; Firefox: page errors, CSS warnings and platform messages need the debugger port |
 | `get_network_logs` | ✓ | ✓ | a failed request has `error`, a binary body `response_body_encoding: "base64"`; bodies at most 64 000 characters, none over 2 MB; a WebSocket payload keeps 64 000 (`payload_len` is the whole); Firefox: WebSocket frames need the debugger port |
+| `mock_route` | ✓ | ✓ | `network` group; requests whose URL matches a glob (`*`, `?`, `\` escapes) get a mocked `status`, `body` (text, at most 1 MB), `content_type` and `headers` without reaching the network; the latest matching route wins; at most 50 routes per tab, kept until `remove_route` or the tab closes (Chrome `Fetch`, not while `enable_proxy_auth` is active; Firefox a `network` intercept) |
+| `list_routes` | ✓ | ✓ | `network` group; the tab's routes with the `hits` each answered |
+| `remove_route` | ✓ | ✓ | `network` group; one route by id, or all |
+| `set_offline` | ✓ | ✓ | `network` group; requests fail as without a network and `navigator.onLine` is false, until set back (Chrome `Network.emulateNetworkConditions`, Firefox `emulation.setNetworkConditions`); mocked routes still answer; Chrome still serves what its HTTP cache holds, as an offline browser does, Firefox fails every request |
 | `get_custom_events` | ✓ | partial | `raw` group; `{events, total, truncated}`, the newest `limit` events; `clear` removes the returned ones; params over 64 000 characters of JSON are replaced by `{truncated, characters}`; Firefox: events of the modules subscribed with `send_bidi_command` |
 | `get_performance_metrics` | ✓ | partial | `perf` group; Firefox: `Nodes`, `Frames`, `Resources`, `TransferSize` from the Web Performance APIs (no Performance domain), plus a note |
 | `profile_page_performance` | ✓ | partial | `perf` group; Firefox: FCP, LCP, DCL and Load from the Web Performance APIs; no trace, so `total_blocking_time_ms` and `top_long_tasks` are `null` |
@@ -379,8 +385,9 @@ claude mcp add browser-control-mcp -- npx -y @raultov/browser-control-mcp
 | `--enable-automation` | off | shows the automation infobar | ignored; `list_instances` shows a warning |
 | `--user-profile` | off | your default profile (no `--user-data-dir`) | only with `--firefox-port` (attach to your running Firefox) |
 | `--allow-cookie-import` | off | exposes `copy_cookies` | capability error |
-| `--tool-groups <GROUPS>` | none | lists the opt-in tool groups, comma separated: `storage`, `files`, `raw`, `perf`, `emulation` or `all` (see [Tool groups](#tool-groups)) | same |
-| `--upload-root <DIR>` | working + temp dir | directory `upload_file` may read files from (repeatable; replaces the defaults) | same |
+| `--secrets <FILE>` | none | dotenv file (`NAME=value`, at least 4 characters per value) whose values every tool result and error shows as `<secret:NAME>`; `fill_input` and `fill_form` type the value of a `<secret:NAME>` (see [Security notes](#security-notes)) | same |
+| `--tool-groups <GROUPS>` | none | lists the opt-in tool groups, comma separated: `storage`, `files`, `raw`, `perf`, `emulation`, `network` or `all` (see [Tool groups](#tool-groups)) | same |
+| `--upload-root <DIR>` | working + temp dir | directory `upload_file` may read files from and `save_pdf` may write PDFs to (repeatable; replaces the defaults) | same |
 | `--enable-webmcp` | off | WebMCP switches and `webmcp_*` tools | capability error |
 | `--proxy-server <URL>` | none | proxy for every instance; exposes `enable_proxy_auth` | `http://` and `socks5://` proxies |
 | `--proxy-username <USER>` | none | answers proxy (407) challenges | same (untested) |
@@ -441,7 +448,13 @@ Chrome and Firefox take the same calls:
    unfinished (`evaluate_js`, `fill_input`, `navigate`...) fails at once
    with that location.
 5. `evaluate_on_call_frame` reads locals of the paused frame; `step_over`
-   moves one statement; `resume` continues.
+   moves one statement; `resume` continues. While paused, the input tools
+   (`click_element`, `hover`, `fill_input`, `fill_form`, `press_key`) fail
+   at once naming the pause and do nothing: the page would handle their
+   events only after `resume`. `evaluate_js` still answers
+   while paused, in the page's global scope. A promise it returns cannot
+   always settle meanwhile: Chrome reads a settled one and fails at once on
+   a pending one; Firefox settles it when its microtasks can run.
 6. `remove_breakpoint` with the id `set_breakpoint` returned.
 
 Both browsers answer the same replies, with 0-based lines everywhere:
@@ -450,7 +463,7 @@ Both browsers answer the same replies, with 0-based lines everywhere:
 | --- | --- |
 | `set_breakpoint` | `{"breakpoint_id": "bp-N", "url", "line_number", "column_number", "resolved"}`: where the browser bound it; `resolved` is false until a script with that URL loads |
 | `remove_breakpoint` | `{"removed": "bp-N"}`; an unknown id fails listing the tab's ids |
-| `step_over`, `resume` | `{"paused", "location": {"url", "line_number", "column_number"} \| null}`: where the thread stopped next (`step_over` waits up to 2 s; `resume` reports a pause only if one follows within 250 ms) |
+| `step_over`, `resume` | `{"paused", "location": {"url", "script_id"?, "line_number", "column_number"} \| null}`: where the thread stopped next (`script_id` on Chrome, for `set_breakpoint`) (`step_over` waits up to 2 s; `resume` reports a pause only if one follows within 250 ms) |
 | `evaluate_on_call_frame` | the `evaluate_js` shape; an exception fails with `Evaluation threw: <what was thrown>` |
 
 Breakpoint ids are per tab and MCP-level (`bp-1`, `bp-2`...), like tab ids.
@@ -558,6 +571,19 @@ incompatible:
   the upload roots (the server's working directory and the system temp
   directory, or the `--upload-root` directories), resolved so `..` and
   symlinks cannot leave them. Paths are never logged.
+- `--secrets <file>` keeps known values (test passwords, API keys) out of
+  what the agent reads: every tool result and error (text, embedded text,
+  structured content) shows them as `<secret:NAME>`, also when escaped
+  inside JSON, and `fill_input` / `fill_form` type the value of a
+  `<secret:NAME>` they are given, so the agent can log in without seeing
+  the password. It is a convenience, not a security boundary: the page can
+  transform a value (encode it, split it) past the masking, images
+  (screenshots, PDFs) are not masked, and the server stops at start-up if
+  the file has a malformed line, a value shorter than 4 characters or a
+  name defined twice (the error names the line, never a value). Values
+  never reach the logs.
+- `save_pdf` writes only `.pdf` files, under the same upload roots and
+  resolved the same way; it overwrites an existing `.pdf` there.
 - The proxy password is never logged and is given only to proxy (407)
   challenges, never to a site's own authentication.
 - The Firefox debugger port needs `devtools.chrome.enabled`: any local

package/npm-shrinkwrap.json

@@ -19,7 +19,7 @@
       "hasInstallScript": true,
       "license": "MIT",
       "name": "@raultov/browser-control-mcp",
-      "version": "0.4.0-beta.7"
+      "version": "0.5.0-beta.8"
     },
     "node_modules/detect-libc": {
       "engines": {
@@ -48,5 +48,5 @@
     }
   },
   "requires": true,
-  "version": "0.4.0-beta.7"
+  "version": "0.5.0-beta.8"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "artifactDownloadUrls": [
-    "https://github.com/raultov/browser-control-mcp/releases/download/v0.4.0-beta.7"
+    "https://github.com/raultov/browser-control-mcp/releases/download/v0.5.0-beta.8"
   ],
   "author": "raultov <raultov@protonmail.com>",
   "bin": {
@@ -9,7 +9,7 @@
   "dependencies": {
     "detect-libc": "^2.1.2"
   },
-  "description": "MCP server to control and debug Chrome and Firefox at runtime: breakpoints, call frames and stepping over CDP and WebDriver BiDi/RDP, plus navigation, DOM, input, screenshots, console and network capture.",
+  "description": "MCP server to control and debug Chrome and Firefox, with JavaScript breakpoints",
   "devDependencies": {
     "prettier": "^3.8.3"
   },
@@ -92,7 +92,7 @@
       "zipExt": ".tar.xz"
     }
   },
-  "version": "0.4.0-beta.7",
+  "version": "0.5.0-beta.8",
   "volta": {
     "node": "18.14.1",
     "npm": "9.5.0"