@zibby/mcp-browser 0.1.12 → 2.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +6 -5
- package/dist/package.json +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -97,13 +97,14 @@ By default the wrapper launches a **local** Chromium (the official `@playwright/
|
|
|
97
97
|
behavior). If you set `BROWSER_WS_ENDPOINT` to a remote Chrome's CDP/WS endpoint,
|
|
98
98
|
it instead **connects to that browser over CDP** (`connectOverCDP`) and launches
|
|
99
99
|
**no local Chromium** — so a browser agent can run on a slim image with no baked
|
|
100
|
-
browser binary, pointing at a
|
|
101
|
-
|
|
100
|
+
browser binary, pointing at a HOSTED Chrome (browserless / Browserbase / any
|
|
101
|
+
CDP endpoint). On a Zibby self-host box the platform's own browser is the
|
|
102
|
+
on-demand `browser` sidecar deployed from the marketplace, reached over MCP —
|
|
103
|
+
this knob is only for bringing your own hosted Chrome.
|
|
102
104
|
|
|
103
105
|
```bash
|
|
104
|
-
# Connect to a
|
|
105
|
-
export BROWSER_WS_ENDPOINT=
|
|
106
|
-
# export BROWSER_WS_ENDPOINT=wss://chrome.browserless.io?token=... # hosted
|
|
106
|
+
# Connect to a hosted Chrome over CDP (no local Chromium needed):
|
|
107
|
+
export BROWSER_WS_ENDPOINT='wss://chrome.browserless.io?token=...'
|
|
107
108
|
npx @zibby/mcp-browser
|
|
108
109
|
```
|
|
109
110
|
|
package/dist/package.json
CHANGED