Integrations / AI agent clients
A browser for every agent client.
You decide exactly what each agent may do: its own key, its own profiles, only the sites you allow, sign-ins it can use on your computer but never read, and a person for the login. Browz ships with an MCP server: add it to the agent you use and every task gets its own isolated browser profile, with its own fingerprint, proxy and cookies. Underneath, every profile’s fingerprint is set in the browser engine itself, not by a script on top, and you can test it yourself (engine-level vs injected scripts). Each guide has the exact config or command for that client.
{
"mcpServers": {
"browz": {
"command": "/Applications/Browz.app/Contents/Resources/browz-mcp",
"args": []
}
}
}AI agent clients
Pick your client.
Apps and editors first, then agent frameworks.
Claude Code
One command adds Browz to Claude Code, for you or for the whole project.
Read the guideClaude Desktop
A double-click extension, or one entry in claude_desktop_config.json.
Read the guideVS Code (Copilot agent mode)
One code --add-mcp command, or an entry in the workspace MCP config.
Read the guideGemini CLI
gemini mcp add, or one entry in ~/.gemini/settings.json.
Read the guideWindsurf (Cascade)
One mcpServers entry in Cascade’s MCP config file.
Read the guideZed
A context_servers entry in Zed’s settings.json.
Read the guideCline
An entry in cline_mcp_settings.json, with tool approval kept on.
Read the guideGoose
A stdio extension, added with goose configure or in config.yaml.
Read the guideCodex CLI
codex mcp add, or an [mcp_servers.browz] table in config.toml.
Read the guideLangChain
langchain-mcp-adapters loads the Browz tools into a LangChain agent.
Read the guideLangGraph
A LangGraph agent with the Browz tools, in one MCP session per run.
Read the guideCrewAI
Hand the Browz MCP tools to a CrewAI agent with one adapter.
Read the guideAutoGen
McpWorkbench hands the Browz tools to an AutoGen AssistantAgent.
Read the guiden8n
The MCP Client Tool node, over HTTP to a local Browz server.
Read the guideCursor
One-click install or one mcp.json entry for Cursor’s agent.
Read the guideOpenAI Agents SDK
The Agents SDK on your computer, or the Responses API through the hosted server (beta).
Read the guideClaude, all apps
Claude Desktop, Claude Code and Claude.ai on one page.
Read the guideAny MCP client
What the Browz MCP server offers any client, and its tools.
See the toolsSign-ins the agent never sees
Let any of these agents log in with a password and code you stored, without the agent, its logs or the model provider ever seeing them.
How it worksHow it works
Three steps, whichever client.
Install Browz and open it
Install Browz, open it, and your agent can start: no account needed for local use. The MCP server is inside the app and works through the app’s own local API, so there is nothing to paste. Keep the app open while your agent works; it can stay on its sign-in screen.
Register the server
Point the client at the server inside Browz,
/Applications/Browz.app/Contents/Resources/browz-mcpon a Mac, or atnpx -y @browz/mcp. Clients in the cloud use the hosted server instead, in beta.Ask for a task
The agent opens a session, which gives the task its own profile: throwaway, or a returning identity that keeps its sign-in.
FAQ
About ai agent clients.
My client is not listed. Will it work?
Probably. Any client that can start a local MCP server over stdio can use Browz with the same command; clients that speak only HTTP can use npx -y @browz/mcp --http on loopback. See the setup docs.
Do these guides need an account or a paid plan?
No. Install Browz, open it, and your agent can start: no account needed for local use. A Browz account adds sync across your computers, teams, Remote control with the hosted MCP server for agents that run in the cloud, and agent tokens for them. The MCP server is on every plan, Free included, with 5 profiles. Paid plans add profiles and more agent sessions at once.
Does the agent see my own browser?
No. It works only in Browz profiles, each a separate browser with its own cookies and storage.
More integrations
Other families.
Automation libraries
Attach Playwright, Puppeteer, Selenium and agent frameworks to Browz profiles over CDP or drive them through the local API.
See the guidesProxy setups
Give each profile the right exit: residential, mobile, datacenter, SOCKS5, rotating or sticky, from any provider.
See the guidesAll integrations
Every guide on one page.
See allGet started
Download Browz. Every task, its own browser.
curl -fsSL https://gobrowz.com/agents/install.sh | sh