Chrome Remote Debugging

Verified Integration

Author: @connecting•Category: ServerApplication

GitHub Repository

JSON-RPC 2.0

Protocol Standard

Sub-second

Execution Latency

Active

Operational Status

Client Configuration

— Connect Chrome Remote Debugging to Claude Desktop or Cursor in seconds

{
  "mcpServers": {
    "chrome-remote-debugging": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-chrome-remote-debugging"
      ],
      "env": {}
    }
  }
}

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows).

Architecture & Capabilities

System Overview

Controls a running Chrome instance by connecting to its remote-debugging endpoint and exposing browser control as MCP tools.

Indexed Date

7/22/2026

License

Open Source

Protocol Layer

stdio / SSE RPC

Frequently Asked Questions

Architecture and operational details for Chrome Remote Debugging

Yes, you need Python ≥ 3.10 and a Chrome/Chromium browser started with the `--remote-debugging-port` flag, for example: `google-chrome --remote-debugging-port=9222`. For SSH tunneling, an SSH client on your PATH and key-based authentication are required.

Related MCP Servers

Browse all servers →

@configuring

0xArchive

Provides comprehensive historical and real-time crypto market data, including orderbooks, trades, candles, and more, from Hyperliquid, HIP-3, and Lighter.xyz.

MCP Server5 FAQs

Learn more

@spawning

0xGasless

Facilitates gasless blockchain transactions and interactions directly from Claude AI conversations.

MCP Server4 FAQs

Learn more

@spawning

0xGasless

Bridges Claude AI with blockchain networks, enabling gasless transactions, swaps, and transfers directly from natural language conversations.

MCP Server5 FAQs

Learn more