Skip to content
Back to search

multizen-browser

Anti-detect browser for AI agents and human operators. Isolated Chromium profiles (cookies, fingerprint, proxy), driven through MCP.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/multizenteam--multizen-browser/badge.svg)](/listings/multizenteam--multizen-browser)

HTML

<a href="/listings/multizenteam--multizen-browser"><img src="/api/listings/multizenteam--multizen-browser/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

These steps run a script from the network that findsafeskills does not scan.

macOS

The cleanest path. Homebrew handles the Gatekeeper quarantine for you:

brew tap multizenteam/multizen
brew install --cask multizen

Or grab the DMG straight from the [releases page](https://github.com/multizenteam/multizen-browser/releases/latest) and run this once after install to bypass the unsigned-app warning:

xattr -cr /Applications/MultiZen.app

Linux

curl -LO https://github.com/multizenteam/multizen-browser/releases/latest/download/MultiZen-linux-x86_64.AppImage
chmod +x MultiZen-linux-x86_64.AppImage
./MultiZen-linux-x86_64.AppImage

Some distros need `libfuse2` (`apt install libfuse2t64` on Ubuntu 24.04+). If Chromium's sandbox refuses to start, add `--no-sandbox`.

Windows

Download [MultiZen-win-x64.exe](https://github.com/multizenteam/multizen-browser/releases/latest/download/MultiZen-win-x64.exe). SmartScreen may flag the installer as unrecognized on first download. Click **More info**, then **Run anyway**.

One-liner installer

For macOS and Linux:

curl -sSL https://getmultizen.com/install.sh | bash

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 273 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <div align="center">
  2. <img src=".github/assets/logo.png" width="96" height="96" alt="MultiZen" />
  3. <h1>MultiZen</h1>
  4. <p><strong>A browser library for AI agents and human operators.</strong></p>
  5. <p>
  6. Local Chromium profiles with their own cookies, fingerprint, and proxy.<br/>
  7. Drive them through MCP from Cursor, Claude Desktop, or any MCP client.
  8. </p>
  9. <p>
  10. <a href="https://github.com/multizenteam/multizen-browser/releases/latest"><img alt="Latest release" src="https://img.shields.io/github/v/release/multizenteam/multizen-browser?style=for-the-badge&color=8b5cf6&labelColor=0a0b0f"></a>
  11. <a href="https://github.com/multizenteam/multizen-browser/blob/master/LICENSE"><img alt="MIT License" src="https://img.shields.io/github/license/multizenteam/multizen-browser?style=for-the-badge&color=ec4899&labelColor=0a0b0f"></a>
  12. <a href="https://github.com/multizenteam/multizen-browser/actions/workflows/release.yml"><img alt="Build" src="https://img.shields.io/github/actions/workflow/status/multizenteam/multizen-browser/release.yml?style=for-the-badge&labelColor=0a0b0f"></a>
  13. <a href="https://github.com/multizenteam/multizen-browser/releases"><img alt="Downloads" src="https://img.shields.io/github/downloads/multizenteam/multizen-browser/total?style=for-the-badge&color=3b82f6&labelColor=0a0b0f"></a>
  14. <a href="https://github.com/multizenteam/multizen-browser/stargazers"><img alt="Stars" src="https://img.shields.io/github/stars/multizenteam/multizen-browser?style=for-the-badge&color=ff6b35&labelColor=0a0b0f"></a>
  15. <a href="https://discord.gg/pd6MhzPbJ3"><img alt="Discord" src="https://img.shields.io/badge/discord-join-5865f2?style=for-the-badge&labelColor=0a0b0f"></a>
  16. </p>
  17. <p>
  18. <a href="https://getmultizen.com"><strong>getmultizen.com</strong></a>
  19. &nbsp;·&nbsp;
  20. <a href="https://github.com/multizenteam/multizen-browser/releases/latest">Download</a>
  21. &nbsp;·&nbsp;
  22. <a href="https://discord.gg/pd6MhzPbJ3">Discord</a>
  23. </p>
  24. <p>
  25. <sub>PROXY PARTNER</sub>
  26. <br/>
  27. <a href="https://dashboard.thordata.com/register?invitation_code=E8XWP3FP">
  28. <picture>
  29. <source media="(prefers-color-scheme: dark)" srcset=".github/assets/thordata-logo-dark.svg" />
  30. <img src=".github/assets/thordata-logo.svg" alt="Thordata" height="24" />
  31. </picture>
  32. </a>
  33. <br/>
  34. <sub>Residential + ISP proxies · 10% off with <code>MULTIZEN10</code></sub>
  35. </p>
  36. <br/>
  37. <img src=".github/assets/profiles-list.jpg" alt="MultiZen profile library with platform, proxy country, and AI-activity indicators" width="100%" />
  38. <br/><br/>
  39. </div>
  40. ## What it is
  41. MultiZen is a desktop app that runs a library of isolated browser profiles. Each profile has its own cookies, login state, fingerprint, and proxy, and runs on your choice of engine — CloakBrowser (Chromium) or Camoufox (Firefox). A local MCP server on `127.0.0.1:7777` exposes browser-drive tools (navigate, click, type, extract, screenshot, evaluate JS, cookies, tabs, waits) to any MCP client.
  42. The result: your AI agent in Cursor or Claude Desktop can complete real authenticated workflows. Cookies and session state survive between launches, so logins and context carry over across AI sessions.
  43. ## Install
  44. ### macOS
  45. The cleanest path. Homebrew handles the Gatekeeper quarantine for you:
  46. ```sh
  47. brew tap multizenteam/multizen
  48. brew install --cask multizen
  49. ```
  50. Or grab the DMG straight from the [releases page](https://github.com/multizenteam/multizen-browser/releases/latest) and run this once after install to bypass the unsigned-app warning:
  51. ```sh
  52. xattr -cr /Applications/MultiZen.app
  53. ```
  54. ### Linux
  55. ```sh
  56. curl -LO https://github.com/multizenteam/multizen-browser/releases/latest/download/MultiZen-linux-x86_64.AppImage
  57. chmod +x MultiZen-linux-x86_64.AppImage
  58. ./MultiZen-linux-x86_64.AppImage
  59. ```
  60. Some distros need `libfuse2` (`apt install libfuse2t64` on Ubuntu 24.04+).
  61. On Ubuntu 24.04+ (and other kernels that restrict unprivileged user namespaces) the browser's sandbox is blocked by default. On the first affected launch MultiZen offers a one-time **secure setup**: it installs a small AppArmor profile that re-permits the sandbox for just this browser (one password prompt). The sandbox then stays on with no warning banner. You can also run or re-run it later from Settings. If you decline or it can't run, MultiZen launches the browser without the sandbox so it still works.
  62. Prefer to do it by hand? Settings shows the exact command; it writes `/etc/apparmor.d/multizen-cloakbrowser` and loads it with `apparmor_parser`. To force sandbox-off regardless, launch the AppImage with `--no-sandbox`.
  63. ### Windows
  64. Download [MultiZen-win-x64.exe](https://github.com/multizenteam/multizen-browser/releases/latest/download/MultiZen-win-x64.exe). SmartScreen may flag the installer as unrecognized on first download. Click **More info**, then **Run anyway**.
  65. ### One-liner installer
  66. For macOS and Linux:
  67. ```sh
  68. curl -sSL https://getmultizen.com/install.sh | bash
  69. ```
  70. ## How it works
  71. ```
  72. +----------------------+ +-----------------------+
  73. | Cursor / Claude | MCP | MultiZen Desktop App |
  74. | Desktop / Cline | <-----> | 127.0.0.1:7777 |
  75. +----------------------+ +-----------+-----------+
  76. |
  77. | spawn / drive (CDP)
  78. v
  79. +--------------+--------------+
  80. | Profile A | Profile B | ...
  81. | cookies | cookies |
  82. | proxy LU | proxy US |
  83. | Win 145 | macOS 145 |
  84. +-------------+--------------+
  85. |
  86. v
  87. patched Chromium binary
  88. (canvas, WebGL, audio,
  89. font, WebRTC fingerprints
  90. spoofed at C++ level)
  91. ```
  92. Each profile is a real Chromium window with persistent state on disk. The MCP server speaks the standard Anthropic Model Context Protocol over Streamable HTTP (plus legacy SSE) so it works with any client. Browser-drive tools call into Chrome DevTools Protocol under the hood.
  93. ## Features
  94. | | What it does |
  95. | --- | --- |
  96. | **MCP server** | Native localhost endpoint. Works with Cursor, Claude Desktop, Cline, Continue, anything else that speaks MCP. |
  97. | **Per-profile engine** | Choose each profile's browser: **CloakBrowser** (Chromium) or **Camoufox** (Firefox-based, for a genuinely non-Chrome TLS/JS fingerprint). |
  98. | **Anti-detect Chromium** | Source-patched browser engine (CloakBrowser). Canvas, WebGL, audio, fonts, WebRTC IP all spoofed at C++ level instead of JS injection. |
  99. | **Persistent state** | Cookies, login, IndexedDB, localStorage stay per-profile across launches and across AI sessions. |
  100. | **Cross-platform persona** | Run a Windows persona on a Mac host (or vice versa). C++ patches keep the fingerprint coherent across V8, Blink, and CSS feature signatures. |
  101. | **Proxy + persona alignment** | Per-profile HTTP or SOCKS5 proxy with a local SOCKS5 bridge so DNS resolution stays remote. Auto-aligns timezone, locale, and `navigator.geolocation` to the proxy egress IP. |
  102. | **Self-hosted** | Profiles live on your disk in plain SQLite plus Chromium user-data-dir format. No account, no license server, no telemetry. |
  103. | **Open source** | MIT for the entire app, MCP server, and CDP driver. Patched Chromium engine is also open source. |
  104. ## Onboarding
  105. <div align="center">
  106. <img src=".github/assets/firstrun.jpg" alt="MultiZen first-run onboarding" width="85%" />
  107. </div>
  108. ## Connect an agent (Codex, Cursor, Claude Desktop)
  109. After installing, the MCP server starts on `127.0.0.1:7777`. It serves the current
  110. **Streamable HTTP** transport at `http://127.0.0.1:7777/mcp` (plus a legacy HTTP+SSE
  111. endpoint at `/sse` for older clients).
  112. The server requires a **bearer token** — it is generated on first run and shown in
  113. the app under **MCP → Connect an agent** (also written to the `mcp-token` file in
  114. the app data directory). Every client config below must send it as
  115. `Authorization: Bearer <token>`. Replace `<token>` with your own. The app's MCP
  116. panel has a **Copy for LLM** button that hands the whole setup (token included) to
  117. a coding agent if you'd rather not edit config files by hand.
  118. **Codex CLI** (`~/.codex/config.toml`) — connects to Streamable HTTP directly:
  119. ```toml
  120. [mcp_servers.multizen]
  121. url = "http://127.0.0.1:7777/mcp"
  122. http_headers = { Authorization = "Bearer <token>" }
  123. ```
  124. **JSON URL clients — Cursor** (`~/.cursor/mcp.json`), Cline, Continue:
  125. ```json
  126. {
  127. "mcpServers": {
  128. "multizen": {
  129. "url": "http://127.0.0.1:7777/mcp",
  130. "headers": { "Authorization": "Bearer <token>" }
  131. }
  132. }
  133. }
  134. ```
  135. **Claude Desktop** (`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS)
  136. — its config has no `url` field, so bridge the endpoint through
  137. [`mcp-remote`](https://www.npmjs.com/package/mcp-remote) (needs Node):
  138. ```json
  139. {
  140. "mcpServers": {
  141. "multizen": {
  142. "command": "npx",
  143. "args": ["mcp-remote", "http://127.0.0.1:7777/mcp", "--header", "Authorization: Bearer <token>"]
  144. }
  145. }
  146. }
  147. ```
  148. Restart your client. The agent now has the full tool set — profile lifecycle (`list_profiles`, `launch_profile`, `close_profile`), page driving (`navigate`, `click`, `type`, `extract`, `screenshot`, `evaluate_js`), tabs (`list_tabs`, `new_tab`, `activate_tab`, `close_tab`), cookies (`get_cookies`, `set_cookies`), waits (`wait_for_load`, `wait_for_navigation`, `wait_for_selector`), and raw `cdp_send`.
  149. ## Stack
  150. | Layer | Tech |
  151. | --- | --- |
  152. | Desktop shell | Electron 33 |
  153. | Renderer | React 19, Tailwind v4, TypeScript strict |
  154. | Main process | TypeScript ESM, electron-vite, native MCP SDK |
  155. | MCP server | `@modelcontextprotocol/sdk` over Streamable HTTP + SSE |
  156. | Profile storage | better-sqlite3 with idempotent migrations |
  157. | Browser driver | chrome-remote-interface over CDP (Chromium); playwright-core (Firefox) |
  158. | Browser engine | CloakBrowser (patched Chromium) or Camoufox (Firefox), per profile |
  159. | Build | Yarn 4 workspaces, electron-vite, electron-builder |
  160. | CI | GitHub Actions matrix on macOS, Windows, Linux |
  161. ## Develop
  162. ```sh
  163. git clone https://github.com/multizenteam/multizen-browser
  164. cd multizen-browser
  165. yarn install
  166. yarn dev # launch the desktop app in dev mode
  167. yarn mcp:dev # run the MCP server standalone for testing
  168. yarn typecheck # strict TS across all workspaces
  169. yarn build # full release build (mac/win/linux per OS)
  170. ```
  171. Requires Node 22+ and Yarn 4 (via Corepack).
  172. ## Repo layout
  173. ```
  174. apps/
  175. desktop/ Electron + React + Tailwind GUI + main process
  176. packages/
  177. mcp-server/ MCP server exposing the browser-drive tools
  178. cdp-driver/ Thin wrapper around chrome-remote-interface
  179. profile-manager/ SQLite profile CRUD + encrypted local storage
  180. settings-store/ App-level settings persistence
  181. types/ Shared TypeScript types
  182. .github/
  183. workflows/release.yml Matrix build, tag-triggered
  184. ```
  185. ## Roadmap
  186. Things landing in upcoming releases.
  187. - **Behavioral injection**: humanized mouse paths, keystroke timing, scroll jitter applied at the CDP input layer.
  188. - **Per-profile cloud sync** (opt-in, end-to-end encrypted): so the same profile follows you across laptops.
  189. - **Team workspaces**: shared profile pool with audit log.
  190. ## Why MultiZen vs the alternatives
  191. | | MultiZen | Browserbase / Hyperbrowser | GoLogin / AdsPower / Multilogin |
  192. | --- | :---: | :---: | :---: |
  193. | Native MCP server | yes | yes | profile CRUD only |
  194. | Drives the browser through MCP | yes | yes | no |
  195. | Anti-detect at C++ level | yes | partial | yes |
  196. | Persistent login across sessions | yes | per-session | yes |
  197. | Self-hosted | yes | no | no |
  198. | Manual GUI for operators | yes | no | yes |
  199. | Pay per browser-hour | no | yes | varies |
  200. | Open source core | yes | SDK only | no |
  201. ## Acceptable use
  202. Building a multi-account browser is dual-use. We support QA testing across roles and regions, agency workflows you are authorized to run, market research, multi-marketplace e-commerce ops, AI-driven sales engineering, and personal accounts you legitimately own. We do not support platform ToS violations, mass account farming, ban evasion, or fraud. Full policy at [getmultizen.com/acceptable-use](https://getmultizen.com/acceptable-use).
  203. ## License
  204. [MIT](LICENSE). Use it however you want.
  205. <div align="center">
  206. <br/>
  207. <sub>
  208. Built in transit by <a href="https://github.com/oboshto">@oboshto</a>.<br/>
  209. Star this repo if MultiZen is useful, it helps a lot.
  210. </sub>
  211. </div>

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.