mcpbrowser 0.3.56 → 0.3.57
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 +25 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -498,6 +498,31 @@ Logs go to `stderr` so they don't interfere with MCP protocol on `stdout`.
|
|
|
498
498
|
- Keep the browser tab open (default behavior)
|
|
499
499
|
- Use the same domain for related requests
|
|
500
500
|
|
|
501
|
+
**E401 error with `npx` / private npm registry?**
|
|
502
|
+
|
|
503
|
+
If your project has a `.npmrc` that points to a private registry (e.g., Azure Artifacts, GitHub Packages, Artifactory), `npx` will try to fetch `mcpbrowser` from that registry instead of npmjs.org and fail with `E401`.
|
|
504
|
+
|
|
505
|
+
**Fix:** Add `npm_config_registry` to the `env` block in your MCP config:
|
|
506
|
+
```json
|
|
507
|
+
{
|
|
508
|
+
"mcpServers": {
|
|
509
|
+
"mcpbrowser": {
|
|
510
|
+
"command": "npx",
|
|
511
|
+
"args": ["-y", "mcpbrowser@latest"],
|
|
512
|
+
"env": {
|
|
513
|
+
"npm_config_registry": "https://registry.npmjs.org"
|
|
514
|
+
}
|
|
515
|
+
}
|
|
516
|
+
}
|
|
517
|
+
}
|
|
518
|
+
```
|
|
519
|
+
|
|
520
|
+
**Alternative:** Install globally to skip `npx` entirely:
|
|
521
|
+
```bash
|
|
522
|
+
npm install -g mcpbrowser
|
|
523
|
+
```
|
|
524
|
+
Then use `"command": "mcpbrowser"` with no `args` in your MCP config.
|
|
525
|
+
|
|
501
526
|
## Links
|
|
502
527
|
|
|
503
528
|
- [GitHub](https://github.com/cherchyk/MCPBrowser)
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "mcpbrowser",
|
|
3
|
-
"version": "0.3.
|
|
3
|
+
"version": "0.3.57",
|
|
4
4
|
"mcpName": "io.github.cherchyk/mcpbrowser",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"description": "MCP browser server — loads and interacts with web pages using the user's Chromium-based browser with full JavaScript execution. Handles authentication, SSO, and anti-bot protection automatically via the user's existing browser session.",
|