ZennoBrowser 1.15.1 was released on June 17 with the first version of its MCP server. AI agents such as Claude and Cursor, along with other MCP-compatible clients, can use it to manage profiles and proxies and launch the browser right from a chat. The server is available on npm as zennobrowser-mcp-server, version 1.0.0, under the MIT license. The package description says it requires Node.js 20 or later, ZennoBrowser running on the same computer, and a public API token. It includes 57 tools, from creating profiles and importing cookies to changing a mobile proxy’s IP and launching browsers in batches.
The profile API now includes a type (local or cloud) and a state (running or stopped). The status field has been renamed statusSync, so scripts that read status need to be updated. Fingerprints now support an explicit Windows version selection: 10 or 11. The browser engine was updated to build 148.1.8.
Version 1.15.2, released on June 23, added Chrome 149 and a patch for SOCKS5 proxies. Five days earlier, users reported in the 1.15.1 thread that some sites stopped loading through SOCKS5 after the update, while the same proxies worked over HTTPS. Support confirmed the bug and called the situation critical, but gave no timeline for a fix. Rolling back to the previous version wasn’t possible. On June 29, version 1.15.3 fixed cloud profile data syncing and proxy connections when switching from TLS 1.3 to 1.2.
