/ Verzeichnis / Playground / Chrome MCP
● Community hangwin ⚡ Sofort

Chrome MCP

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

Warum nutzen

Hauptfunktionen

Live-Demo

In der Praxis

mcp-chrome.replay ▶ bereit
0/0

Installieren

Wählen Sie Ihren Client

~/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"
      ]
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

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

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

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

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

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

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

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

Continue nutzt ein Array von Serverobjekten statt einer Map.

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

In context_servers hinzufügen. Zed lädt beim Speichern neu.

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

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: Chrome MCP

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

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

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

Voraussetzungen
  • 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
Ablauf
  1. Confirm tabs
    List my open Chrome tabs.✓ Kopiert
    → Tab titles + URLs for every active tab
  2. Extract
    From the Bloomberg tab, extract the article body and the sidebar data table.✓ Kopiert
    → 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?✓ Kopiert
    → Synthesis with per-tab citations

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

Fallstricke
  • Session expires mid-task — Extension surfaces a refresh prompt; reauth in that tab and retry
Kombinieren mit: memory

Catch UI regressions by screenshotting flows in your dev build

👤 Frontend engineers ⏱ ~30 min intermediate

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

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

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

Fallstricke
  • Screenshots differ due to font loading — Add a sleep or wait_for_selector step before capturing
Kombinieren mit: filesystem

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

mcp-chrome + filesystem

Save extracted pages to disk for later indexing

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

Remember key findings across browsing sessions

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

Werkzeuge

Was dieses MCP bereitstellt

WerkzeugEingabenWann aufrufenKosten
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

Kosten & Limits

Was der Betrieb kostet

API-Kontingent
Local — unlimited
Tokens pro Aufruf
DOM extracts can be large; 5k–50k tokens
Kosten in €
Free
Tipp
Use read_tab with selector to scope extraction instead of pulling the full DOM

Sicherheit

Rechte, Secrets, Reichweite

Minimale Scopes: chrome.tabs chrome.scripting
Credential-Speicherung: None — Chrome holds the sessions
Datenabfluss: Tab contents flow through the MCP client to your LLM provider
Niemals gewähren: access to incognito without reason

Fehlerbehebung

Häufige Fehler und Lösungen

Extension not detected

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

Prüfen: 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.

Alternativen

Chrome MCP vs. andere

AlternativeWann stattdessenKompromiss
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

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen