ZennoBrowser MCP Server

What ZennoBrowser MCP Server does

ZennoBrowser MCP Server MCP server exposes ZennoBrowser’s Public API to MCP-compatible clients. It lets an agent manage the resources used by the antidetect browser, including workspaces, browser profiles, profile folders, proxies, proxy folders, threads, browser instances, presets, and extensions.

The server also supports profile data operations. Agents can inspect full fingerprint details, import or export cookies, copy cookies between profiles, update profile proxies and tags in bulk, assign presets, recover invalid profiles, force-unlock cloud-locked profiles, and clear profile caches. Product-level tools report ZennoBrowser and browser engine versions, workspace limits, and tariff information.

How it works

The package runs as a local stdio MCP server. An MCP client starts the Node.js process with npx or a globally installed command, and the process sends requests to the ZennoBrowser Public API. ZennoBrowser must already be running locally, and the server uses an API token supplied through the environment.

Operations can be performed individually or in bulk. For example, an agent can create a profile, create and assign a proxy, create a thread, and start a browser instance. Bulk tools cover profile creation and deletion, proxy creation and deletion, thread creation and lifecycle actions, browser startup and shutdown, and several profile updates.

ZennoBrowser MCP Server MCP server is intended for workflows where an agent needs to coordinate browser resources rather than only open a page. Destructive operations such as deleting profiles or proxies cannot be undone, so actions that invoke those tools should be reviewed before approval.

Setup and configuration

Use Node.js 20 or newer, start ZennoBrowser on the local machine, and obtain a valid API token from ZennoLab. The published package is @zennolab/zennobrowser-mcp-server; older unscoped package versions no longer receive updates.

A client can launch the server without a local package installation:

{
  "command": "npx",
  "args": ["-y", "@zennolab/zennobrowser-mcp-server@latest"],
  "env": {
    "ZB_API_TOKEN": "your-api-token-here"
  }
}

Alternatively, install the package globally with npm and use zennobrowser-mcp-server as the command. ZB_API_TOKEN is required for authentication. ZB_API_BASE_URL is optional and defaults to http://localhost:8160; set it when the ZennoBrowser Public API uses another base URL or port.

The README provides configurations for Claude Desktop, Cursor, and VS Code with GitHub Copilot MCP support. A connection-refused error on the default address generally means ZennoBrowser or its Public API is not running, or that the API is configured on another port.

Tools and capabilities

The server provides 57 tools grouped into these areas:

• Workspaces: list accessible workspaces.
• Profiles: list, inspect, create, update, delete, move, recover, unlock, clean up, and manage cookies.
• Folders: create, list, rename, and delete profile or proxy folders.
• Proxies: list, create, update, delete, bulk-create, bulk-delete, and rotate a mobile proxy IP.
• Threads: create, list, extend, stop, and apply lifecycle actions in bulk.
• Browser instances: list active instances, start or stop them, perform bulk start or stop actions, and change window visibility.
• Presets and extensions: create or delete presets, list extensions, and add extensions from the Chrome Web Store or local .crx and .zip files.
• Product information: retrieve ZennoBrowser version, browser engine version, workspace limits, and tariff details.

ZennoBrowser MCP Server MCP server fits agent workflows that need both resource administration and browser-instance control. It does not replace ZennoBrowser itself; the desktop application and its Public API must be available for requests to succeed.