MCP servers · cloudcorprecords

browserdebug: Chrome debugging as a CLI and stdio MCP server

A Chrome DevTools-style debugging tool available as both a command-line interface and a stdio MCP server, exposing 26 tools.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

browserdebug provides Chrome DevTools-style debugging in one binary, usable either as a CLI or as a stdio MCP server. It can record performance traces and read their insights, list and inspect network requests, read console messages, take text snapshots and screenshots, emulate network, CPU and device conditions, and drive page input by element uid. The MCP server exposes 26 tools, including click, fill, navigate_page, evaluate_script and take_screenshot.

It suits developers who want to inspect and debug web pages running in Chrome, from a terminal or from an MCP-capable AI client. Its performance-trace workflow requires a trace to be started before it can be stopped and prevents it from being started twice. CLI exit codes are 0 for success, 1 for browser errors and 2 for usage errors.

The package bundles no browser and downloads none. A deployment must inject a DevTools-protocol-compatible executor, defined by the DebugBrowser interface in src/types.ts, to drive a real Chrome. Without one, browser commands fail with a "Browser unavailable" error.

Limitations and requirements

Browser commands need a DevTools-protocol-compatible executor injected by the deployment to drive a real Chrome. The package does not include or download a browser, and without an executor, browser commands fail with a "Browser unavailable" error.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    io.github.CloudCorpRecords/browserdebug

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

    v0.1.0
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
modelcontextprotocol

MCP reference servers

Seven small example servers maintained by the Model Context Protocol project: files, Git, web fetching, memory, time, step-by-step thinking and a test server.

92K GitHub starsSoftware development
Updated 18 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
firecrawl

Firecrawl MCP Server (web search and scraping)

Firecrawl's MCP server that lets an AI assistant search the web, turn pages and PDFs into clean Markdown, crawl sites and interact with dynamic pages.

7.8K GitHub starsWeb, search & browserProductivity & automation
Updated 17 Nov 2026
browserdebug: Chrome debugging as a CLI and stdio MCP server | AI Gate Discover