Install Browser MCP for OpenAI Codex
codex mcp add browser-mcp -- npx @agent360/browser-mcp
Run that in your terminal, load the Chrome extension once (Step 2 below), and Codex can drive your real, logged-in Chrome — your cookies, your sessions, your 2FA — instead of a blank headless browser that gets blocked on every login wall.
Install — 3 steps (~90 seconds)
Step 1: Add the MCP server to Codex
codex mcp add browser-mcp -- npx @agent360/browser-mcp
This writes a [mcp_servers.browser-mcp] entry to ~/.codex/config.toml (Codex's own config command does the writing — you don't touch the file by hand). If you'd rather edit it yourself, the entry looks like this:
[mcp_servers.browser-mcp] command = "npx" args = ["@agent360/browser-mcp"]
Default location: ~/.codex/config.toml on Mac/Linux (%USERPROFILE%\.codex\config.toml on Windows). You can also scope it to one project with a .codex/config.toml in that repo, if it's a trusted project.
Step 2: Load the Chrome extension (one-time)
The MCP server needs a companion Chrome extension to actually drive the browser — this part is identical no matter which MCP client you use.
Recommended — Chrome Web Store (auto-updates, zero config):
- Install from the Chrome Web Store →
- Done. Chrome updates it in the background on its own.
Alternative — manual load (no Chrome Web Store account, or you want the dev version):
- Download the latest release zip and unzip it anywhere
- Open Chrome →
chrome://extensions - Toggle Developer mode on (top right)
- Click Load unpacked (top left) and select the unzipped folder
- The Agent360 Browser MCP icon appears in your toolbar
With the manual route, Chrome won't auto-update the extension — re-download the zip and click ↻ reload on chrome://extensions when you want the latest version.
Step 3: Restart Codex and verify
Restart your Codex CLI session so it picks up the new server, then in the composer type:
/mcp
browser-mcp should show up connected, with its tools listed. That's it — no API keys, no cloud account, nothing leaves your machine.
What your Codex agent can do
The 2FA-killer move
This is the thing headless tools can't do: Codex hits a login wall, reads the one-time code out of your own logged-in Gmail tab, and continues the sign-in — because it's driving *your* browser, not a fresh anonymous one. No API can do that. Use it to operate platforms with no API, QA your own web app end-to-end against real auth, or work dashboards at human pace with you approving the sensitive steps.
34 tools, no server-side moving parts
| Category | What it gives your agent |
|---|---|
| Navigation & content | browser_navigate, browser_get_page_content, browser_screenshot, browser_execute_script |
| Interaction | browser_click, browser_fill, browser_select_option, browser_set_combobox, browser_set_date, browser_dismiss_overlays, browser_hover, browser_scroll, browser_press_key |
| Tabs & frames | browser_list_tabs, browser_switch_tab, browser_get_new_tab (for OAuth popups), browser_list_frames / browser_select_frame |
| Data & network | browser_get_cookies, browser_get_local_storage, browser_fetch (bypasses CORS from the extension), browser_wait_for_network, browser_extract_token |
| CAPTCHA | browser_solve_captcha — auto-detects reCAPTCHA v2/v3, hCaptcha, Turnstile, FunCaptcha; ~80% checkbox-solve rate, human fallback for the rest |
| Human-in-the-loop | browser_ask_user — overlay dialog for 2FA codes, CAPTCHA grids, or any credential Codex shouldn't guess at |
browser_extract_token ships with zero-config shortcuts for 9 common dashboards (Stripe, HubSpot, Slack, Shopify, Mailchimp, Pipedrive, Calendly, Google, LinkedIn) — but it isn't limited to those. Point it at any provider's API-settings page and it'll navigate there and walk you through pulling the token the same way; the 9 are just shortcuts, not a whitelist.
Runs up to 10 concurrent browser sessions with color-coded Chrome tab groups, so parallel Codex tasks don't step on each other's tabs.
Works with any MCP client
Browser MCP is a standard stdio MCP server — it doesn't know or care which client is talking to it. The same ~/.codex/config.toml entry is shared by the ChatGPT desktop app, Codex CLI, and the Codex IDE extension, so one setup unlocks all three. Outside the Codex/ChatGPT family it works identically with Claude Code, Claude Desktop, Cursor, Cline, Continue, or anything else that speaks MCP — same package, same extension, same npx @agent360/browser-mcp command, just wired in with that client's own config format instead of codex mcp add.
FAQ
Is this an official OpenAI integration? No — Browser MCP is an independent, open-source MCP server built by Agent360. It works with Codex because Codex speaks the standard Model Context Protocol, not because of any special partnership.
Do I need Claude Code installed to use this with Codex? No. codex mcp add writes straight to Codex's own ~/.codex/config.toml — nothing about this path touches Claude Code at all.
Is my browsing data safe? What does the extension see? Everything stays local. The extension talks to an MCP server on 127.0.0.1 on your own machine — nothing is sent to any external server, no telemetry, no analytics. Cookies and tokens are only pulled when your agent explicitly asks for them, one call at a time. Source is open and auditable on GitHub.
How does CAPTCHA solving actually work? Three layers: (1) auto-detect and click reCAPTCHA/hCaptcha/Turnstile checkboxes automatically (~80% pass rate), (2) AI-vision-guided grid solving for image challenges, (3) browser_ask_user shows you the challenge to solve by hand if the first two miss — then the agent continues. Nothing is routed through a third-party CAPTCHA-solving service.
Is it really free? Yes — MIT-licensed, open source, no paywall, no account, no API key. Built by Agent360 as part of its developer-tools work.
How do I remove it? codex mcp remove browser-mcp drops the entry from config.toml, then remove the extension from chrome://extensions. There's no global npm install to clean up — npx runs the server directly each time, it's never installed persistently.
What if I already have Browser MCP set up for Claude Code? The Chrome extension is shared — you only load it once, regardless of how many MCP clients point at it. You just need one more codex mcp add (or manual config.toml entry) so Codex knows about the same local server.