Share over HTTP
By default each MCP client launches its own BrowserControl over stdio. To let several clients or agents share one browser, start the server yourself and serve it over Streamable HTTP.
Start the server
uvx browsercontrol --transport httpIt listens on http://127.0.0.1:8000/mcp. Change the address with --host and --port, or with BROWSER_HOST and BROWSER_PORT. --transport sse serves the older SSE transport for clients that still need it.
Point clients at it
claude mcp add --transport http browsercontrol http://127.0.0.1:8000/mcp{
"mcpServers": {
"browsercontrol": {
"url": "http://127.0.0.1:8000/mcp"
}
}
}Clients differ in how they name URL-based servers (url, serverUrl, or a type: "http" field). Check your client's MCP docs if the entry above isn't recognized.
Shared or isolated
Every connected client drives the same browser, but each keeps its own choice of session. One agent calling switch_session doesn't move another.
To keep clients fully apart, give each its own isolated session automatically:
uvx browsercontrol --transport http --isolate-clientsWith --isolate-clients (or BROWSER_ISOLATE_CLIENTS=true), each client gets a fresh in-memory session on its first tool call: separate cookies, tabs, captured traffic, mocks, and action log. Use it when agents work in parallel and must not see each other's logins.
Security
There is no authentication
Anyone who can reach the port controls the browser, including every site it is signed in to. Keep the default 127.0.0.1 host. BrowserControl logs a warning if you bind to any other address.
If you do need remote access, put it behind something that authenticates, such as an SSH tunnel (ssh -L 8000:127.0.0.1:8000 host) or a reverse proxy with auth.
