How to install nodriver — Chrome browser automation in Antigravity CLI
To install nodriver — Chrome browser automation in Antigravity CLI, add the "nodriver-chrome-browser-automation" block to the mcpServers section of ~/.gemini/config/mcp_config.json (remote servers use "serverUrl"), then start agy.
Built from the published package · server updated 6 days ago
- 1
Open the MCP config
Create or open ~/.gemini/config/mcp_config.json for every project, or .agents/mcp_config.json for this project only.
- 2
Add the server
Paste this. If the file already has servers, add the "nodriver-chrome-browser-automation" entry inside the existing mcpServers block.
{ "mcpServers": { "nodriver-chrome-browser-automation": { "command": "uvx", "args": [ "nodriver-mcp" ] } } } - 3
Start Antigravity CLI
Run agy. The server and its tools load when the session starts.
Config file: ~/.gemini/config/mcp_config.json (all projects) or .agents/mcp_config.json (this project)
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 Antigravity CLI?
Yes. Antigravity CLI supports local and remote mcp servers, skills, plugins, and nodriver — Chrome browser automation installs with the steps above.
nodriver — Chrome browser automation does not show up in Antigravity CLI. What now?
Restart Antigravity CLI 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.
