Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Background Browser MCP open my saved website and check that I'm signed in"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Give Codex and, optionally, ChatGPT access to a separate signed-in browser on your Windows PC. Routine browsing runs headless. You sign in directly on each website once, then reuse the saved session through MCP.
The project uses Playwright MCP, a local setup dashboard, a persistent Chrome profile, and recovery supervisors. It does not call a model API or require an OpenAI API key. ChatGPT access optionally uses an authenticated OAuth gateway and your own ngrok account.
On Windows, install Node.js 22 or newer and Google Chrome. Node.js 24 LTS and Windows 11 are recommended. Have your usual Codex client available.
Download this repository with Code → Download ZIP, extract it, and open PowerShell in the extracted folder.
Run:
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\install.ps1Open the generated Open browser setup.url shortcut in your installation folder. The default installation is %USERPROFILE%\.background-browser.
Add a website, select Sign in, and complete its password, SSO, or MFA prompts directly in the separate login window. Return to the dashboard and select Save session & return to background.
Add this server to Codex as Streamable HTTP, then restart/reload its MCP connection:
http://127.0.0.1:8933/mcpAsk Codex: “Use my background browser to open the website I saved and verify that I am signed in.” A saved website card or a healthy service does not establish that its account session works.
Full Windows setup · Codex connection · Optional ChatGPT connection
Related MCP server: Browser MCP
Your separate profile and session handoff live under the installation folder. This browser does not reuse your personal Chrome profile. Login windows appear only when you start the sign-in flow; ordinary tool calls use headless Chrome. Saved sessions can expire or be invalidated by the website.
The login window starts installed Chrome directly and connects through Chrome's supported debugging interface. Websites can still restrict automated access; this project does not guarantee sign-in to every Google product or other site. See login troubleshooting.
The private dashboard shortcut contains a local access token. The optional OAuth gateway has a separate owner passphrase. Keep both, your ngrok authtoken, browser data, and OAuth state off GitHub and out of chat messages. Each friend installs their own runtime and signs into their own accounts. Sharing this source does not share the author's browser, app, or accounts.
The local browser components have no project service fee. Optional remote access can fit within ngrok's current free plan, which has an assigned development domain and usage caps. This is not a promise that third-party services, subscriptions, or limits will remain free forever. See ngrok's current free-plan limits.
Your Codex/ChatGPT account, available features, workspace policy, and usage limits remain separate. In particular, this project cannot grant access to custom MCP plugins if your ChatGPT account does not have it. The official custom MCP guide describes the web setup and applicable restrictions.
The PC must be awake, signed in, and connected to the internet for remote use. Recovery restarts failed components; it cannot browse while the PC is off, restore an expired website login, or guarantee recovery from every live-but-unresponsive process.
Folder | Purpose |
| Browser manager, manual login helper, dashboard, OAuth gateway, and recovery sources |
| Fresh Windows installation and management |
| Generic local plugin source and account-browsing skill; no registered app binding |
| Setup, architecture, privacy, and example configuration |
The installer does not overwrite your Codex configuration. You can use the direct MCP connection or the optional local plugin template. The repository is source distribution; it is not an OpenAI plugin-store submission.
See architecture and recovery, privacy and security, and troubleshooting. Start with the local Codex connection before adding remote access.
This server cannot be deployed
Let your AI agent operate any website through a real, logged-in browser session.
Cloud browsers for AI agents: get past bot detection, sign in with MFA, run web tasks at scale.
Local Commander connects ChatGPT, Claude, Cursor and other MCP clients to Windows 11 computers you own. Your AI can read approved project files and Git state, run the checks and commands you authorize, and check local services. Your workspace at localcmd.app shows which computer ran each request and how it ended. Once you approve a computer and connect your AI, it can do what your Windows account can do; you can limit it to folders, block commands or switch it off at any time. Free on up to 5 computers; the Team pack adds 10 more for $15 a month.
Browser MCP for logged-in tasks. Uses your Chrome — credentials stay local. Zero-token replay.
