@automatebrowser/mcp 0.3.0

package/.claude-plugin/marketplace.json

@@ -0,0 +1,17 @@
+{
+  "name": "automatebrowser",
+  "owner": {
+    "name": "AutomateBrowser",
+    "url": "https://farazpawle.github.io/automatebrowser/"
+  },
+  "description": "AutomateBrowser — drive your real, logged-in browser from your editor.",
+  "plugins": [
+    {
+      "name": "automate-browser",
+      "source": "./",
+      "description": "The MCP server's 46 browser tools plus the automate-browser skill: tab ownership, page interaction, extraction, sessions, capture and troubleshooting.",
+      "homepage": "https://farazpawle.github.io/automatebrowser/",
+      "license": "MIT"
+    }
+  ]
+}

package/.claude-plugin/plugin.json

@@ -0,0 +1,10 @@
+{
+  "name": "automate-browser",
+  "displayName": "AutomateBrowser",
+  "version": "0.3.0",
+  "description": "Drive your real, logged-in browser from your editor — 46 tools, plus the automate-browser skill covering tab ownership, page interaction, extraction, sessions, capture and troubleshooting.",
+  "author": {
+    "name": "AutomateBrowser"
+  },
+  "keywords": ["browser", "automation", "mcp", "chrome", "scraping"]
+}

package/CHANGELOG.md

@@ -0,0 +1,167 @@
+# Changelog
+
+Notable changes to `@automatebrowser/mcp`. Format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versions follow
+[Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+**Nothing has been published to npm under this name yet.** `0.3.0` is cut and verified and is the
+version the first publish will carry; `0.2.0` was cut the same way on 2026-08-26 and held. Every
+version before those belongs to `@browsermcp/mcp`, the project this one was extracted from. That
+lineage is kept below rather than hidden, because an installed copy that predates the rebrand is
+still out there and its users need somewhere to see what changed. Until that publish happens,
+`[0.3.0]` is what you get by building from source.
+
+Dates are the date of the work, not of a release.
+
+## [Unreleased]
+
+Nothing yet. `0.3.0` was cut on 2026-09-17, and work after it lands here.
+
+## [0.3.0] — 2026-09-17
+
+Cut and verified, **not yet published** — the version the first publish will carry. This is the bulk
+of the current product, substantially more than `[0.2.0]` contains, so it is this section and not
+that one that describes what a user actually receives. `[0.2.0]` stays rather than being absorbed,
+because it names a real cut that the link block below points at.
+
+### Added
+
+- **A terminal client.** `automate-browser` drives the same browser from a shell, joining the same
+  relay mesh as any connected editor.
+- **Performance answers, not just numbers.** Core Web Vitals (LCP, FCP, CLS, INP) rated against
+  Google's thresholds, the long tasks that blocked the main thread, a breakdown of where the LCP time
+  actually went, and re-analysis of a saved trace with no browser attached. Field data from real
+  visitors where an API key is supplied.
+- **A JS heap sampler** that reports the trend over a window, with no debugger and no banner.
+- **Cross-origin iframes** can be driven without the debugger.
+- **`browser_eval` takes a function plus element refs**, so a script can act on elements already
+  found rather than re-querying the DOM.
+- **`browser_emulate`** — location, user agent, extra headers, colour scheme and a responsive set.
+- **`browser_downloads`**, **`browser_issues`**, element and WebP screenshots, coordinate clicking
+  for targets no ref can address, and a strip of stills for showing a person what happened.
+- **`include`** attaches the fresh console or network state to the same reply as the action, removing
+  a round-trip after every navigation.
+- **A structured error taxonomy** — codes, recovery hints and a retryable flag, delivered both as
+  prose and as `structuredContent`.
+- **An action audit log**, with secrets redacted before they are written.
+- **Origin allow/deny lists**, a sensitive-value tier, and a read-only mode.
+- **A remote browser** on another machine, and whole-browser proxy control.
+- **A shipped agent skill** with seven references, installable as a plugin, plus the manifests that
+  make it discoverable.
+- **A landing page** and an out-of-date-install check.
+- **A file-path sandbox** over the client's MCP roots, a pre-flight on write targets so a bad path
+  fails before the work rather than after it, and `AUTOMATE_BROWSER_WORKSPACE` for the many clients
+  that send no roots at all.
+- **An opt-in switch to forbid agent-written JavaScript** entirely.
+- **A ceiling on inline screenshot size**, so a high-density display does not silently cost three
+  times the context for the same picture.
+- **The first unit suite** — no browser, no relay, no model — and a real-Chrome integration suite.
+- **A memory profile of the relay** in CI. It is the one process meant to outlive its clients, and
+  nothing watched it before.
+- **Recovery is visible rather than inferred.** When the connection to the browser drops and comes
+  back, the existing diagnostics say so, instead of leaving an agent to work it out from a failure.
+- **A real-browser regression suite that runs on two browsers**, covering two profiles driven at
+  once, actions two frames deep, and partial form fills — with every failure reporting the scenario,
+  the page, the browser and the two commands that reproduce it.
+- **The extension's command definitions are generated from the server's schemas**, so the two halves
+  of the wire protocol can no longer drift apart without a gate noticing.
+
+### Changed
+
+- **The tool list costs 9,435 tokens per request instead of 10,469 — 9.9% less, with nothing
+  removed.** Every MCP client re-sends every tool schema on every message, so this is the one cost a
+  user pays for doing nothing. Measured across 348 real Claude Code sessions and 89,258 model turns it
+  came to **934 million tokens, 80% of everything this server has ever cost a context** — 92 million of
+  it in 36 sessions that never called a browser tool at all. Two cuts, neither touching a tool, a
+  parameter or a validation rule: the `$schema` dialect key that `zod-to-json-schema` stamps on all 46
+  input and 9 output schemas and the protocol never reads (770 tokens, stripped at the wire by
+  `wireSchema`), and three parameter descriptions that were being restated on up to six tools each —
+  `includeSnapshot` cost 29 tokens six times over. Those explanations moved to the shipped skill's
+  `page-interaction` reference, read once per **task** rather than once per **turn**. Profile ceilings
+  in `scripts/count-tokens.mjs` were lowered to match, the first time they have ever moved down:
+  full 9,580, core 4,210, slim 1,855.
+- **`browser_screenshot` now says what a picture costs**, because the same scan found screenshots to be
+  **half** this server's footprint on a heavy browser day: 249 inline captures averaging ~1,531 tokens
+  each, and an MCP result is re-read on every later turn until the session ends. Only 20 of 445
+  captures scoped themselves to one element. The tool's description and the skill's
+  `capture-and-diagnostics` reference now point at `ref` for a single element, and at `browser_eval` /
+  `browser_find` for a value that needs no picture at all. Deliberately spent 30 of the tokens saved
+  above to say it.
+- **The agent drives only a tab it owns**, and works in the background. It no longer takes over
+  whatever tab the user happens to be looking at.
+- **Element refs survive a re-render**, via stable signatures rather than positional indexes.
+- **Interactions wait for the element to be ready** and for the DOM to settle afterwards.
+- **Transient failures retry automatically**, gated on whether the tool is idempotent.
+- **Five outcomes are told apart, instead of being squeezed through one error flag.** A form fill
+  that lands two fields of three now reports itself as partial rather than as a clean success, and a
+  reply lost on the way back is no longer advertised as safe to retry — for a click, that advice was
+  "click twice". The audit log records which of the five actually happened.
+- **Cookie, storage and header values are redacted by default**; ask for them explicitly.
+- **The console and network lists are paged**, newest first.
+- Snapshots can be lean, full, or written to a file.
+
+### Fixed
+
+- A reconnecting extension no longer orphans the agent's tabs.
+- Background screenshot captures no longer hang; a stall is bounded and named.
+- Advanced mode no longer reshapes a click, and a trusted Enter submits forms.
+- Uncaught page errors keep their stacks.
+- The network log survives a service-worker eviction.
+- Two long-lived logs moved out of the swept temp directory.
+- Dependency advisories pinned so `npm audit --omit=dev` passes.
+- Retrying an action can no longer land on a different browser or a different tab than the one it
+  started against.
+- Passing an address to a tool no longer sidesteps the page restrictions that were meant to judge it.
+- A failed address check no longer skips read-only protection entirely.
+- Invalid response options are rejected **before** the action runs, not after it has already happened.
+- Network restrictions reach every connected browser, not only the first one to connect.
+- One failed reconnection attempt no longer ends automatic recovery for the rest of the session.
+- Element references from different embedded pages no longer resolve against the wrong page, and a
+  form fill or clear aimed at an embedded page reaches it rather than the page around it.
+- A doubly-nested frame is no longer listed twice under a reference that does not work.
+- Reloading a page now waits for the new document rather than reporting the one it replaced.
+- Setting a radio button to "false" no longer switches it on.
+- The schema size budget is enforced for **every** tool profile. It had been measuring only the
+  default one, so two of the three had been quietly over their ceiling for two weeks.
+
+### Removed
+
+- **`acceptInsecureCerts`.** It never worked on any build — Chrome does not expose the certificate
+  domain to extensions — so it could only ever return an error, charged against every request in
+  every editor. Passing it now fails by name rather than being quietly ignored, and says what to do
+  instead: start the browser with `--ignore-certificate-errors`, or click through the warning page
+  once, which is remembered for that host for the session. Everything else works against such a site
+  normally either way.
+
+## [0.2.0] — 2026-08-26
+
+Cut and verified, **not published**. The first version under the AutomateBrowser name.
+
+### Added
+
+- **A singleton relay.** One process owns the port; every editor connects to it as a controller, so
+  several editors share one browser instead of fighting over a port.
+- **Per-tab ownership** — two editors can drive two tabs of the same browser at once, with soft-claim
+  leases, lease-loss notifications and a roster in the extension popup.
+- **A debugger-free extension**, rewritten with an always-on connection, so the yellow automation
+  banner is gone for everything but the opt-in CDP features.
+- **Tool profiles** (`full`, `core`, `slim`) behind a registry, a per-call timeout, a per-controller
+  send queue, and a console-error footer on mutating calls.
+- **A tool-schema token budget** and a release verification gate, both enforced in CI.
+- **A generated tool reference** in the README, written from the live schemas.
+- **Auto-recovery** when the extension's service worker is asleep.
+- A warning when the relay is a different build from the server talking to it.
+
+### Changed
+
+- Renamed from `@browsermcp/mcp` to `@automatebrowser/mcp`; de-branded throughout.
+
+## [0.1.3] — 2025-04-25
+
+The last release of `@browsermcp/mcp`, the upstream project this was extracted from, published to npm
+under that name. `0.1.0` through `0.1.2` precede it; this repository begins at the point the server
+was extracted from that monorepo on 2025-03-27, and no history before that is reproduced here.
+
+[Unreleased]: https://github.com/farazpawle/automatebrowser/compare/v0.3.0...HEAD
+[0.3.0]: https://github.com/farazpawle/automatebrowser/compare/cf28a4b...v0.3.0
+[0.2.0]: https://github.com/farazpawle/automatebrowser/commit/cf28a4b

package/LICENSE

@@ -0,0 +1,202 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1.  Definitions.
+
+    "License" shall mean the terms and conditions for use, reproduction,
+    and distribution as defined by Sections 1 through 9 of this document.
+
+    "Licensor" shall mean the copyright owner or entity authorized by
+    the copyright owner that is granting the License.
+
+    "Legal Entity" shall mean the union of the acting entity and all
+    other entities that control, are controlled by, or are under common
+    control with that entity. For the purposes of this definition,
+    "control" means (i) the power, direct or indirect, to cause the
+    direction or management of such entity, whether by contract or
+    otherwise, or (ii) ownership of fifty percent (50%) or more of the
+    outstanding shares, or (iii) beneficial ownership of such entity.
+
+    "You" (or "Your") shall mean an individual or Legal Entity
+    exercising permissions granted by this License.
+
+    "Source" form shall mean the preferred form for making modifications,
+    including but not limited to software source code, documentation
+    source, and configuration files.
+
+    "Object" form shall mean any form resulting from mechanical
+    transformation or translation of a Source form, including but
+    not limited to compiled object code, generated documentation,
+    and conversions to other media types.
+
+    "Work" shall mean the work of authorship, whether in Source or
+    Object form, made available under the License, as indicated by a
+    copyright notice that is included in or attached to the work
+    (an example is provided in the Appendix below).
+
+    "Derivative Works" shall mean any work, whether in Source or Object
+    form, that is based on (or derived from) the Work and for which the
+    editorial revisions, annotations, elaborations, or other modifications
+    represent, as a whole, an original work of authorship. For the purposes
+    of this License, Derivative Works shall not include works that remain
+    separable from, or merely link (or bind by name) to the interfaces of,
+    the Work and Derivative Works thereof.
+
+    "Contribution" shall mean any work of authorship, including
+    the original version of the Work and any modifications or additions
+    to that Work or Derivative Works thereof, that is intentionally
+    submitted to Licensor for inclusion in the Work by the copyright owner
+    or by an individual or Legal Entity authorized to submit on behalf of
+    the copyright owner. For the purposes of this definition, "submitted"
+    means any form of electronic, verbal, or written communication sent
+    to the Licensor or its representatives, including but not limited to
+    communication on electronic mailing lists, source code control systems,
+    and issue tracking systems that are managed by, or on behalf of, the
+    Licensor for the purpose of discussing and improving the Work, but
+    excluding communication that is conspicuously marked or otherwise
+    designated in writing by the copyright owner as "Not a Contribution."
+
+    "Contributor" shall mean Licensor and any individual or Legal Entity
+    on behalf of whom a Contribution has been received by Licensor and
+    subsequently incorporated within the Work.
+
+2.  Grant of Copyright License. Subject to the terms and conditions of
+    this License, each Contributor hereby grants to You a perpetual,
+    worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+    copyright license to reproduce, prepare Derivative Works of,
+    publicly display, publicly perform, sublicense, and distribute the
+    Work and such Derivative Works in Source or Object form.
+
+3.  Grant of Patent License. Subject to the terms and conditions of
+    this License, each Contributor hereby grants to You a perpetual,
+    worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+    (except as stated in this section) patent license to make, have made,
+    use, offer to sell, sell, import, and otherwise transfer the Work,
+    where such license applies only to those patent claims licensable
+    by such Contributor that are necessarily infringed by their
+    Contribution(s) alone or by combination of their Contribution(s)
+    with the Work to which such Contribution(s) was submitted. If You
+    institute patent litigation against any entity (including a
+    cross-claim or counterclaim in a lawsuit) alleging that the Work
+    or a Contribution incorporated within the Work constitutes direct
+    or contributory patent infringement, then any patent licenses
+    granted to You under this License for that Work shall terminate
+    as of the date such litigation is filed.
+
+4.  Redistribution. You may reproduce and distribute copies of the
+    Work or Derivative Works thereof in any medium, with or without
+    modifications, and in Source or Object form, provided that You
+    meet the following conditions:
+
+    (a) You must give any other recipients of the Work or
+    Derivative Works a copy of this License; and
+
+    (b) You must cause any modified files to carry prominent notices
+    stating that You changed the files; and
+
+    (c) You must retain, in the Source form of any Derivative Works
+    that You distribute, all copyright, patent, trademark, and
+    attribution notices from the Source form of the Work,
+    excluding those notices that do not pertain to any part of
+    the Derivative Works; and
+
+    (d) If the Work includes a "NOTICE" text file as part of its
+    distribution, then any Derivative Works that You distribute must
+    include a readable copy of the attribution notices contained
+    within such NOTICE file, excluding those notices that do not
+    pertain to any part of the Derivative Works, in at least one
+    of the following places: within a NOTICE text file distributed
+    as part of the Derivative Works; within the Source form or
+    documentation, if provided along with the Derivative Works; or,
+    within a display generated by the Derivative Works, if and
+    wherever such third-party notices normally appear. The contents
+    of the NOTICE file are for informational purposes only and
+    do not modify the License. You may add Your own attribution
+    notices within Derivative Works that You distribute, alongside
+    or as an addendum to the NOTICE text from the Work, provided
+    that such additional attribution notices cannot be construed
+    as modifying the License.
+
+    You may add Your own copyright statement to Your modifications and
+    may provide additional or different license terms and conditions
+    for use, reproduction, or distribution of Your modifications, or
+    for any such Derivative Works as a whole, provided Your use,
+    reproduction, and distribution of the Work otherwise complies with
+    the conditions stated in this License.
+
+5.  Submission of Contributions. Unless You explicitly state otherwise,
+    any Contribution intentionally submitted for inclusion in the Work
+    by You to the Licensor shall be under the terms and conditions of
+    this License, without any additional terms or conditions.
+    Notwithstanding the above, nothing herein shall supersede or modify
+    the terms of any separate license agreement you may have executed
+    with Licensor regarding such Contributions.
+
+6.  Trademarks. This License does not grant permission to use the trade
+    names, trademarks, service marks, or product names of the Licensor,
+    except as required for reasonable and customary use in describing the
+    origin of the Work and reproducing the content of the NOTICE file.
+
+7.  Disclaimer of Warranty. Unless required by applicable law or
+    agreed to in writing, Licensor provides the Work (and each
+    Contributor provides its Contributions) on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+    implied, including, without limitation, any warranties or conditions
+    of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+    PARTICULAR PURPOSE. You are solely responsible for determining the
+    appropriateness of using or redistributing the Work and assume any
+    risks associated with Your exercise of permissions under this License.
+
+8.  Limitation of Liability. In no event and under no legal theory,
+    whether in tort (including negligence), contract, or otherwise,
+    unless required by applicable law (such as deliberate and grossly
+    negligent acts) or agreed to in writing, shall any Contributor be
+    liable to You for damages, including any direct, indirect, special,
+    incidental, or consequential damages of any character arising as a
+    result of this License or out of the use or inability to use the
+    Work (including but not limited to damages for loss of goodwill,
+    work stoppage, computer failure or malfunction, or any and all
+    other commercial damages or losses), even if such Contributor
+    has been advised of the possibility of such damages.
+
+9.  Accepting Warranty or Additional Liability. While redistributing
+    the Work or Derivative Works thereof, You may choose to offer,
+    and charge a fee for, acceptance of support, warranty, indemnity,
+    or other liability obligations and/or rights consistent with this
+    License. However, in accepting such obligations, You may act only
+    on Your own behalf and on Your sole responsibility, not on behalf
+    of any other Contributor, and only if You agree to indemnify,
+    defend, and hold each Contributor harmless for any liability
+    incurred by, or claims asserted against, such Contributor by reason
+    of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+Portions Copyright (c) Microsoft Corporation.
+Portions Copyright 2017 Google Inc.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.