grok-browser-mcp
Attaches to a running Brave browser via Chrome DevTools Protocol, providing tools to list and focus tabs, snapshot clickable elements, click, type, press keys, navigate, scroll, wait, evaluate JavaScript, and take screenshots in the user's existing browser session.
Click on "Install 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., "@grok-browser-mcpTake a screenshot of the current tab"
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.
grok-browser-mcp
MCP server that attaches to your already-running Brave over Chrome DevTools Protocol (CDP). Grok CLI can then snapshot, click, type, and screenshot whatever tab you have open — same window, same logins.
It does not launch a fresh empty browser.
Requirements
Related MCP server: playwriter
Install
git clone https://github.com/v76ADrR/grok-browser-mcp.git
cd grok-browser-mcp
npm installEnable CDP on Brave (once)
The Arch/CachyOS Brave wrapper reads ~/.config/brave-flags.conf. Put:
--remote-debugging-port=9222
--remote-debugging-address=127.0.0.1
--remote-allow-origins=*Restart Brave. Tabs usually restore. Confirm:
curl -s http://127.0.0.1:9222/json/versionOr call the MCP tool browser_prepare (this restarts Brave).
CDP is localhost only. Any process on this machine can control the browser while those flags are set. Remove them and restart Brave when you are done.
Grok CLI config
~/.grok/config.toml:
[mcp_servers.browser]
command = "/usr/bin/node"
args = ["/ABS/PATH/TO/grok-browser-mcp/src/server.mjs"]
enabled = true
startup_timeout_sec = 20
tool_timeout_sec = 180Reload: /mcps then r, or a new Grok session.
Tools
Tool | Purpose |
| Brave PIDs + CDP health |
| Write flags; restart Brave if CDP is down |
| List / focus tabs |
| Clickable elements + refs |
| Filter snapshot by text |
| Click by ref / selector / text |
| Keyboard |
| JS in the page |
| JPEG of the current tab |
| Navigation |
Never call Playwright browser.close() on this connection — it would quit the user's Brave.
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Browser MCP for logged-in tasks. Uses your Chrome — credentials stay local. Zero-token replay.
Live browser debugging for AI assistants — DOM, console, network via MCP.
Automate cloud Chrome—navigate, click, type, screenshot, run code, record screen video
Stealth web automation for AI agents. Login, signup, navigate, screenshot.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI coding assistants to control and inspect a live Chrome browser for automation, debugging, performance analysis, network monitoring, and DOM interaction through Chrome DevTools Protocol.1,465,302Apache 2.0
- AlicenseNot gradedqualityAmaintenanceConnects to your running Chrome browser, enabling AI agents to automate it via Playwright API with existing logins and extensions.2,6283,858MIT
- AlicenseNot gradedqualityDmaintenanceGives AI agents full control over Brave Browser, optimized for local LLMs to ensure low latency and high reliability.MIT
- AlicenseAqualityDmaintenanceConnects to a running Chrome instance via CDP to expose browser control as MCP tools, preserving login state, cookies, and extensions for automation.1915MIT