Auto Browser MCP
MCP gives an agent a Playwright browser where a person can take over the same session and save an authentication profile
- 922 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The agent can submit forms and change data as the signed-in user
- Saved authentication state grants account access
- The shared noVNC desktop can expose other sessions’ windows
Install
- Works in
Manual install
git clone https://github.com/LvcidPsyche/auto-browser.git
cd auto-browser
docker compose up --buildStarts the local controller and browser; published ports default to loopback.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent can submit forms and change data as the signed-in user
- Saved authentication state grants account access
- The shared noVNC desktop can expose other sessions’ windows
This is third-party code. Review the repository files before installing.
What it does
Auto Browser gives an agent a managed Chromium session through MCP. The agent opens pages, reads structure and performs interface actions. Screenshots help check its location and the result of an action. A person can open the same session through noVNC and continue manually. This supports signing in to your own account or recovering a workflow after failure. Authentication state can be saved as a named profile for a later session. Docker Compose starts the controller and browser together. HTTP MCP clients connect directly, while a stdio bridge serves other clients. Settings select tool profiles and action approvals; review them before connecting a work account.
Who it is for. Web-service testers sharing control of one browser session between an agent and a person.
Good fit when
- You want to sign into a test account manually before delegating later steps
- A site workflow breaks and a person needs to continue the same session
- Tests need fresh browser sessions with saved authentication state
- You want to observe agent activity and review approvals in a dashboard
Not a fit when
- You only need page text without a controlled browser
- Users need isolation but you cannot configure separate session containers
- You cannot entrust the service with account authentication state
Example request
Open the test site through Auto Browser. Let me sign in manually, then read the order list without changing data and show a result screenshot.MCP
- Transport
- http, stdio
- Authentication
- not required
Environment variables
AUTO_BROWSER_BASE_URL- Controller address for the stdio bridge; local default is http://127.0.0.1:8000.
AUTO_BROWSER_BEARER_TOKENsecret- Protected controller token used by the stdio bridge.
Limitations
Docker and Compose are required; prebuilts target linux/amd64, so inspect source builds for other environments. Ordinary mode separates session storage but shares Chromium and the noVNC desktop, allowing a person to see other sessions’ windows. Choose separate container mode for different users. Domain restrictions do not cover every iframe or third-party resource, so they do not provide complete browser network isolation.
How to disable. Close active browser sessions, remove the client MCP connection and run `docker compose down` in the project directory. Inspect saved profiles and logs separately under `data/`. Revoke exposed controller credentials and site sessions with the relevant services.
FAQ
How do I start Auto Browser locally?
Clone the repository and run `docker compose up --build`. The controller and browser must be running before the MCP client connects.
How do I connect Claude Code or Codex?
Use the HTTP connection commands below. Both use `http://127.0.0.1:8000/mcp`; the default local mode needs no separate server token.
Is `uvx auto-browser-mcp` enough?
No. It starts a stdio bridge to the controller. The Auto Browser stack must already run; set `AUTO_BROWSER_BASE_URL` for a non-default address.
Does every action require approval?
That depends on controller and client settings. Test the approval policy safely. Human takeover support does not mean every click requires confirmation.
Can the service be reached from another machine?
Yes, after configuring a protected deployment. Tokens and operator identity are needed, and saved authentication state needs protection. Local defaults are unsuitable for public exposure.
What license and model costs apply?
Code uses MIT; the chosen model has separate usage costs.
Discussion
No questions or reviews yet.
Related
MCP serversAn MCP server and Chrome extension that let the agent drive your already open browser with your logged-in sessions, all locally
An MCP server that lets an agent drive a real browser: open pages, click and fill forms through Playwright
An MCP server that drives your already open Chrome and stops to ask you about a 2FA code, a CAPTCHA, or a choice only you can make
Browserless.io MCP server: a cloud browser for the agent with page reads, site crawls, Lighthouse audits and click-driven sessions
MCP Server Playwright by Automata Labs
MCP Server Playwright
Playwright-based MCP server for browsing sites, clicking, filling forms, taking screenshots and running JavaScript in a browser
A separate browser for agents with a skill and MCP: Claude Code and Codex work in your logged-in accounts, and every session is recorded for replay
README in short
The project includes a browser node and controller. MCP profiles select tool sets, with detailed diagnostics outside the ordinary profile.