chrome-devtools-mcp-adspower

Chrome DevTools MCP + AdsPower Integration Skill

Connect Google's Chrome DevTools MCP to AdsPower antidetect browser profiles. This lets AI coding agents (Claude Code, Cursor, Codex CLI) control fingerprint-isolated browser sessions through natural language.

Why This Combination

• Chrome DevTools MCP gives AI agents eyes in the browser: inspect DOM, monitor network, run JavaScript, take screenshots
• AdsPower gives each browser session a unique fingerprint, proxy, and identity
• Together: your AI agent can operate across multiple isolated browser identities — each with its own fingerprint, cookies, and IP address

Claude Code → Chrome DevTools MCP → AdsPower Profile (unique fingerprint + proxy)
                                  → AdsPower Profile (unique fingerprint + proxy)
                                  → AdsPower Profile (unique fingerprint + proxy)

How It Works

AdsPower's Local API opens browser profiles and exposes a Chrome DevTools Protocol (CDP) endpoint for each one. Chrome DevTools MCP connects to that endpoint via --browserUrl.

Prerequisites

• AdsPower installed and running (paid plan with API access)
• Chrome DevTools MCP installed (npm install -g chrome-devtools-mcp@latest)
• API Key generated (AdsPower → Automation → API → Generate)
• Python 3.8+ with requests installed

Step 1: Open an AdsPower Profile and Get the CDP Endpoint

import requests

API_KEY = "your_api_key"
BASE_URL = "http://local.adspower.net:50325"
HEADERS = {"Authorization": f"Bearer {API_KEY}"}

PROFILE_ID = "your_profile_id"

# Open the browser profile
resp = requests.get(
    f"{BASE_URL}/api/v1/browser/start?user_id={PROFILE_ID}",
    headers=HEADERS,
    timeout=30,
).json()

if resp["code"] == 0:
    # This is the CDP WebSocket endpoint
    ws_endpoint = resp["data"]["ws"]["puppeteer"]
    debug_port = ws_endpoint.split(":")[2].split("/")[0]
    print(f"CDP WebSocket: {ws_endpoint}")
    print(f"Debug port: {debug_port}")
else:
    print(f"Error: {resp['msg']}")