Back to Browse

Browserdebug MCP Server

Developer ToolsModerate5.5MCP RegistryLocal
Free

Server data from the Official MCP Registry

Debug web pages in Chrome: performance traces, network, console, snapshots, screenshots.

About

Debug web pages in Chrome: performance traces, network, console, snapshots, screenshots.

Security Report

5.5
Moderate5.5Moderate Risk

browserdebug is a local stdio MCP server with no hardcoded secrets, no network calls, and no exfiltration logic; it bundles no browser and fails closed when no executor is injected. The main concerns are that upload_file accepts any local file path and evaluate_script runs arbitrary JavaScript in the page, which are inherent to the tool's purpose but worth scoping. File write paths for screenshots, snapshots, and traces are also unvalidated. Supply chain analysis found 4 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.

8 files analyzed · 10 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

File System Write

Writes or modifies files on your machine. Check that this is expected for the tool.

browser_control

Check that this permission is expected for this type of plugin.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "browserdebug": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/browserdebug@0.1.0"
      ]
    }
  }
}

Some servers take additional arguments. See the repository for details.

Documentation

View on GitHub

From the project's GitHub README.

browserdebug

Chrome DevTools-style debugging as a CLI and a stdio MCP server in one bin. Record performance traces and read their insights, list and inspect network requests, read console messages, take text snapshots and screenshots, emulate network/CPU/device conditions, and drive page input by element uid.

The browser sits behind an injectable executor interface (DebugBrowser in src/types.ts). This package bundles no browser and downloads none: with no executor configured, browser commands fail with a clear "Browser unavailable" error. Deployments inject a DevTools-protocol-compatible executor to drive a real Chrome. The performance-trace state machine lives in the core: a trace must be started before it can be stopped, and cannot be started twice.

Install

npx -y @reneturcios/browserdebug mcp

CLI

browserdebug mcp
browserdebug pages
browserdebug navigate <url>
browserdebug snapshot
browserdebug screenshot [file]
browserdebug --version

Exit codes: 0 success, 1 browser error, 2 usage error.

MCP tools

26 tools: click, drag, fill, fill_form, handle_dialog, hover, press_key, upload_file, close_page, list_pages, navigate_page, new_page, select_page, wait_for, emulate, resize_page, performance_analyze_insight, performance_start_trace, performance_stop_trace, get_network_request, list_network_requests, evaluate_script, get_console_message, list_console_messages, take_screenshot, take_snapshot.

MCP client config:

{
  "mcpServers": {
    "browserdebug": {
      "command": "npx",
      "args": ["-y", "@reneturcios/browserdebug", "mcp"]
    }
  }
}

Docker

docker run -i ghcr.io/cloudcorprecords/browserdebug          # MCP server
docker run --rm ghcr.io/cloudcorprecords/browserdebug --version

Development

npm install
npm run build
npm test

MIT license.

Reviews

No reviews yet

Be the first to review this server!