Chrome Debug MCP Server

This MCP allows you to record browser interactions with a chrome extension that include screenshots and console logs. The data is then saved to a

Local serverstdioGo

What is the Chrome Debug MCP Server?

This MCP allows you to record browser interactions with a chrome extension that include screenshots and console logs. The data is then saved to a local database

The short version

A Model Context Protocol (MCP) implementation for browser automation using Playwright, with full Greasemonkey API support.

The tools it exposes

The server publishes 2 tools. What each one is for:

  • Prerequisites — The Prerequisites tool exposed by this server
  • Setup — The Setup tool exposed by this server

What it needs from you

  • Node.js 16 or higher - npm 7 or higher

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.

How to install the Chrome Debug MCP Server

{
  "mcpServers": {
    "chrome-debug": {
      "command": "node",
      "args": [
        "path/to/chrome-debug-mcp/build/index.js"
      ],
      "disabled": false,
      "alwaysAllow": []
    }
  }
}

From the project documentation. Replace placeholders and example paths before connecting.

Configuration

  • Node.js 16 or higher - npm 7 or higher

Example prompts to try

  • “Use Chrome Debug MCP to Prerequisites.”
  • “Use Chrome Debug MCP to Setup.”

Frequently asked questions

This MCP allows you to record browser interactions with a chrome extension that include screenshots and console logs. The data is then saved to a local database Confirm the tools offered by your installed version in the connected client. Tool availability and permissions depend on the server and account configuration.