/ Annuaire / Playground / Chrome MCP
● Communauté hangwin ⚡ Instantané

Chrome MCP

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

Pourquoi l'utiliser

Fonctionnalités clés

Démo en direct

Aperçu en pratique

mcp-chrome.replay ▶ prêt
0/0

Installer

Choisissez votre 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"
      ]
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

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

Cursor utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

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

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "Edit Configuration".

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

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

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

Continue utilise un tableau d'objets serveur plutôt qu'une map.

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

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

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

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : Chrome MCP

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

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

Quand l'utiliser : You're logged into a paywalled site or gated dashboard and want Claude to read it.

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

Résultat : Answers backed by real authenticated content, no scraping of login pages.

Pièges
  • Session expires mid-task — Extension surfaces a refresh prompt; reauth in that tab and retry
Combiner avec : memory

Catch UI regressions by screenshotting flows in your dev build

👤 Frontend engineers ⏱ ~30 min intermediate

Quand l'utiliser : You just shipped a CSS refactor and want a visual diff on 10 core pages.

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

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

Pièges
  • Screenshots differ due to font loading — Add a sleep or wait_for_selector step before capturing
Combiner avec : filesystem

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

mcp-chrome + filesystem

Save extracted pages to disk for later indexing

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

Remember key findings across browsing sessions

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

Outils

Ce que ce MCP expose

OutilEntréesQuand appelerCoût
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

Coût et limites

Coût d'exécution

Quota d'API
Local — unlimited
Tokens par appel
DOM extracts can be large; 5k–50k tokens
Monétaire
Free
Astuce
Use read_tab with selector to scope extraction instead of pulling the full DOM

Sécurité

Permissions, secrets, portée

Portées minimales : chrome.tabs chrome.scripting
Stockage des identifiants : None — Chrome holds the sessions
Sortie de données : Tab contents flow through the MCP client to your LLM provider
Ne jamais accorder : access to incognito without reason

Dépannage

Erreurs courantes et correctifs

Extension not detected

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

Vérifier : 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.

Alternatives

Chrome MCP vs autres

AlternativeQuand l'utiliserCompromis
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

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills