Chrome DevTools 高级 MCP 浏览器自动化服务

Chrome Devtools Advanced MCP

Your Intelligent Bridge Between AI and the Browser.

This Model Context Protocol (MCP) server enables AI assistants like Claude, Roo Code, or Windsurf to interact with Google Chrome in a natural, powerful, and stealthy way. Unlike other automation tools, this solution connects to your actual browser profile, allowing you to use your existing login sessions, cookies, and extensions without detection.

✨ Why Use This?

• 🕵️ "Human" Navigation: Uses a persistent clone of your real Chrome profile (cookies, localStorage, logged-in accounts). If you're logged into LinkedIn, Gmail, or your corporate ERP, your AI assistant is too — and the session survives between runs.
• 👤 Profile Cloning: list_chrome_profiles finds every profile on the machine, clone_chrome_profile mirrors the one you want into ~/.chrome-mcp/profiles/…, and sync_chrome_profile_to_real pushes logins back into your own Chrome.
• 🛡️ Undetectable: Stealth mode is applied per tab, and Chrome runs with the automation switch excluded.
• 🛠️ Robust Toolset: 96+ specialized tools, plus MCP resources and prompts, optimized for data scraping, specific element extraction, and visual analysis.
• ⚡ Fast & Safe: Safely executes scripts and screenshots, with intelligent output truncation to prevent crashing your AI context.

🚀 Quick Installation

For Users (VS Code / Cline / Kilo Code / Antigravity / Claude Desktop)

Simply add this to your mcp.json configuration file:

{
  "mcpServers": {
    "chrome-devtools-advanced-mcp": {
      "command": "npx",
      "args": ["-y", "chrome-devtools-advanced-mcp", "--port=9223"]
    }
  }
}

Restart your assistant (Ctrl+R in VS Code), and you'll have instant access.

💡 Simplified Usage Guide

0. First time: use your real Chrome profile (one command, one sign-in)

Ask your AI:

"Set up Chrome with my profile" → it calls setup_chrome_profile

That mirrors your real profile (your profile name/avatar, bookmarks, history, new-tab tiles, settings and — once — your extensions) into ~/.chrome-mcp/profiles/<profile> and opens Chrome on it.

What you have to do (the whole list):

Nothing else ever: no re-login, no closing Chrome afterwards, your personal browser is never touched (the clone is a separate Chrome instance). Saved passwords and autofill cannot be copied on Windows (Chrome encrypts them with a key bound to the browser) — save them once inside the clone if you want them there.

1. Launch the Browser

After that, ask your AI:

"Launch Chrome with my profile"

This triggers launch_chrome_with_profile, which reuses the clone window (or an already-debuggable Chrome) without closing your other windows.

2. Navigate & Analyze

You can ask:

• "Go to amazon.com and search for laptops"
• "Analyze the HTML of the login form" (Uses optimized get_html)
• "Take a screenshot of the pricing table"

3. Interact

The AI can click, type, and fill forms intelligently, waiting for elements to load automatically.

🛠️ Tool List

Tools are split into two tiers so the default list stays manageable for the AI: ~42 core tools are visible from the start; ~52 advanced tools (Network Advanced, Anti-Detection & Privacy, Service Workers, System, Performance) stay hidden until the AI calls show_advanced_tools (call hide_advanced_tools to collapse the list again).

📚 Resources & Prompts

Beyond tools, this server exposes two other MCP primitives:

• Resources (cacheable/listable, not just one-shot tool calls) — for each open tab: chrome://tab/{tabId}/html, chrome://tab/{tabId}/screenshot, chrome://tab/{tabId}/har.
• Prompts (pre-baked task templates that chain the tools above): audit-accessibility, debug-console-errors, scrape-table.

In clients that support them (e.g. Claude Desktop), these show up as attachable resources / slash-style prompts, separate from the tool list.

❓ FAQ

Do I need to close my Chrome? No! Thanks to "Shadow Profile" technology, this server creates a temporary safe clone of your profile. You can keep browsing normally while the AI works in parallel.

Does it work on Mac/Linux? Yes, it is fully cross-platform.

I see "Tool disabled by user" error This is a VS Code security feature.

1. Reload VS Code (Ctrl+R).
2. When the AI tries to use a tool again, click "Always Allow" on the popup.

Why are cookie values redacted / file:// blocked? Security defaults (see docs/USAGE_GUIDE.md → Security defaults): navigation is limited to http(s), cookie values require includeValues:true, and HAR exports/downloads are sandboxed to your working dir or temp folder.

📚 Documentation

• docs/USAGE_GUIDE.md — practical workflows for the AI on the current (v1.5) tool vocabulary.
• docs/TOOLS.md — complete, machine-checked reference of all 96 tools.
• docs/INSTALL.md — installation & configuration.
• docs/CHANGELOG.md — release notes.

👨‍💻 For Developers

To contribute or run locally:

git clone https://github.com/Eddym06/chrome-devTools-advanced-mcp.git
cd chrome-devTools-advanced-mcp
npm install
npm run build
npm start

Before opening a PR:

npm run lint        # ESLint (flat config)
npm run build       # clean tsc build
npm test            # vitest — includes an in-memory MCP client/server integration test
npm run docs:check  # fails if any guide references a non-existent tool
# optional, on a machine with Chrome installed:
CHROME_MCP_E2E=1 npm test   # real-Chrome end-to-end suite

CI (.github/workflows/ci.yml) runs lint + build + test on Node 20 and 22 for every push/PR.

Developed with ❤️ by @eddym06