Integrations / AI agent clients / n8n
A browser for n8n AI agents.
n8n’s AI Agent node takes tools from MCP servers through the MCP Client Tool node, which speaks HTTP, not stdio. Run the Browz server over HTTP on the same computer and the workflow’s agent can browse in isolated profiles.
npx -y @browz/mcp --httpSetup
Set it up.
Install Browz and open it
Download Browz on the computer that runs n8n.
Start the server over HTTP
It listens on 127.0.0.1 only and creates a bearer token file the first time; it prints only the file’s path.
Terminalnpx -y @browz/mcp --httpCopy the token
The token is in the Browz data folder. Copy it into an n8n credential, not into the workflow itself.
Terminalcat ~/.browz/mcp-http-tokenAdd the MCP Client Tool node
Attach an MCP Client Tool node to your AI Agent node. Set the endpoint to
http://127.0.0.1:50334/mcp, the server transport to HTTP Streamable, authentication to Bearer with a new credential holding the token, and choose which tools to include.Or use the hosted server (beta)
For n8n in the cloud or in a container, use
https://mcp.gobrowz.com/mcpas the endpoint with authentication MCP OAuth2, or Bearer with an agent token from your account page. Through the hosted server the agent works with profiles directly:browz_profile_create,browz_profile_start,browz_profile_stopandbrowz_profile_delete.
Node fields from MCP Client Tool node, the n8n repository.
Example
A scheduled page check.
A Schedule Trigger, an AI Agent node with a chat model, and the MCP Client Tool limited to the tools below. Give the agent this as its prompt.
browz_session_open
browz_navigate
browz_snapshot
browz_screenshot
browz_session_closeOpen a throwaway Browz session for "status check", go to https://status.example.com, read the page with a snapshot and reply with the overall status line only. Always close the session at the end.Good to know
Notes and tips.
- The local HTTP server answers requests addressed to localhost, 127.0.0.1 or [::1], so run n8n directly on the computer with Browz rather than in Docker, or use the hosted server.
- The bearer token in
mcp-http-tokengives full access to your Browz. Keep it in an n8n credential, or give the server a local agent key with narrower scopes instead. - The remote server at
https://mcp.gobrowz.com/mcpis in free public beta: it needs the Browz app open with Remote control on, on a computer with a hardware security chip, and offers the profile, tab and page tools. See what it needs and what it offers. - Browz has to be installed and open on the same computer: the local MCP server drives the app’s own profiles through its local API, and reads the app’s credentials itself, so no token goes in the config.
- A person completes sign-ins, 2FA codes and CAPTCHAs. The agent can pause with
browz_request_humanand hand you the profile’s window, then carry on in the same session. Browz never solves or bypasses CAPTCHAs. - Use agents only where each site’s terms allow automated use, on accounts you are entitled to use. Our acceptable use policy applies to agents the same as to people.
- The MCP server is on every plan, Free included (5 profiles). How many agent sessions can be open at once depends on the plan: see pricing.
FAQ
n8n and Browz.
Why not stdio, like other clients?
n8n’s MCP Client Tool node connects to MCP servers over HTTP only (Streamable HTTP, or the older SSE). The Browz server serves Streamable HTTP on loopback with --http.
Does the server have to keep running?
Yes, while workflows use it. Run it in a terminal you leave open, or as a service; it needs the Browz app open too.
Can I change the port?
Yes: npx -y @browz/mcp --http --port 50400, then use that port in the endpoint.
Get started
Download Browz. Every task, its own browser.
curl -fsSL https://gobrowz.com/agents/install.sh | sh