
ZennoBrowser MCP Server
io.github.ZennoLabPublished by GitHub account ZennoLabv1.1.2Updated Oct 27, 2026
MCP server for ZennoBrowser antidetect browser: manage browser profiles from AI agents
Overview
Local MCP server that lets an AI agent manage ZennoBrowser antidetect browser profiles, proxies, cookies, threads and browser instances.
- What you can do
- List workspaces and manage profiles: create, bulk create, update, move, delete, recover, unlock and clean up, plus read fingerprint details
- Import, export and copy cookies between profiles, and assign presets, proxies and tags in bulk
- Manage profile folders, proxies and proxy folders, including bulk creation, deletion and mobile proxy IP rotation
- Create, extend and stop threads, and start, stop, bulk start or hide browser instances
- List, create and delete presets and extensions, and read product, browser engine, limit and tariff information
- When to use it
- Useful when you run ZennoBrowser on Windows and want an agent to set up and operate many antidetect browser profiles, proxies and sessions from Claude Desktop, Cursor or VS Code instead of clicking through the app.
- Requirements
- Node.js 20 or newer, ZennoBrowser running locally, and a ZennoBrowser API token supplied in the ZB_API_TOKEN environment variable. The optional ZB_API_BASE_URL variable defaults to the local API address. Runs as a local stdio process; Windows only.
Installation
In SourceWeft
- Open ZennoBrowser MCP Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
ZennoBrowser MCP Server — Antidetect Browser Automation for AI Agents
Control the ZennoBrowser antidetect browser from AI agents. Manage browser profiles, proxies, cookies, threads and browser instances from Claude Desktop, Cursor and VS Code through the Model Context Protocol (MCP).
[npm version] [license] [CI] [MCP compatible] [Node.js 20+]
Quick start · Installation · Tools · Example prompts · Troubleshooting
MCP (Model Context Protocol) server for ZennoBrowser Public API. Exposes browser automation and profile management capabilities to AI agents such as Claude Desktop, Cursor, and VS Code MCP clients.
Why ZennoBrowser MCP Server
- Full Public API coverage. 57 tools for workspaces, profiles, folders, proxies, threads, browser instances, presets, extensions and product info.
- Built for scale. Bulk tools create, update, start and stop many profiles, proxies, threads and browser instances in one call.
- Cookies and fingerprints. Import, export and copy cookies between profiles, and read full fingerprint details of any profile.
- Works with your AI client. Runs as a local stdio server in Claude Desktop, Cursor and VS Code.
- Free to start. ZennoBrowser is available for Windows. Its START plan includes unlimited local profiles and 2 simultaneous browsers.
Quick start
- Start ZennoBrowser on your computer and get an API token in your personal account on ZennoLab.
- Add the server to your MCP client using one of the configurations in Installation.
- Ask your agent, for example: "Create a new profile named "Test Profile", then start a browser instance for it."
Tools such as
delete_profile,bulk_delete_profileanddelete_proxycannot be undone. Review the agent's actions before approving destructive calls.
Requirements
- Node.js 20+
- ZennoBrowser running locally
- A valid ZennoBrowser API token
Installation
The package is published as
@zennolab/zennobrowser-mcp-server. Versions up to 1.0.0 were published as the unscopedzennobrowser-mcp-server, which no longer receives updates — replace it with@zennolab/zennobrowser-mcp-serverin your MCP client config.
npx (no install required)
Claude Desktop — edit claude_desktop_config.json:
Cursor — add to MCP settings (.cursor/mcp.json or Settings → MCP):
VS Code (with GitHub Copilot MCP support) — add to .vscode/mcp.json:
Global install
Then use zennobrowser-mcp-server as the command instead of npx ... @zennolab/zennobrowser-mcp-server:
Environment Variables
Tools
Workspaces
Profiles
Profile Folders
Proxies
Proxy Folders
Threads
Browser Instances
Presets & Extensions
Product
Example Prompts
Create a profile and start the browser:
Create a new profile named "Test Profile", then start a browser instance for it.
Full end-to-end flow:
Create a profile named "Scraper", create a proxy with URI "socks5://user:[email protected]:1080", assign the proxy to the profile, create a thread, then start a browser instance for the profile using that thread.
Bulk operations:
List all profiles in my default workspace and delete any that haven't been used in the last 30 days.
Cookie management:
Export cookies from profile "Session A" and import them into profile "Session B".
Troubleshooting
Error: Missing required environment variable ZB_API_TOKEN
Set the ZB_API_TOKEN environment variable to your ZennoBrowser API token.
Error: connect ECONNREFUSED 127.0.0.1:8160
ZennoBrowser is not running or the Public API is not working. If the API runs on a different port, set ZB_API_BASE_URL=http://localhost:<port>.
Tool calls return errors with "Unauthenticated"
Your API token is invalid or expired. Generate a new token in personal account on ZennoLab.
npx downloads the package every time
Install globally with npm install -g @zennolab/zennobrowser-mcp-server@latest to avoid re-downloading on each start.
Related
- ZennoBrowser — the antidetect browser this server controls
- ZennoLab documentation — product guides (in Russian)
- ZennoBrowser community forum — questions, bug reports and feature requests
- zennoposter-mcp — MCP servers for ZennoPoster and ZennoDroid
License
Source: README.md at commit ce8abc1
Tools
0Version history
1- v1.1.2LatestOct 9, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts