/ Directorio / Playground / Chrome MCP
● Comunidad 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 qué usarlo

Características clave

Demo en vivo

Cómo se ve en la práctica

mcp-chrome.replay ▶ listo
0/0

Instalar

Elige tu 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"
      ]
    }
  }
}

Abre Claude Desktop → Settings → Developer → Edit Config. Reinicia después de guardar.

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

Cursor usa el mismo esquema mcpServers que Claude Desktop. La configuración del proyecto prevalece sobre la global.

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

Haz clic en el icono MCP Servers de la barra lateral de Cline y luego en "Edit Configuration".

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

Mismo formato que Claude Desktop. Reinicia Windsurf para aplicar.

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

Continue usa un array de objetos de servidor en lugar de un mapa.

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

Añádelo a context_servers. Zed recarga en caliente al guardar.

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

Un solo comando. Verifica con claude mcp list. Quita con claude mcp remove.

Casos de uso

Usos del mundo real: Chrome MCP

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

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

Cuándo usarlo: You're logged into a paywalled site or gated dashboard and want Claude to read it.

Requisitos previos
  • 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
Flujo
  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.

Errores comunes
  • Session expires mid-task — Extension surfaces a refresh prompt; reauth in that tab and retry
Combinar con: memory

Catch UI regressions by screenshotting flows in your dev build

👤 Frontend engineers ⏱ ~30 min intermediate

Cuándo usarlo: You just shipped a CSS refactor and want a visual diff on 10 core pages.

Flujo
  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.

Errores comunes
  • Screenshots differ due to font loading — Add a sleep or wait_for_selector step before capturing
Combinar con: filesystem

Combinaciones

Combínalo con otros MCPs para multiplicar por 10

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

Herramientas

Lo que expone este MCP

HerramientaEntradasCuándo llamarCoste
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

Coste y límites

Lo que cuesta ejecutarlo

Cuota de API
Local — unlimited
Tokens por llamada
DOM extracts can be large; 5k–50k tokens
Monetario
Free
Consejo
Use read_tab with selector to scope extraction instead of pulling the full DOM

Seguridad

Permisos, secretos, alcance

Ámbitos mínimos: chrome.tabs chrome.scripting
Almacenamiento de credenciales: None — Chrome holds the sessions
Salida de datos: Tab contents flow through the MCP client to your LLM provider
No conceder nunca: access to incognito without reason

Resolución de problemas

Errores comunes y soluciones

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 otros

AlternativaCuándo usarlaContrapartida
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

Más

Recursos

📖 Lee el README oficial en GitHub

🐙 Ver issues abiertas

🔍 Ver todos los 400+ servidores MCP y Skills