Give Codex a real cloud browser
Connect Codex to a Nevazu browser over MCP: a real Chrome in the cloud that stays signed in, on its own IP. Nothing to install: you approve the sign-in and watch it work.
Official Codex documentation
Codex reaches tools through the Model Context Protocol (MCP). Each Nevazu browser has its own hosted MCP server, so Codex can take screenshots of the whole screen, click, type, scroll, press shortcuts and upload files in a real Chrome: the same browser, tabs and sign-ins you use in the live view. You watch at the same time and take control back with any click or key.
What it can do
- Read pages the way a person sees them, from screenshots of the real screen: content drawn by scripts, images, charts and layout included.
- Work in the sites you are signed in to, with the session kept between visits.
- See what the browser’s region shows: websites see its dedicated IP and local time zone.
- Upload files from your computer into the browser, for a page’s upload form.
Connect Codex
- Create a browser in Nevazu, in the region you want.
- On the browser, choose the robot button (Connect an agent) and, under Use with agents, copy the setup. Paste it into Codex: it adds the server itself, as shown below.
- A Nevazu page opens in your web browser. Choose whether it may act or only look, and for how long: 1, 7, 30 or 90 days. Then choose Allow.
Every browser has its own MCP server: its own address (https://connect.nevazu.com/mcp/ followed by that browser’s ID) and its own sign-in, which reaches that browser only. Copy the setup from the browser you want Codex to use. For two browsers, add two servers with different names, such as nevazu-work and nevazu-tokyo, and sign in to each.
To add it by hand, the setup for Codex looks like this, with your browser’s own address in place of BROWSER_ID:
Add this to ~/.codex/config.toml (create the file if it is missing), then run codex mcp login nevazu-work in a terminal: Codex opens the sign-in in the user’s web browser and keeps the tokens. The same server in one command: codex mcp add nevazu-work --url https://connect.nevazu.com/mcp/BROWSER_ID. If Codex says login is not supported, update it.
[mcp_servers.nevazu-work]
url = "https://connect.nevazu.com/mcp/BROWSER_ID"
tool_timeout_sec = 90
# Then sign in from a terminal: codex mcp login nevazu-workThese steps follow Codex’s own documentation: Codex: Model Context Protocol ↗
Watching and taking over
While Codex is in control, the live view shows a green outline; while you are, a blue one. Any click, key, scroll or paste of yours takes control back before it is carried out, and Codex waits until you hand control back. Privacy pause also stops screenshots until you end it.
Questions
Do I need to install anything?
No. The MCP server is hosted by Nevazu and reached over HTTPS; Codex only adds its address. There is no key to store: you approve a sign-in instead, and Nevazu emails you each time an agent signs in.
Can Codex use the sites I am signed in to?
Yes: it works in the same Chrome and sign-ins you use. That also means it can do anything those accounts allow. Give it only tasks you would do yourself, choose view only where looking is enough, and prefer a separate browser for agent work.
Can Codex use more than one browser?
Yes, one MCP server per browser. Each browser has its own server address and its own sign-in, so add one server for each browser you want it to use, under different names. Approving one sign-in never gives access to your other browsers.
What does it cost?
Nevazu is prepaid and billed per minute while the browser runs; its dedicated IP and storage are charged while it exists. A browser an agent is working in stays awake; once the agent stops making requests, it sleeps on its usual timer. Current prices are on the pricing page.
How do I disconnect Codex?
In the browser’s Settings → Agent access, or on the Agents page. A disconnected agent loses access at once, even mid-task.