Introduction
MZBase is a desktop app for people who run many accounts. Every account gets its own browser profile with its own fingerprint, proxy and data, and the work on those accounts is automated with workflows and AI agents. It runs on Windows first; macOS and Linux come later.
The building blocks
Section titled “The building blocks”| Part | What it does |
|---|---|
| Profiles | An isolated browser: its own data folder, cookies, proxy, fingerprint and settings. See Profiles. |
| MZBrowser | Our own Chromium-based engine. A profile runs as a composed Persona or as the Real machine. |
| Proxies | HTTP and SOCKS5 proxies, providers, Change IP, IPv6 from your own line, and a proxy router with pools. See Proxies. |
| Workflows | A canvas of nodes that drives profiles, accounts, mail, SMS, files, AI and apps. See Workflows. |
| AI agents | Claude Code and Codex in the agent hub, your own API keys through the AI gateway, and local models on your GPU. |
| Phones | Android phones on your PC or your own Linux server, each with its own device identity (early preview). |
| Team server | A server you host on Cloudflare or Docker for members, sharing, locks and sync. See Team server. |
| Local API | An HTTP API, a CLI (mzb) and an MCP server on 127.0.0.1 for your own tools. See Local API. |
Local first
Section titled “Local first”- On one computer, MZBase needs no server and no account to use. Profiles live in the app’s data folder.
- A team server is a connection you add: it stores the team’s accounts, profile metadata and locks, and profile bundles go to your own storage bucket, encrypted.
- MZBase’s own servers handle only your MZBase account, licenses, downloads and updates. They never receive profiles, cookies, passwords or workflows.
One capability layer
Section titled “One capability layer”Every action in MZBase is defined once in the app’s core and used everywhere it fits:
- as a workflow node on the canvas;
- as a tool for AI agents and over MCP;
- as a
mzbcommand and a Local API call.
So an agent can do what a workflow does, under the same permissions, and a workflow you build can be started from your own scripts.
- Getting started: install the app and open your first profile.
- Node reference: every workflow node with its parameters.