How to install nodriver — Chrome browser automation in Codex
To install nodriver — Chrome browser automation in Codex, run "codex mcp add nodriver-chrome-browser-automation -- uvx nodriver-mcp" in your terminal, then type /mcp in Codex to check it.
Built from the published package · server updated 6 days ago
- 1
Run the install command
In a terminal, run:
codex mcp add nodriver-chrome-browser-automation -- uvx nodriver-mcp - 2
Check it
Inside Codex, type /mcp to see the server and its tools.
MCP servers run with your permissions. If nodriver — Chrome browser automation needs an API key, add it under env in the config. Check its README.
Install nodriver — Chrome browser automation in another app
Similar servers
Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
Let your AI agent operate any website through a real, logged-in browser session.
Dark web OSINT over Tor: search onion engines, scrape pages, report with your own model.
Questions
Does nodriver — Chrome browser automation work in Codex?
Yes. Codex supports mcp servers in the codex cli and ide extension, and nodriver — Chrome browser automation installs with the steps above.
nodriver — Chrome browser automation does not show up in Codex. What now?
Restart Codex fully, check the JSON is valid, and make sure uv (for uvx) is installed. See common MCP errors and fixes.
Is nodriver — Chrome browser automation safe?
It scores 54 of 100. Review the code before you install it, and only give it the access it needs. Grades and details.
