convez.ai
MCP ServerAutomaçãoIntermediário
adbarc92

Browser Bridge MCP

adbarc92/mcp-browser-bridge

Controle o navegador direto da IA com screenshots, clicks e automação

Ver no GitHub
InicialPluginScore · de 0 a 100

Servidor MCP que oferece acesso direto do navegador a assistentes de IA — navegação, cliques, preenchimento de formulários, execução de JavaScript e captura de telas. Funciona com qualquer cliente MCP compatível (Claude Code, Cursor, Windsurf, Cline) através de uma extensão Chrome que estabelece comunicação via WebSocket.

Instalação

$npx convez-ai adbarc92/mcp-browser-bridge

1 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

Estrelas
1
Forks
0
Acompanhando
0
Saúde
42%
Último commit
há 2 semanas
Versão
—
Issues abertas
1
Contribuidores
1

Casos de uso

  • Automação de testes QA estruturados e validação de cenários
  • Web scraping e leitura de conteúdo dinâmico com análise em tempo real
  • Preenchimento automático de formulários e interações com páginas complexas

Veredito

Ferramenta robusta que elimina a lacuna entre IA e interação web real. Implementação limpa com suporte a múltiplos clientes MCP, embora requeira instalação de extensão Chrome e compreensão de configuração de MCP para máximo aproveitamento.

README

A tradução para o português deste README ainda está na fila.

Browser Bridge MCP

npm version

MCP server that gives AI coding assistants direct access to the browser — navigate, click, fill forms, run JavaScript, take screenshots, and read page content.

MCP Client ←(stdio)→ mcp-browser-bridge ←(WebSocket :7483)→ Browser Extension ←(Chrome APIs)→ Browser

Works with any MCP-compatible client: Claude Code, Cursor, Windsurf, Cline, and others.

Quick Start

1. Install the extension

Install from the Chrome Web Store, or load manually:

  1. Download or clone this repo.
  2. Open chrome://extensions, enable Developer mode.
  3. Click Load unpacked and select the extension/ folder.

Works in any Chromium browser: Chrome, Brave, Edge, Arc, Vivaldi, Opera.

2. Add to your MCP client

Run:

claude mcp add browser-bridge -- npx -y mcp-browser-bridge

Or add to .mcp.json:

{
  "mcpServers": {
    "browser-bridge": {
      "command": "npx",
      "args": ["-y", "mcp-browser-bridge"]
    }
  }
}

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "browser-bridge": {
      "command": "npx",
      "args": ["-y", "mcp-browser-bridge"]
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "browser-bridge": {
      "command": "npx",
      "args": ["-y", "mcp-browser-bridge"]
    }
  }
}

Use npx -y mcp-browser-bridge as the server command in your client's MCP configuration. The server communicates over stdio.

3. Verify

Start your MCP client. The extension popup should show a green Connected indicator. Call the browser_status tool to confirm.

Available Tools

All tools accept an optional tabId parameter. When omitted, they target the active tab.

ToolDescription
browser_statusCheck if the extension is connected and get active tab info
browser_navigateNavigate a tab to a URL
browser_screenshotCapture a screenshot of the visible area of a tab
browser_evaluateExecute JavaScript in a tab and return the result
browser_clickClick an element by CSS selector
browser_fillFill a form field by CSS selector (React-compatible)
browser_get_contentGet the text or HTML of a page or element
browser_get_tabsList all open browser tabs
browser_get_consoleGet captured console log entries from a tab
browser_wait_forWait for a CSS selector to appear on the page
browser_send_messageSend a custom message to the extension

Included Prompts

The server ships two MCP prompts that provide guided workflows to any connected client:

PromptDescription
browseGeneral-purpose browser interaction — navigating, clicking, filling forms, screenshotting, running JS. Accepts an optional task argument.
qa-runnerStructured QA checklist execution — drives the browser through test scenarios defined in markdown and reports pass/fail results. Accepts an optional checklist path.

In Claude Code, these appear as slash commands: /browser-bridge:browse and /browser-bridge:qa-runner.

Configuration

The WebSocket port defaults to 7483. To change it:

  • Server side: Set the BRIDGE_WS_PORT environment variable in your MCP config.
  • Extension side: Change the port in the extension popup and click Reconnect.

Security

  • WebSocket binds to 127.0.0.1 only — no network exposure.
  • Connections restricted to browser extension origins.
  • Single extension client at a time.

Troubleshooting

Extension shows "Disconnected" Check that the MCP server is running and the port is free:

# macOS/Linux
lsof -i :7483

# Windows
netstat -aon | findstr :7483

Tools return "No extension connected" Open the extension popup and click Reconnect.

Screenshots fail The target tab must be visible and focused. Background or minimized tabs cannot be captured.

browser_evaluate returns unexpected results Results must be JSON-serializable. Promises return {} — use synchronous expressions or await inside an IIFE and return a plain value.

Development

git clone https://github.com/adbarc92/mcp-browser-bridge.git
cd mcp-browser-bridge
npm install
npm run build
npm test                 # 53 tests via Vitest

Load the extension locally via chrome://extensions → Load unpacked → select extension/.

The repo includes a .mcp.json configured for local development.

License

MIT

Ver o original no GitHub

Bom para

Relacionados