/ Diretório / Playground / Chrome MCP
● Comunidade hangwin ⚡ Instantâneo

Chrome MCP

por hangwin · hangwin/mcp-chrome

Let Claude drive your real Chrome — already logged in, with your cookies and sessions — for browser automation and research.

Chrome MCP installs as a Chrome extension and exposes browser functions to Claude: navigate, click, type, screenshot, extract, semantic-search across tabs. Because it uses your actual browser, it works on sites that block headless bots and lets Claude act inside authenticated sessions you already have open.

Por que usar

Principais recursos

Demo ao vivo

Como fica na prática

mcp-chrome.replay ▶ pronto
0/0

Instalar

Escolha seu cliente

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "mcp-chrome": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-chrome-bridge"
      ]
    }
  }
}

Abra Claude Desktop → Settings → Developer → Edit Config. Reinicie após salvar.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "mcp-chrome": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-chrome-bridge"
      ]
    }
  }
}

Cursor usa o mesmo esquema mcpServers que o Claude Desktop. Config de projeto vence a global.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "mcp-chrome": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-chrome-bridge"
      ]
    }
  }
}

Clique no ícone MCP Servers na barra lateral do Cline, depois "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "mcp-chrome": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-chrome-bridge"
      ]
    }
  }
}

Mesmo formato do Claude Desktop. Reinicie o Windsurf para aplicar.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "mcp-chrome",
      "command": "npx",
      "args": [
        "-y",
        "mcp-chrome-bridge"
      ]
    }
  ]
}

O Continue usa um array de objetos de servidor em vez de um map.

~/.config/zed/settings.json
{
  "context_servers": {
    "mcp-chrome": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "mcp-chrome-bridge"
        ]
      }
    }
  }
}

Adicione em context_servers. Zed recarrega automaticamente ao salvar.

claude mcp add mcp-chrome -- npx -y mcp-chrome-bridge

Uma linha só. Verifique com claude mcp list. Remova com claude mcp remove.

Casos de uso

Usos do mundo real: Chrome MCP

Do research on sites that require login without handing Claude your password

👤 Researchers, analysts using subscription content ⏱ ~20 min beginner

Quando usar: You're logged into a paywalled site or gated dashboard and want Claude to read it.

Pré-requisitos
  • Chrome extension installed — Install from Chrome Web Store; the bridge MCP auto-connects
  • Target site already open and authenticated in Chrome — Log in manually in a regular tab first
Fluxo
  1. Confirm tabs
    List my open Chrome tabs.✓ Copiado
    → Tab titles + URLs for every active tab
  2. Extract
    From the Bloomberg tab, extract the article body and the sidebar data table.✓ Copiado
    → Structured content pulled; no "cannot access" error
  3. Cross-tab synthesis
    Across the 3 research-provider tabs I have open, what's the consensus view on X?✓ Copiado
    → Synthesis with per-tab citations

Resultado: Answers backed by real authenticated content, no scraping of login pages.

Armadilhas
  • Session expires mid-task — Extension surfaces a refresh prompt; reauth in that tab and retry
Combine com: memory

Catch UI regressions by screenshotting flows in your dev build

👤 Frontend engineers ⏱ ~30 min intermediate

Quando usar: You just shipped a CSS refactor and want a visual diff on 10 core pages.

Fluxo
  1. Open baseline
    Open my dev site pages listed in /qa/flows.json and screenshot each into /screenshots/before/.✓ Copiado
    → Screenshots captured with filenames matching URLs
  2. Compare
    After I deploy, take fresh screenshots and diff against /screenshots/before/. Summarize visual changes per page.✓ Copiado
    → Per-page diff report with concrete observations

Resultado: A visual-regression report in 5 minutes, using your real browser environment.

Armadilhas
  • Screenshots differ due to font loading — Add a sleep or wait_for_selector step before capturing
Combine com: filesystem

Combinações

Combine com outros MCPs para 10× de alavancagem

mcp-chrome + filesystem

Save extracted pages to disk for later indexing

Extract this tab and write to /research/ai-paper-notes.md.✓ Copiado
mcp-chrome + memory

Remember key findings across browsing sessions

Summarize what I read today and store it in memory.✓ Copiado

Ferramentas

O que este MCP expõe

FerramentaEntradasQuando chamarCusto
list_tabs none Start of any session to see what's available free
read_tab tab_id: int Pull content from a specific tab free
click tab_id, selector: str Interact with page elements free
screenshot tab_id, full_page?: bool Visual capture for diff or review free
search_tabs query: str Find which tab discusses X free

Custo e limites

O que custa rodar

Cota de API
Local — unlimited
Tokens por chamada
DOM extracts can be large; 5k–50k tokens
Monetário
Free
Dica
Use read_tab with selector to scope extraction instead of pulling the full DOM

Segurança

Permissões, segredos, alcance

Escopos mínimos: chrome.tabs chrome.scripting
Armazenamento de credenciais: None — Chrome holds the sessions
Saída de dados: Tab contents flow through the MCP client to your LLM provider
Nunca conceda: access to incognito without reason

Solução de problemas

Erros comuns e correções

Extension not detected

Pin the extension; the bridge binary needs the extension polling for it

Verificar: chrome://extensions shows it enabled
Tab content is blank

Page may use shadow DOM — try read_tab with include_shadow=true

Clicks don't register

Site uses anti-automation (Cloudflare, etc). Try scrolling to trigger lazy-load first.

Alternativas

Chrome MCP vs. outros

AlternativaQuando usarTroca
chrome-devtools MCPYou want the devtools protocol (console, network, perf) not user automationDevTools MCP doesn't drive the UI — it inspects it
playwright MCPYou want headless automation in CINo auth state; bot-detection prone

Mais

Recursos

📖 Leia o README oficial no GitHub

🐙 Ver issues abertas

🔍 Ver todos os 400+ servidores MCP e Skills