MCP Chrome Bridge
wizardofweb125-lab/mcp-chrome-bridge
Controle Chrome remotamente através de agentes de IA via MCP
Ver no GitHubServidor MCP que permite controlar Chrome via agentes de IA. Oferece acesso a abas, navegação, cliques, preenchimento de formulários, screenshots, logs do console e até gravação em GIF. Funciona com qualquer cliente compatível com MCP, usando uma extensão Chrome nativa para comunicação segura.
Instalação
npx convez-ai wizardofweb125-lab/mcp-chrome-bridge1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Automação de testes web com agentes de IA
- Web scraping e coleta de dados via agentes
- Automação de fluxos de trabalho em aplicações web
- Gravação e análise de interações de usuário
- Debugging remoto e análise de console/network logs
Veredito

Ferramenta robusta para quem precisa de automação web profunda com agentes de IA. A arquitetura via extensão Chrome é bem pensada, mas exige setup técnico não-trivial (relay, extensão, native messaging). Ideal para construtores de automação, não para iniciantes.
README
A tradução para o português deste README ainda está na fila.
MCP server that lets any AI agent control Chrome — tabs, navigation, clicks, forms, screenshots, console/network logs, GIF recording, and more. Works with any MCP-compatible client (Claude Code, OpenCode, custom agents).
Architecture
Agent → MCP server (stdio) → WebSocket relay (localhost:9876) → Chrome Extension → chrome.debugger API
- The extension creates a dedicated "Agent" tab group (purple) in your existing Chrome
- Same Chrome session = same cookies/auth (no separate browser needed)
- Native messaging keeps the extension alive
Setup
1. Install dependencies
cd mcp-chrome-bridge
npm install
2. Start the relay
node relay.js
Or set it up as a systemd user service for persistence.
3. Load the Chrome extension
- Open Chrome →
chrome://extensions/ - Enable "Developer mode" (toggle top-right)
- Click "Load unpacked" → select the
extension/folder
4. Install native messaging host
./install.sh <your-extension-id>
The extension ID is shown in chrome://extensions/ after loading.
5. Configure your MCP client
Add to your MCP config:
{
"mcpServers": {
"chrome-bridge": {
"command": "node",
"args": ["/path/to/mcp-chrome-bridge/server.js"]
}
}
}
Tools
Browser (via Chrome extension relay)
| Tool | Description |
|---|---|
tabs_context | List tabs in the agent window |
tabs_create | Open a new tab |
tabs_close | Close a tab |
navigate | Navigate to a URL |
read_page | Read visible text content |
get_page_text | Get full page text |
click | Click an element (CSS selector) |
form_input | Fill a form field |
javascript | Execute JS in a tab |
find | Find elements by selector or text |
file_upload | Upload a file to an input[type=file] |
screenshot | Screenshot a tab |
screenshot_area | Screenshot a specific region |
console_logs | Read browser console messages |
network_logs | Read network requests |
gif_start | Start GIF recording |
gif_capture | Capture a GIF frame |
gif_stop | Stop recording, get frames |
Desktop (local, no relay needed)
| Tool | Description |
|---|---|
computer_mouse_move | Move mouse cursor |
computer_click | Click at coordinates |
computer_type | Type text via keyboard |
computer_key | Press key combo (e.g. ctrl+a) |
computer_screenshot | Screenshot entire screen or region |
web_fetch | Fetch a URL (server-side) |
web_search | Search the web via DuckDuckGo |
System dependencies
- Node.js 18+
- xdotool — for desktop mouse/keyboard tools
- grim — for Wayland screen capture (optional, X11 fallback via extension)
Environment variables
| Variable | Default | Description |
|---|---|---|
RELAY_URL | ws://127.0.0.1:9876 | WebSocket relay address |
Troubleshooting
See TROUBLESHOOTING.md for common issues (relay timeouts, extension disconnects, shadow DOM, file uploads).