AI agents / Browz for Claude
Give Claude a browser of its own.
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. Claude browses in Browz instead of in your own browser: each task gets an isolated profile with its own fingerprint, proxy and cookies, sessions persist between chats, and you can take over the window at any time. Set it up in Claude Desktop or Claude Code in a minute. Claude.ai connects through the remote server, in beta. 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).
claude mcp add --transport stdio browz -- /Applications/Browz.app/Contents/Resources/browz-mcpBrowz for Claude
What your agent gets.
Claude Desktop
Double-click the Browz extension, or add one entry to claude_desktop_config.json. It starts the server inside Browz.
Desktop setup 02Claude Code
One claude mcp add command, over stdio on your computer, or remotely with a browser sign-in (beta).
Claude.ai
Add Browz as a custom connector, sign in with your Browz account and choose what Claude may do. Claude reaches the Browz on your computer, and your computer stays closed to the internet. In beta: tell us how it works for you from Settings › Help and support.
Connector setup 04Measured with Claude
In our published benchmark the same AI agent finished 46 of 50 public web tasks through Browz and 38 of 50 through a plain browser MCP server; on sites that challenge automated browsers it was 14 of 18 against 9 of 18.
See the benchmarkSetup
Working in minutes.
These are the same snippets as the setup docs and the Connect an AI agent screen in the app.
Install Browz and open it
Download Browz for Mac, Windows or Linux. Claude drives the profiles of that app.
Add Browz to Claude
Pick your Claude below. Claude Desktop and Claude Code start the server inside the app. Claude.ai connects through the remote server, in beta, and asks you to sign in.
Ask Claude
“Using Browz: create a new profile called agent-check, start it, open https://example.com, tell me the page title, take a screenshot, then stop the session and delete the profile.”
Install Browz, open it, and your agent can start: no account needed for local use. Keep the app open while your agent works; it can stay on its sign-in screen.
Claude Desktop Download the extension and double-click it, or drag it onto Settings › Extensions.
Claude Desktop config Add this to claude_desktop_config.json (Settings › Developer › Edit Config), then restart Claude (macos: ~/Library/Application Support/Claude/claude_desktop_config.json, windows: %APPDATA%\Claude\claude_desktop_config.json, linux: ~/.config/Claude/claude_desktop_config.json)
{
"mcpServers": {
"browz": {
"command": "/Applications/Browz.app/Contents/Resources/browz-mcp",
"args": []
}
}
}Claude Code Add Browz to Claude Code
claude mcp add --transport stdio browz -- /Applications/Browz.app/Contents/Resources/browz-mcpClaude Code, remote (beta) Add the remote server; Claude Code signs you in with your Browz account (run /mcp)
claude mcp add --transport http browz https://mcp.gobrowz.com/mcpClaude.ai connector (beta) Customize › Connectors › Add › Add custom connector, name it Browz, paste this URL, choose "Sign in now" and sign in with your Browz account
https://mcp.gobrowz.com/mcpThe snippets use the macOS path to the server inside Browz, /Applications/Browz.app/Contents/Resources/browz-mcp; on Windows and Linux the paths are in the setup docs. Give each agent its own key, limited to the profiles and sites it needs, and let it sign in without seeing the password. The remote MCP server for hosted agents is in Beta: free for every account, Free included, within the beta allowance, and it needs the Browz app open with Remote control on, on a computer with a hardware security chip. See what it needs and its allowance. Use agents only where each site’s terms allow it: our acceptable use policy applies to agents the same as to people.
FAQ
About Browz for Claude.
Does Claude see my own browser or passwords?
No. Claude works only in Browz profiles, each a separate browser with its own cookies and storage. When a site asks for a password or a code, you enter it yourself in the profile’s window. Or store the sign-in in Browz and let Claude use it without seeing it: Browz types the password and code itself, only on the sites you allowed. How.
Which Claude plans work?
Claude Desktop and Claude Code run the local server on your computer. Claude.ai custom connectors, through our remote server in beta, depend on your Claude plan; see Anthropic’s documentation for which plans offer them.
Is the Claude Desktop extension safe to install?
It is a small bundle (browz.mcpb) that starts the MCP server already inside Browz, so Browz has to be installed and open.
More for agent builders
Other guides.
Browz for AI agents
Everything an agent gets in Browz.
OverviewAnti-detect browser for AI agents
One consistent device, its own proxy and cookies for every agent task.
Read moreMCP browser
What the Browz MCP server gives any MCP client, local or remote.
Read moreBrowz for Cursor
An isolated browser for Cursor’s agent, from one config entry.
Read more