Integrations
Browz with the tools you already use.
Every Browz profile is an isolated browser with its own fingerprint, proxy and cookies. These guides show how to drive one from your AI agent, your automation library or your proxy provider, with the exact config and code for each.
AI agent clients
Pick your client.
Add the Browz MCP server to the agent you already use, so each task gets its own isolated browser profile.
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 worksAutomation libraries
Pick your library.
Attach Playwright, Puppeteer, Selenium and agent frameworks to Browz profiles over CDP or drive them through the local API.
Playwright
connectOverCDP to a Browz profile: its own cookies, fingerprint and proxy.
Read the guidePlaywright for Python
connect_over_cdp from Python, with a profile that keeps its sign-in.
Read the guidePuppeteer
puppeteer.connect to a running profile; disconnect, never close.
Read the guideSelenium
ChromeDriver attaches with debuggerAddress; match its major version.
Read the guidebrowser-use
Hand browser-use a Browz profile’s CDP URL instead of its own browser.
Read the guideStagehand
Stagehand 3 attaches to a Browz profile with cdpUrl.
Read the guideRaw CDP
Plain WebSocket and fetch to a profile’s DevTools endpoint, no library.
Read the guideLocal REST API
Create, start, navigate, screenshot and stop profiles with curl.
Read the guidebrowz CLI
Create, start and stop profiles from a shell script.
Read the guideProxy setups
Pick your setup.
Give each profile the right exit: residential, mobile, datacenter, SOCKS5, rotating or sticky, from any provider.
Residential proxies
One residential exit per profile, with timezone and language that follow it.
Read the guideMobile proxies
Save the provider’s change-IP link; Browz verifies the new exit.
Read the guideDatacenter and static proxies
Static exits matched one to one, with launch guards on.
Read the guideSOCKS5 proxies
SOCKS5 with or without a login, DNS resolved at the proxy.
Read the guideHTTP and HTTPS proxies
HTTP and HTTPS proxies, and what each check error means.
Read the guideA proxy per profile
Give every profile its own exit, by hand, by policy or from a script.
Read the guideRotating vs sticky proxies
When each fits, and how Browz treats each.
Read the guideProxies for AI agents
Each agent session on its own pool proxy, kept for returning identities.
Read the guideDNS and WebRTC with a proxy
Keep DNS, WebRTC, timezone and language in line with the exit.
Read the guideLooking for the reference instead? The developer quickstart covers the local API, CLI and SDKs, the AI agent setup docs cover every MCP client, and llms.txt is the starting point for agents. Want an agent to log in without ever seeing the password? See AI agent login without sharing the password. Still choosing a browser? See ten browsers for AI agents compared and engine-level vs injected-script fingerprint protection. Use Browz only where each site’s terms allow it; our acceptable use policy applies to scripts and agents the same as to people.
Get started
Download Browz. Every task, its own browser.
curl -fsSL https://gobrowz.com/agents/install.sh | sh