Chromedebug

io.github.dynamicupgradePublished by GitHub account dynamicupgradev2.9.6Updated Oct 25, 2026

Record browser bugs - frames, clicks and console logs - and hand them to your AI over MCP.

VerifiedSTDIODesktop onlyBrowser Automation

Overview

AI-generated overview

Chromedebug records browser bugs — frames, clicks and console logs — and hands them to an AI assistant over MCP.

What you can do
Captures browser bug sessions, including frames, clicks and console logs, and exposes the recorded material to the assistant over MCP for review.
When to use it
Useful when you want an assistant to look at a recorded browser bug session — frames, clicks and console logs — instead of describing the problem by hand.
Requirements
Runs as a local process on the user's machine, installed from the npm package @dynamicu/chromedebug-mcp over stdio. Desktop only; no web executable. No authentication, environment variables or headers are declared.
Before you install
It records browser activity such as frames, clicks and console logs, which can include sensitive page content; review what a recording captures before sharing it with an assistant.

Installation

In SourceWeft

  1. Open Chromedebug in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2.9.6LatestOct 12, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.