Skip to main content
Glama

JS Reverse MCP

English | 中文

Ein AI-first / AI-natives JavaScript-Reverse-Engineering-MCP-Server, der deinen KI-Coding-Assistenten (wie Claude, Cursor, Copilot) in die Lage versetzt, wie ein Analyst kontinuierlich JavaScript-Verhalten im Browser zu debuggen, zu lokalisieren, zu speichern und nachzuvollziehen.

Es geht nicht darum, die Chrome-DevTools-API unverändert an das Modell weiterzureichen, sondern darum, Skripte, Breakpoints, Netzwerk, WebSocket, Browserzustand und lokale Datei-I/O so zu reorganisieren, dass sie für kontinuierliches Schlussfolgern und Handeln eines KI-Agenten geeignet sind. Anti-Erkennung ist Teil der Fähigkeiten: Standardmäßig wird ein speziell für dieses MCP neu kompilierter und unabhängig gepflegter Patchright-Fork verwendet, der Stealth auf Protokollebene bietet. Für starke Anti-Scraping-Seiten kann optional der CloakBrowser-Quellcode-Ebenen-Fingerabdruckmodus von CloakBrowser aktiviert werden.

☁️ 赞助 · Sponsored by IPWO

IPWO-Wohnproxys unterstützen flexible Proxy-Konfigurationen. Entwickler können je nach Aufgabe die passende Netzwerkumgebung wählen – für Webzugriff, Anfragetests, regionale Inhaltsanalyse und automatisierte Workflows.

Für Projekte mit JS-Reverse-Engineering, Browser-Debugging und Web-Netzwerkanalyse können Wohnproxys auch als ergänzende Netzwerkumgebungsoption dienen und Entwicklern helfen, Zugriffs- und Testanforderungen in verschiedenen Regionen flexibler zu erfüllen.

👉 Kostenloser Testzugang, 10 % Rabattcode: 0204

Related MCP server: MCP JS Debugger

☁️ 赞助 · Sponsored by Infistar.cc 无限星河

js-reverse-mcp × Infistar.cc 无限星河|Alle Modelle API · Stabiler Antrieb für KI-gestütztes Debugging

Vielen Dank an Infistar.cc 无限星河 für das Sponsoring und die Bereitstellung von Modellservice-Support für js-reverse-mcp!

  • ⚡ Bewältigt komplexe Debugging-Aufgaben stabil: Bietet unternehmensgerechte Hochkonkurrenz-Kanäle und Multi-Node-Redundanz, Preise ab 10 % der offiziellen Kanäle, reduziert Rate-Limits, 429-Fehler und Verbindungsabbrüche bei langen Aufgaben.

  • 🧠 Ein API-Key für gängige Modelle: Unterstützt ChatGPT, Claude, Gemini, Kimi, GLM, DeepSeek und andere Modelle, kompatibel mit Claude Code, Codex, Cursor und anderen KI-Programmiertools.

  • 🔎 Unterstützt autorisiertes Debugging und Sicherheitsforschung: Geeignet für mehrstufige Aufgaben wie Skriptsuche, Breakpoint-Analyse, Netzwerkanfrage-Tracking, Call-Stack-Prüfung und Code-Logik-Verständnis.

  • 📦 Exklusives Benefit für Projektnutzer: Über den exklusiven Partnerlink registrieren und den ersten Aufruf abschließen, um ein Testguthaben im Wert von 5 USD / ein exklusives Erstauflade-Angebot zu erhalten.

Positionierung: Unterstützung für Claude Code / Codex Modell-API-Konfiguration.

Funktionen

  • AI-native Tool-Design: Tool-Granularität, Ausgabegrenzen und Fehlermeldungen sind alle auf Agent-Entscheidungen ausgelegt, um das Modell nicht in ineffektive nächste Schritte zu treiben

  • Nachvollziehbare Workflows: Skriptquellcode, rohe Netzwerkdaten und Binärergebnisse können in lokale Dateien exportiert und als Eingabe für spätere Analysen verwendet werden

  • Breakpoint-Kontext-Ausführung: Beim Pausieren kann direkt im Call Frame ausgewertet, auf Scope-Variablen geprüft, schrittweise ausgeführt und der Quellcode-Kontext zurückgegeben werden

  • Skriptanalyse: Alle geladenen JS-Dateien auflisten, Code durchsuchen, Quellcode abrufen/speichern, große komprimierte Skripte automatisch formatieren

  • Netzwerk- und WebSocket-Analyse: Request-Call-Stacks, XHR-Breakpoints, Set-Cookie-Erkennung, Export von rohen Body/Header-Daten, WebSocket-Nachrichtengruppierung

  • Browserzustand-Wiedergabe: Cookies / Cache / Storage / sessionStorage der aktuellen Site bereinigen, kombiniert mit Reload zur Reproduktion von Cookie- und Risikokontroll-Abläufen

  • Standardmäßig mit Fenster + persistenter Login-Sitzung: Browser sichtbar, Cookies / localStorage bleiben über Sitzungen hinweg erhalten

  • Spezieller Patchright-Kern: Standardmäßig abhängig von einem unabhängig gepflegten Patchright-Fork dieses Projekts, der kontinuierlich bekannte Shared-Implementation-Merkmale des Upstreams behebt

  • Optionale Anti-Erkennungsschicht: Spezielles Patchright-Stealth auf Protokollebene standardmäßig aktiviert; für starke Anti-Scraping-Seiten kann --cloak mit CloakBrowser-Binärdatei hinzugefügt werden

Spezieller Patchright-Fork

js-reverse-mcp hängt nicht mehr direkt vom allgemeinen Patchright-Veröffentlichungspaket ab, sondern verwendet das speziell für dieses MCP kompilierte und veröffentlichte @zhizhuodemao/patchright. Dieser Fork wird in einem separaten Repository kontinuierlich gepflegt und entwickelt sich mit den tatsächlichen Erkennungsmustern dieses MCP weiter.

  • Keine direkte Abhängigkeit mehr vom allgemeinen Patchright-Veröffentlichungspaket

  • Anpassungen auf Protokollebene für bestätigte Shared-Implementation-Merkmale des Upstreams, neu kompiliert und veröffentlicht

  • Anti-Erkennungsanpassungen hängen nicht von JS-Injektion auf Seitenebene ab

  • Behält ursprüngliche Fähigkeiten wie evaluate, locator und Seitensteuerung bei

  • Der Fork wird kontinuierlich im speziellen Repository für dieses MCP gepflegt

Die öffentliche Dokumentation erläutert nur die Designgrenzen, nicht die internen Erkennungsmuster und Implementierungsdetails. Das Ziel des speziellen Forks ist es, bestätigte Shared-Implementation-Merkmale zu reduzieren, nicht eine absolute Nicht-Erkennbarkeit der Browserautomatisierung zu versprechen.

Systemanforderungen

Schnellstart (npx)

Keine Installation erforderlich, direkt in der MCP-Client-Konfiguration hinzufügen:

{
  "mcpServers": {
    "js-reverse": {
      "command": "npx",
      "args": ["js-reverse-mcp"]
    }
  }
}

Claude Code

claude mcp add js-reverse npx js-reverse-mcp

Wenn du noch kein nutzbares Modell-API hast oder eine benutzerdefinierte API-Adresse konfigurieren möchtest, findest du hier eine Anleitung: Claude Code / Codex Drittanbieter-Modell-API-Konfigurations-Tutorial.

Codex

codex mcp add js-reverse -- npx js-reverse-mcp

Wenn du noch kein nutzbares Modell-API hast oder eine benutzerdefinierte API-Adresse konfigurieren möchtest, findest du hier eine Anleitung: Claude Code / Codex Drittanbieter-Modell-API-Konfigurations-Tutorial.

Cursor

Gehe zu Cursor Settings -> MCP -> New MCP Server und verwende die obige Konfiguration.

VS Code Copilot

code --add-mcp '{"name":"js-reverse","command":"npx","args":["js-reverse-mcp"]}'

Lokale Installation (optional)

git clone https://github.com/zhizhuodemao/js-reverse-mcp.git
cd js-reverse-mcp
npm install
npm run build

Dann in der MCP-Konfiguration den lokalen Pfad verwenden:

{
  "mcpServers": {
    "js-reverse": {
      "command": "node",
      "args": ["/你的路径/js-reverse-mcp/build/src/index.js"]
    }
  }
}

AI-first Design

Das Kernziel dieses Projekts ist nicht „den Browser bedienen zu können", sondern dem KI-Agenten zu ermöglichen, eine echte JS-Reverse-Engineering-Aufgabe stabil abzuschließen: Seite öffnen, Risikokontrolle passieren, Skript lokalisieren, Quellcode speichern, Breakpoints setzen, Verhalten auslösen, Laufzeit prüfen, Netzwerkmaterial exportieren, Zustand reproduzieren und dann weiter schlussfolgern.

Mehrere Designausrichtungen ziehen sich durch den Code:

  • Tools sind Agent-Primitives, keine DevTools-Menü-Abbildungen: list_network_requests kann sowohl Indizes auflisten, als auch Details per reqid abfragen und präzise Materialien über outputFile exportieren; evaluate_script kann sowohl auf der Seite ausgeführt werden, als auch im Breakpoint-Call-Frame, und kann Eingaben über localFilePath empfangen.

  • Ausgaben müssen den nächsten Schritt leiten: Listenausgaben bleiben kurz und scanbar; Detailausgaben haben Grenzen; lange Ergebnisse weisen auf Export hin; pending Requests weisen klar darauf hin, zuerst die Ausführung fortzusetzen, damit der Agent nicht auf eine Response wartet, die nie kommt.

  • Lokale Dateien sind die Analyse-Workbench: save_script_source, list_network_requests(..., outputFile), evaluate_script(..., localFilePath) ermöglichen dem Agenten, zwischen Browser, Netzwerk und lokalen Dateien hin- und herzuwechseln, anstatt große Codeblöcke oder Binärdaten in den Chat-Kontext zu stopfen.

  • Zustand kann bereinigt, Abläufe können wiedergegeben werden: Das Standardprofil behält den Login-Zustand; --isolated bietet eine einmalige saubere Umgebung; clear_site_data löscht nur den zustandsbezogenen Status der aktuellen Site, um Cookie-Erzeugung, Risikokontroll-Initialisierung und Request-Ketten wiederholt zu reproduzieren.

  • Anti-Erkennung dient der Debugging-Kette: CDP-stille Navigation, echtes Viewport, Google-Referer, spezieller Patchright-Fork und CloakBrowser zielen alle darauf ab, dass der Agent in die Zielseite gelangen und die Analyse fortsetzen kann, nicht das Projekt in ein generisches Scraping-Framework zu verwandeln.

Anti-Erkennungsmechanismus (unterstützende Fähigkeit)

Anti-Erkennung ist eine der zugrunde liegenden unterstützenden Fähigkeiten von js-reverse-mcp. Die Wrapper-Schicht (dieses MCP selbst) hat null JS-Injektion und macht keine Object.defineProperty-Hacks (das wäre selbst ein Erkennungssignal). Alle Anti-Erkennung erfolgt in zwei sich nicht überlappenden Schichten:

Schicht

Standardmodus

--cloak-Modus

Protokollebene (CDP)

Spezieller Patchright-Fork: ruft Runtime.enable / Console.enable nicht auf, führt evaluate in der isolierten World aus, entfernt Automatisierungs-Launch-Flags und behebt kontinuierlich bekannte Shared-Implementation-Merkmale

Gleich

Quellcode-Ebene (C++-Binär-Patch)

Keine – verwendet direkt das System-Google-Chrome

CloakBrowser-Binärdatei (plattformspezifische Quellcode-Ebenen-Fingerabdruck-Patches, abdeckend navigator.webdriver, canvas, WebGL, audio, GPU, Fonts, Bildschirm, WebRTC, TLS)

Profilverzeichnis

~/.cache/chrome-devtools-mcp/chrome-profile (persistenter Login-Zustand)

~/.cache/chrome-devtools-mcp/cloak-profile (physisch vom Standard getrennt)

Tatsächlicher Browser

Dein installiertes Google Chrome (mit Web Store, Erweiterungen, Sync)

Benutzerdefinierte Chromium-Kompilierung (ohne Google-Dienste, ohne Web Store)

Zusätzlich einige Maßnahmen auf Navigationsebene (in beiden Modi wirksam):

  • CDP-stille Navigation – Bei Seitenladen wird Network.enable / Debugger.enable nicht aktiviert; Request-/Konsolen-Sammlung läuft nur über Playwright-Listener, bis ein Tool explizit CDP benötigt

  • Google-Referer – new_page bringt standardmäßig referer: https://www.google.com/ mit

  • Echtes Viewport – Das Playwright-Standard-Fake-Viewport von 1280×720 wird deaktiviert, der Browser zeigt die echte Bildschirmgröße

Wann --cloak aktivieren: Nur wenn das oben Genannte nicht ausreicht und die Site per Fingerabdruck blockiert. Details siehe docs/cloak.md.

Werkzeugliste (24 Stück)

Seite und Navigation

Werkzeug

Beschreibung

select_page

Offene Seiten auflisten oder per Index den Debugging-Kontext auswählen

new_page

Neue Seite erstellen und zu URL navigieren

navigate_page

Navigieren, zurück, vor oder Seite aktualisieren

select_frame

Alle Frames (iframes) auflisten oder Ausführungskontext auswählen

click_element

Streng abgleichen und auf ein einzelnes sichtbares Element im aktuellen Frame klicken

take_screenshot

Seiten-Screenshot aufnehmen

Skriptanalyse

Werkzeug

Beschreibung

list_scripts

Alle im Browser geladenen JavaScript-Skripte auflisten

get_script_source

Skriptquellcode-Ausschnitt abrufen, mit Zeilenbereich oder Zeichenoffset

save_script_source

Vollständigen Skriptquellcode in lokale Datei speichern (geeignet für große/komprimierte/WASM-Dateien)

search_in_sources

In allen Skripten nach Zeichenfolge oder regulärem Ausdruck suchen

Breakpoints und Ausführungssteuerung

Werkzeug

Beschreibung

set_breakpoint_on_text

Breakpoint automatisch durch Suche im Code-Text setzen (geeignet für komprimierten Code)

break_on_xhr

XHR/Fetch-Breakpoint nach URL-Muster setzen

remove_breakpoint

Breakpoints mit expliziter Aktion nach ID, URL oder alle entfernen

list_breakpoints

Alle aktiven Breakpoints auflisten

get_paused_info

Pausenzustand, Call-Stack und Scope-Variablen abrufen

pause_or_resume

Mit expliziter Aktion pausieren oder fortsetzen

step

Schrittweises Debugging (over/into/out), gibt Position und Quellcode-Kontext zurück

Netzwerk und WebSocket

Werkzeug

Beschreibung

list_network_requests

Netzwerkanfragen auflisten, Details anzeigen oder rohe Materialien wie Header/Body/Query exportieren

clear_network_requests

Nach expliziter Bestätigung gesammelte Requests und Body-Cache der aktuellen Seite leeren

get_request_initiator

JavaScript-Call-Stack einer Netzwerkanfrage abrufen

get_websocket_messages

WebSocket-Verbindungen auflisten, Nachrichtenmuster analysieren oder Nachrichtendetails abrufen

Browserzustand

Werkzeug

Beschreibung

clear_site_data

Cookies, Origin-Storage und sessionStorage der aktuellen Site bereinigen; globalen HTTP-Cache kann explizit ausgewählt werden

Inspektionswerkzeuge

Werkzeug

Beschreibung

evaluate_script

JavaScript auf der Seite oder im Breakpoint-Kontext ausführen, unterstützt Main World, Speichern von Ergebnissen und Lesen einer lokalen Eingabedatei

list_console_messages

Konsolenmeldungen auflisten oder Einzeldetails per msgid abrufen

Verwendungsbeispiele

Grundlegender JS-Reverse-Engineering-Ablauf

  1. Zielseite öffnen

打开 https://example.com 并列出所有加载的 JS 脚本
  1. Zielfunktion finden

在所有脚本中搜索包含 "encrypt" 的代码
  1. Breakpoint setzen

在加密函数入口处设置断点
  1. Auslösen und analysieren

在页面上触发操作,断点命中后检查参数、调用栈和作用域变量

WebSocket-Protokollanalyse

列出 WebSocket 连接,分析消息模式,查看特定类型的消息内容

Vom Agenten empfohlener vollständiger Erfassungsablauf

Da die Navigationsphase bewusst CDP-still gehalten wird, werden beim ersten Betreten der Zielseite die Network-/Debugger-Domänen nicht sofort geöffnet. Empfohlener Ablauf: Erst Risikokontrolle passieren, dann per Refresh erfassen:

1. new_page 打开目标页
2. 调用 list_network_requests 激活 collectors
3. navigate_page(type="reload") 刷新页面
4. 再次 list_network_requests 查看完整请求
5. 对关键 reqid 使用 outputFile 导出原始材料
1. clear_site_data(confirm=true) 清理当前站点状态
2. navigate_page(type="reload") 重新触发初始化
3. list_network_requests 找到设置 cookie 或提交 sensor 的请求
4. 导出 requestBody / responseHeaders / responseBody
5. 用 evaluate_script + localFilePath 在页面上下文中复算或验证

Konfigurationsoptionen

Die CLI bleibt schlank, alle Flags sind optional. Für 99 % der Szenarien reicht der Standard. Bei lokalen Dateien wird empfohlen, mit --allowedRoots die Verzeichnisse einzuschränken, die der Agent lesen und schreiben darf.

Option

Beschreibung

Standardwert

--cloak

Auf CloakBrowser-Stealth-Binärdatei umschalten (ersetzt System-Chrome). Aktiviert plattformspezifische C++-Quellcode-Ebenen-Fingerabdruck-Patches. Beim ersten Start werden automatisch ~200MB Binärdateien heruntergeladen; die Fingerabdruck-Identität wird pro Profil persistiert. Details siehe docs/cloak.md.

false

--isolated

Temporäres user-data-dir verwenden (Cookies/localStorage werden nicht behalten, beim Schließen automatisch bereinigt)

false

--browserUrl, -u

Mit einer bereits laufenden Chrome-Instanz verbinden (CDP-HTTP-Endpunkt, z. B. http://127.0.0.1:9222). Das MCP erkennt automatisch die WebSocket-Debugger-URL. Wie du diesen Endpunkt bei lokalem Chrome, AdsPower, BitBrowser usw. erhältst, siehe docs/cdp-endpoint.md.

–

--logFile

MCP-Debug-Log in normale Datei mit 0600 schreiben; detaillierte Logs nur mit DEBUG=mcp:*. Verwende nicht DEBUG=*, Browser-Protokoll-Logs können Seiten, Cookies, Skripte und Anmeldedaten leaken.

–

--allowedRoots

Wiederholbar angeben, welche lokalen Verzeichnisse der Agent lesen und schreiben darf; echte Pfade auflösen und Symlink-Ausbrüche ablehnen. Wenn aktiviert, werden file:-, view-source:file:- und filesystem:file:-Browserseiten deaktiviert. Wenn nicht angegeben, ist der lokale Dateizugriff nicht verzeichnisbeschränkt; beim Start wird eine Sicherheitswarnung ausgegeben.

–

Beispielkonfigurationen

Standard – System-Chrome + persistenter Login-Zustand (für die meisten Debugging-Szenarien empfohlen):

{
  "mcpServers": {
    "js-reverse": {
      "command": "npx",
      "args": ["js-reverse-mcp"]
    }
  }
}

--cloak – starke Anti-Scraping-Seiten (Cloudflare Turnstile / DataDome / FingerprintJS-Schutz):

Dringend empfohlen: Binärdateien vorab herunterladen (einmalig, ~30–60 Sekunden). Wenn du diesen Schritt nicht machst, lädt der erste Start des MCP mit --cloak still ~200MB herunter, was wie ein eingefrorenes MCP aussieht:

npx cloakbrowser install

(Das cloakbrowser-Paket wird bereits über optionalDependencies mitinstalliert; dieser Befehl löst nur dessen eingebaute Binärdatei-Download-Logik aus, mit Fortschrittsbalken)

{
  "mcpServers": {
    "js-reverse-cloak": {
      "command": "npx",
      "args": ["js-reverse-mcp", "--cloak"]
    }
  }
}

Zwei parallele Instanzen – zwei MCP-Instanzen mit physisch getrennten Profilen, je nach Zielseite umschalten:

{
  "mcpServers": {
    "js-reverse": {
      "command": "npx",
      "args": ["js-reverse-mcp"]
    },
    "js-reverse-cloak": {
      "command": "npx",
      "args": ["js-reverse-mcp", "--cloak"]
    }
  }
}

--isolated – jedes Mal ein frisches Profil (Cookies/localStorage werden nicht behalten):

{
  "mcpServers": {
    "js-reverse": {
      "command": "npx",
      "args": ["js-reverse-mcp", "--isolated"]
    }
  }
}

Mit laufendem Chrome / Drittanbieter-Fingerprint-Browser verbinden

--browserUrl akzeptiert nur CDP-Endpunkte (HTTP-Endpunkte, die auf /json/version antworten), keine herstellerspezifischen privaten Local-APIs. Wie du den CDP-Port bei lokalem Chrome, AdsPower, BitBrowser usw. erhältst, findest du in der speziellen Dokumentation:

📖 docs/cdp-endpoint.md – So erhältst du den CDP-Debugging-Port

Kürzester Weg (lokales Chrome):

# 先关掉所有 Chrome 窗口,然后
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
  --remote-debugging-port=9222 --user-data-dir=/tmp/chrome-debug
{
  "mcpServers": {
    "js-reverse": {
      "command": "npx",
      "args": ["js-reverse-mcp", "--browserUrl", "http://127.0.0.1:9222"]
    }
  }
}

Der CDP-Port von Fingerprint-Browsern (AdsPower, BitBrowser usw.) ändert sich bei jedem Start zufällig. Du musst den Browser zuerst über die herstellerspezifische Local-API starten und dann den Port extrahieren. Die Schritte und Beispielskripte findest du in der oben genannten Dokumentation.

Fehlerbehebung

Von Anti-Scraping-Systemen blockiert

Wenn der Zugriff auf bestimmte Seiten blockiert wird (z. B. Zhihu gibt 40362 zurück, Cloudflare-Challenge-Endlosschleife):

  1. Zuerst --isolated probieren – mit frischem Profil Restzustands-Verschmutzung ausschließen:

    "args": ["js-reverse-mcp", "--isolated"]
  2. Wenn das nicht reicht, --cloak aktivieren – plattformspezifische Quellcode-Ebenen-Fingerabdruck-Patches aktivieren:

    "args": ["js-reverse-mcp", "--cloak"]
  3. Zuletzt das persistente Profil manuell löschen (Login-Zustand geht verloren):

    rm -rf ~/.cache/chrome-devtools-mcp/chrome-profile

Wann --cloak aktiviert werden sollte und wann nicht, findest du in docs/cloak.md.

Agent-Routing-Evaluation (Maintainer)

npm run eval:routing:validate prüft offline die tatsächliche MCP-tools/list, Server-Instructions und die 30 Tool-Auswahl-Verträge in evals/tool-routing.json; dieser Befehl greift nicht auf Modell-Endpunkte zu und ist in den Presubmit aufgenommen.

Die echte Modell-Evaluation ist explizit opt-in und ruft einzeln OpenAI-kompatible Chat-Completions-Endpunkte auf, was Kosten verursachen kann:

MCP_ROUTING_EVAL_ENDPOINT=https://api.example.com/v1/chat/completions \
MCP_ROUTING_EVAL_MODEL=model-name \
MCP_ROUTING_EVAL_API_KEY=secret \
npm run eval:routing

MCP_ROUTING_EVAL_API_KEY kann bei lokalen Endpunkten ohne Authentifizierung weggelassen werden; Remote-Endpunkte mit Anmeldedaten müssen HTTPS verwenden, HTTP ist nur für Loopback erlaubt. Mit MCP_ROUTING_EVAL_TIMEOUT_MS kann das Timeout für einzelne Requests angepasst werden. Standardmäßig wird 100 % Durchlaufquote verlangt; beim Vergleich über Modelle hinweg kann mit MCP_ROUTING_EVAL_MIN_PASS_RATE ein Schwellenwert in (0, 1] gesetzt werden. Die Evaluation gibt keine API-Keys, Endpunkte oder Fehlerantwort-Bodys von Endpunkten aus.

Sicherheitshinweis

Dieses Tool setzt Browserinhalte dem MCP-Client aus und erlaubt das Prüfen, Debuggen und Ändern beliebiger Daten im Browser. Verwende es nicht auf Seiten mit sensiblen Informationen.

evaluate_script.localFilePath sowie verschiedene outputFile/filePath-Optionen bewirken, dass der MCP-Prozess Dateien auf dem Hostsystem liest oder schreibt. In Produktions- oder gemeinsam genutzten Umgebungen sollte der Zugriff mithilfe eines oder mehrerer --allowedRoots auf ein dediziertes Arbeitsverzeichnis eingeschränkt werden; ohne Konfiguration ist der Zugriffsbereich uneingeschränkt. Nach Aktivierung von --allowedRoots werden auch die Browser-Seiten file:, view-source:file: und filesystem:file: abgelehnt, um zu verhindern, dass Verzeichnisgrenzen durch Browser-Navigation umgangen werden. Falls lokale Seiten debuggt werden müssen, sollte diese Option nur in Sitzungen nicht konfiguriert werden, in denen das Risiko der Offenlegung lokaler Dateien ausdrücklich akzeptiert wird.

Lizenz

Apache-2.0

Available Tools

24 tools
break_on_xhrA

Sets a URL-substring breakpoint for a future XHR/Fetch when runtime request arguments, local variables, or payload construction must be inspected. For an already captured request, call get_request_initiator first because it is non-pausing; use this only when that evidence is insufficient. Set it before reproducing the user action—it does not inspect past traffic—then call get_paused_info/evaluate_script and finally step or resume. The URL pattern identifies this breakpoint for list_breakpoints and remove_breakpoint(action="remove_xhr").

NameRequiredDescriptionDefault
urlYesCase-sensitive URL substring matched against future XHR/Fetch requests. Prefer a narrow endpoint path from list_network_requests; retain the exact string to remove the breakpoint later.

Output Schema

NameRequiredDescription
okYesWhether the tool completed successfully.
dataNoMachine-readable result payload.
toolYesStable MCP tool name.
errorNo
summaryYesConcise human-readable outcome.
clear_network_requestsA
DestructiveIdempotent

Discard captured HTTP(S) evidence for the currently selected page after confirm=true. Use this immediately before reproducing an action when a clean network capture window is needed; do not use it to reset login, cookies, cache, or other browser state. It irreversibly clears the in-memory request queue, cached response bodies, and initiator maps only. Browser cookies, HTTP cache, origin storage, console messages, and WebSocket connections/messages are unchanged; use clear_site_data for cookie and storage reset. New captures continue above the previous reqid high-water mark because reqids are never reused.

NameRequiredDescriptionDefault
confirmNoMust be true to irreversibly delete the selected page's captured request history, response-body cache, and initiator evidence. This confirms capture cleanup, not browser-state cleanup.

Output Schema

NameRequiredDescription
okYesWhether the tool completed successfully.
dataNoMachine-readable result payload.
toolYesStable MCP tool name.
errorNo
summaryYesConcise human-readable outcome.
clear_site_dataA
DestructiveIdempotent

Irreversibly clear browser state after confirm=true to create a clean replay environment for the selected page. Use this before replaying login, session creation, storage initialization, or other state-dependent flows; do not use it to inspect cookies or determine which response set one. For cookie provenance, including HttpOnly, Secure, and SameSite attributes, use list_network_requests with cookieName first. Cleanup covers cookies affecting the selected page's HTTP(S) frames—including HttpOnly and Secure cookies through the browser context—persistent storage for those frame origins, and each HTTP(S) frame's sessionStorage. It does not reload the page. The browser HTTP cache is global and is preserved by default; set clearBrowserCache=true only when that wider cross-page effect is explicitly intended.

NameRequiredDescriptionDefault
confirmNoMust be true to irreversibly delete cookies affecting the selected page's HTTP(S) frames, persistent storage for those frame origins, and HTTP(S) frame sessionStorage. This confirms state reset for replay, not inspection.
clearBrowserCacheNoAlso clear the browser-wide HTTP cache. Leave false for site-scoped replay cleanup. Setting true has a wider global effect on every page and origin in this browser, not only the selected page or its frame origins.

Output Schema

NameRequiredDescription
okYesWhether the tool completed successfully.
dataNoMachine-readable result payload.
toolYesStable MCP tool name.
errorNo
summaryYesConcise human-readable outcome.
click_elementA
Destructive

Performs one verified, auditable click in the currently selected frame. Use it when the task requires activating a known button, link, or control after selecting the correct page/frame and identifying a CSS selector; it is the preferred minimal interaction primitive over arbitrary evaluate_script code. It does not discover elements, type text, or silently guess among matches: the selector must resolve to exactly one element unless index is explicit, and the chosen element must be visible. A click can submit data, navigate, or trigger external effects, so confirm=true is required and the result reports the exact resolved element.

NameRequiredDescriptionDefault
indexNoExplicit zero-based match index. Required when the selector matches more than one element.
buttonNoMouse button. Defaults to left.left
confirmNoMust be true to authorize this specific click because it can submit data, navigate, or trigger external side effects.
timeoutNoMaximum wait time in milliseconds. If set to 0, the default timeout will be used.
selectorYesCSS selector evaluated only in the currently selected frame. Use select_frame first when the target is inside an iframe.
modifiersNoOptional keyboard modifiers held during the click.

Output Schema

NameRequiredDescription
okYesWhether the tool completed successfully.
dataNo
toolYesStable MCP tool name.
errorNo
summaryYesConcise human-readable outcome.
evaluate_scriptA
Destructive

Evaluates one focused JavaScript function for DOM/page state, web storage, page-defined globals, a paused-frame expression, or browser-side processing of one local file. Use it when those runtime values are the goal and no narrower evidence tool applies. Do not use document.cookie or page evaluation to investigate HttpOnly/Secure cookies, Set-Cookie provenance, or captured HTTP evidence; use list_network_requests with cookieName/reqid, and use search_in_sources/get_script_source for source discovery. While running, evaluation uses the selected frame's isolated world by default or its page main world with mainWorld=true; while paused, it always uses the chosen call frame and ignores mainWorld. Call get_paused_info before paused evaluation, then step or resume when finished. Arbitrary code can change page/external state and requires confirm=true; inline results are bounded, so use outputFile for exact large or binary results.

NameRequiredDescriptionDefault
confirmNoMust be true to authorize this exact arbitrary-code evaluation, which may mutate page state, send requests, or cause external side effects. Prefer a read-only expression when inspection is sufficient.
functionYesJavaScript function declaration invoked by the tool, for example `() => document.title` or `async () => await Promise.resolve(location.href)`. Return JSON-serializable data; ArrayBuffer/typed arrays require outputFile for exact bytes. With localFilePath, accept `async ({localFile}) => ...` and read localFile.text for UTF-8 or localFile.base64 for exact bytes. Keep the function focused; use mainWorld=true only when page-defined globals are required.
mainWorldNoRunning-page mode only: false uses the selected frame's isolated context; true uses that frame's page main world to access application-defined globals. When execution is paused, evaluation always targets frameIndex and this option is ignored.
frameIndexNoPaused mode only: zero-based call frame from get_paused_info (default: top frame). The index and its callFrameId expire after any step or resume.
outputFileNoSave the exact result locally instead of returning bounded inline content. JSON-serializable values are written as JSON text and ArrayBuffer/typed arrays as raw bytes; the returned filename is resolved and subject to --allowedRoots.
localFilePathNoAbsolute path to one host file passed as localFile; the browser never reads the path directly. Relative paths, file:// URLs, globs, ~, and directories are rejected, access is subject to --allowedRoots, and file contents may expose sensitive host data.
confirmOverwriteNoSet true only to authorize replacing an existing outputFile. A new file does not require overwrite confirmation.

Output Schema

NameRequiredDescription
okYesWhether the tool completed successfully.
dataNo
toolYesStable MCP tool name.
errorNo
summaryYesConcise human-readable outcome.
get_paused_infoA
Read-only

Inspects the current call stack, source locations, and selected call-frame scopes after a code/XHR breakpoint or explicit pause has stopped execution. It neither creates a pause nor resumes one. Returned frameIndex values and callFrameIds belong only to the current pause and expire after any step or resume; use evaluate_script with frameIndex for a focused expression, then step or pause_or_resume(action="resume").

NameRequiredDescriptionDefault
frameIndexNoZero-based frame from this pause whose scopes should be read (default: top frame). Frame indices change after a step and expire on resume.
includeScopesNoInclude bounded variables from the selected call frame (default: true). Set false when only the stack and source locations are needed.
maxScopeDepthNoScope categories to include for frameIndex (default: 2): 1 reads arguments/locals, 2 also reads closures, and 3+ includes other non-global scopes. Increase only when the needed value is absent.

Output Schema

NameRequiredDescription
okYesWhether the tool completed successfully.
dataNo
toolYesStable MCP tool name.
errorNo
summaryYesConcise human-readable outcome.
get_request_initiatorA
Read-only

Non-pausing first action for tracing which JavaScript initiated a retained HTTP request when CDP initiator evidence was active. Pass the reqid from list_network_requests; because initiator capture starts lazily and is not retroactive, an older request may have no stack—in that case reproduce the action and inspect the new reqid, or set break_on_xhr before reproduction when runtime values are required. If the captured stack identifies the code, inspect its URL/location with get_script_source. If arguments, locals, or a dynamically built payload are still needed, use break_on_xhr, reproduce, then call get_paused_info or evaluate_script before stepping or resuming. This tool only reads retained evidence and does not pause or reproduce the request.

NameRequiredDescriptionDefault
requestIdYesNumeric reqid returned by list_network_requests, not a raw CDP request ID. It survives navigation while retained, but becomes stale after FIFO eviction or clear_network_requests; list requests again if needed.

Output Schema

NameRequiredDescription
okYesWhether the tool completed successfully.
dataNoMachine-readable result payload.
toolYesStable MCP tool name.
errorNo
summaryYesConcise human-readable outcome.
get_script_sourceA
Read-only

Reads a small source region around a search match, paused location, or known statement without executing or pausing the page. Select by URL when available because URL-backed scripts can be resolved again after navigation; use the debugger-context-scoped scriptId only for current inline/eval scripts. Use line ranges for normal source and offset/length for minified single-line bundles. For a whole, minified, or WASM source, use save_script_source; to observe runtime values next, call set_breakpoint_on_text against the original loaded source.

NameRequiredDescriptionDefault
urlNoURL from list_scripts, search_in_sources, or a call stack. Preferred stable selector for URL-backed scripts; resolution tries an exact match before a substring match, so provide enough of the URL to avoid ambiguity.
lengthNoMaximum characters to return from offset (default: 1000). This is ignored unless offset is provided.
offsetNoZero-based character offset into the original source. Use for a bounded read of minified single-line code when line ranges would be too large.
endLineNoInclusive 1-based end line for a bounded multi-line snippet. Omit both line bounds and use offset/length for a minified single-line bundle.
scriptIdNoDebugger-context-scoped script ID from list_scripts, search_in_sources, or paused information. Required for unnamed inline/eval scripts, but invalid after reload, navigation, or debugger target/frame change; prefer url for external scripts.
startLineNoInclusive 1-based start line, typically copied from search_in_sources or paused information. Use with endLine for normal multi-line source.

Output Schema

NameRequiredDescription
okYesWhether the tool completed successfully.
dataNoMachine-readable result payload.
toolYesStable MCP tool name.
errorNo
summaryYesConcise human-readable outcome.
get_websocket_messagesA
Read-only

Inspect captured bidirectional WebSocket connections and frame payloads for the selected page. Use this for WebSocket, socket, live-update, push, streaming, or realtime message flows; use list_network_requests for ordinary HTTP/XHR/fetch traffic and WebSocket upgrade request headers. WebSocket capture starts lazily on this tool's first use and is not retroactive: if the relevant socket already connected or exchanged frames, call this tool once to initialize capture, then reload or reproduce the flow. Without wsid it lists connections so you can choose one. With wsid it lists paginated sent/received frames; add show_content=true for payload previews. With wsid and analyze=true it groups frames by payload pattern and returns group IDs and sample frame indices; then use groupId to inspect one pattern. With wsid and frameIndex it returns one retained frame's detailed payload using the stable index shown in frame tables or analysis samples.

NameRequiredDescriptionDefault
wsidNoSelect a WebSocket connection by the wsid returned from connection-list mode. Omit it to list captured connections before inspecting their frames.
analyzeNoWith wsid, group retained frames by payload pattern/fingerprint. Use this to discover message types in noisy realtime traffic; it returns traffic statistics, group IDs, and sample stable frame indices. Follow with groupId or frameIndex for focused inspection.
groupIdNoWith wsid, list only frames from a pattern group such as A, B, or C. Run analyze=true first to discover group IDs. If analysis used direction, repeat the same direction because grouping is computed over that filtered frame set.
pageIdxNoZero-based page for the active connection-list, frame-list, group-list, or analysis-group mode. Omit it for the first page.
pageSizeNoItems per page: connections when wsid is omitted, frames in normal/group mode, or pattern groups when analyze=true. Defaults to 10.
directionNoWith wsid, restrict frame-list, analysis, or group results to frames "sent" by the page or "received" from the server. It does not filter connection-list mode.
urlFilterNoIn connection-list mode only (without wsid), return WebSocket URLs containing this substring. Use it to narrow by host, path, or query text.
frameIndexNoWith wsid, return one retained frame and its payload by stable frame index. This is the Idx shown in frame tables or analyze=true samples, not a page-relative array offset. Indices are monotonic and may begin above 0 after older frames are evicted.
show_contentNoWith wsid in normal or group frame-list mode, include payload previews up to 10,000 characters for frames on the current page. Leave false for compact metadata, or use frameIndex when one exact frame needs detailed inspection.
includePreservedConnectionsNoIn connection-list mode only (without wsid), include connections preserved from the last three navigations. Use this when the relevant socket belonged to a previous page state.

Output Schema

NameRequiredDescription
okYesWhether the tool completed successfully.
dataNo
toolYesStable MCP tool name.
errorNo
summaryYesConcise human-readable outcome.
list_breakpointsA
Read-only

Inspects code and XHR/Fetch breakpoints managed by this MCP session before reproducing an action or cleaning up debugger state. Returns current code breakpointIds and the exact XHR URL patterns needed by remove_breakpoint; URL-backed definitions are restored after navigation when possible, but a rebuilt debugger session may assign new IDs. This does not show why or where execution is currently paused—use get_paused_info for the active call stack.

NameRequiredDescriptionDefault
pageIdxNoPage number (0-based). Defaults to 0.
pageSizeNoMaximum items per page. Defaults to 20.

Output Schema

NameRequiredDescription
okYesWhether the tool completed successfully.
dataNo
toolYesStable MCP tool name.
errorNo
summaryYesConcise human-readable outcome.
list_console_messagesA
Read-only

Inspects console messages and uncaught page errors captured for the selected page. Use it to diagnose runtime failures, warnings, application logs, or values already emitted by page code; use search_in_sources for source text and list_network_requests for HTTP evidence instead. Without msgid it lists messages 20 per page by default, optionally filtered by type or retained navigation history. With msgid it returns one message by its stable ID for focused inspection. Capture begins when this MCP attaches and is not retroactive, so reload or reproduce code that logged before attachment.

NameRequiredDescriptionDefault
msgidNoStable message ID returned by list mode. Pass it to inspect one captured console message; omit it to list messages.
typesNoConsole levels/types to include in list mode, such as error, warn, log, or trace. Values are OR-ed; omit or pass an empty array for all types.
pageIdxNoPage number to return (0-based). When omitted, returns the first page.
pageSizeNoMaximum number of messages to return. Defaults to 20.
includePreservedMessagesNoInclude retained console messages from the last 3 navigations. Leave false when only the current page load is relevant.

Output Schema

NameRequiredDescription
okYesWhether the tool completed successfully.
dataNo
toolYesStable MCP tool name.
errorNo
summaryYesConcise human-readable outcome.
list_network_requestsA

Inspect captured HTTP(S) traffic for the currently selected page. Use this for API calls, request or response headers and bodies, redirects, authentication/session flows, replay or signing inputs, and determining which response created, refreshed, rotated, overwritten, or deleted a cookie. Without reqid it lists and filters requests; with cookieName it traces exact response Set-Cookie updates oldest-first, including cookies with HttpOnly, Secure, or SameSite attributes that page JavaScript cannot fully inspect; with reqid it returns bounded request details; with reqid plus outputFile it exports exact data. To inspect complete Set-Cookie values and attributes, export outputPart="responseHeaders" for a reqid returned by cookieName mode. cookieName never searches outbound Cookie request headers. Use get_websocket_messages for WebSocket frame payloads; this tool only represents the HTTP upgrade request. Capture begins when this MCP attaches and is not retroactive, so reload or reproduce traffic that occurred earlier. Captures then survive navigation in a 5000-request FIFO queue. List and cookie-flow modes default to 20 items per page; filters combine with AND and multiple values inside one filter combine with OR.

NameRequiredDescriptionDefault
reqidNoInspect one captured request by the reqid returned by request-list or cookie-flow mode. Omit it to list/filter requests or trace cookie setters. Add outputFile when exact, complete, or large data is needed.
methodsNoFilter requests by HTTP method (the request verb). Matched case-insensitively. Pass one or more of GET, POST, PUT, DELETE, PATCH, HEAD, OPTIONS; multiple values are OR-ed (e.g. ["POST"] shows only POSTs, ["GET","POST"] shows both). Use this to hunt for submissions (POST/PUT/PATCH) versus reads (GET). This is the HTTP verb, distinct from resourceTypes which filters by resource category (xhr, document, ...). When omitted or empty, methods are not filtered.
pageIdxNoZero-based page to return in request-list or cookie-flow mode. Omit it for the first page.
pageSizeNoMaximum requests or Set-Cookie updates per page in list or cookie-flow mode. Defaults to 20.
urlFilterNoFilter request-list results to URLs containing this substring. Use an endpoint path, host, query fragment, or other known URL text; combine with methods/resourceTypes to narrow an API flow.
cookieNameNoTrace an exact cookie name in response Set-Cookie headers. Use this when asked where, when, or by which response a cookie was created, refreshed, rotated, overwritten, or deleted, including HttpOnly cookies and cookies carrying Secure or SameSite attributes. Matching setter responses are returned oldest-first with reqids and use pageSize/pageIdx. Export outputPart="responseHeaders" for a returned reqid to inspect the complete value and Path, Domain, HttpOnly, Secure, SameSite, Expires, or Max-Age attributes. This mode does not search outbound Cookie request headers.
outputFileNoWith reqid, save selected network data to a local file. Use export instead of bounded inline details for complete Set-Cookie headers, exact bytes, large or binary bodies, long query payloads, replay/signature inputs, or external decoding. Absolute paths and paths relative to the current working directory are supported. The response reports the resolved absolute path; use it with evaluate_script localFilePath for browser-side processing. Subject to --allowedRoots when configured.
outputPartNoSelect what outputFile receives for the chosen reqid. Use "responseHeaders" for complete cookie attributes and repeated Set-Cookie headers, "responseBody" for raw response bytes, "requestBody" for captured request bytes, "queryParams" for parsed URL parameters, or "all" for a JSON bundle of metadata, headers, query parameters, and body content/metadata. Defaults to "all".all
resourceTypesNoFilter requests to only return requests of the specified resource types (xhr, fetch, document, script, ...). This is the resource category, NOT the HTTP verb — use methods for GET/POST filtering. When omitted or empty, returns all requests.
confirmOverwriteNoMust be true when outputFile already exists. New files do not require confirmation.

Output Schema

NameRequiredDescription
okYesWhether the tool completed successfully.
dataNo
toolYesStable MCP tool name.
errorNo
summaryYesConcise human-readable outcome.
list_scriptsA
Read-only

Discovers JavaScript currently loaded in the selected debugger context—the main frame by default, or the frame chosen with select_frame. Use select_frame first for iframe-specific source/debugger work. Includes external, inline, and eval scripts in that context; if you already know a function name, endpoint, or code literal, use search_in_sources instead. Each result includes a context-scoped scriptId that expires on reload, navigation, or debugger target change and, for external scripts, a URL that is the preferred selector for get_script_source or save_script_source.

NameRequiredDescriptionDefault
filterNoCase-insensitive URL substring used to narrow external scripts. It does not search source text or match unnamed inline/eval scripts; use search_in_sources for code-content queries.
pageIdxNoPage number (0-based). Defaults to 0.
pageSizeNoMaximum items per page. Defaults to 20.

Output Schema

NameRequiredDescription
okYesWhether the tool completed successfully.
dataNo
toolYesStable MCP tool name.
errorNo
summaryYesConcise human-readable outcome.
new_pageA

Opens a separate browser page for a URL, reusing an existing about:blank startup tab when available. Use this when the task needs another tab or should preserve the currently selected page; use navigate_page to change the URL in the existing selected page instead. It waits for DOMContentLoaded, not every background resource, and then makes the opened page the target for later tools. It preserves cookies, storage, cache, and other browser state; use clear_site_data separately when a clean replay is required.

NameRequiredDescriptionDefault
urlYesAbsolute URL to load in a separate or reusable blank page. Use navigate_page instead when the current selected page should be reused.
timeoutNoMaximum wait time in milliseconds. If set to 0, the default timeout will be used.

Output Schema

NameRequiredDescription
okYesWhether the tool completed successfully.
dataNoMachine-readable result payload.
toolYesStable MCP tool name.
errorNo
summaryYesConcise human-readable outcome.
pause_or_resumeA

Explicitly requests an immediate pause or resumes an existing paused execution; it never toggles implicitly. Use a code breakpoint or break_on_xhr instead when a specific statement/request should stop, and use get_paused_info before resuming if evidence must be collected. Resuming invalidates current callFrameIds and frame indices.

NameRequiredDescriptionDefault
actionYesUse "pause" only while running, or "resume" only after a breakpoint/manual pause. Resume after get_paused_info/evaluate_script/step inspection is complete.

Output Schema

NameRequiredDescription
okYesWhether the tool completed successfully.
dataNoMachine-readable result payload.
toolYesStable MCP tool name.
errorNo
summaryYesConcise human-readable outcome.
remove_breakpointA
DestructiveIdempotent

Removes a known code breakpoint, XHR/Fetch breakpoint, or every MCP-managed breakpoint after explicit confirmation. Use breakpointId from set_breakpoint_on_text/list_breakpoints for remove_code, or reuse the exact URL pattern from break_on_xhr/list_breakpoints for remove_xhr. Removal does not resume an already paused page; call pause_or_resume(action="resume") separately after inspection.

NameRequiredDescriptionDefault
urlNoExact URL substring pattern previously passed to break_on_xhr or returned by list_breakpoints. Used only with action="remove_xhr".
actionYesRequired removal mode: remove_code needs breakpointId, remove_xhr needs url, and remove_all removes both kinds.
confirmNoMust be true to authorize the selected removal action. This does not authorize or trigger resuming execution.
breakpointIdNoCurrent breakpoint ID returned by set_breakpoint_on_text or list_breakpoints. Used only with action="remove_code"; list again after a debugger/page-session rebuild because restoration may assign a new ID.

Output Schema

NameRequiredDescription
okYesWhether the tool completed successfully.
dataNoMachine-readable result payload.
toolYesStable MCP tool name.
errorNo
summaryYesConcise human-readable outcome.
save_script_sourceA

Saves one complete JavaScript or WASM source for local inspection when an inline snippet is insufficient, especially for large or minified bundles. Prefer get_script_source for a small known region and search_in_sources to locate text across loaded scripts first. With format=true, destinations using a supported JavaScript/TypeScript extension are formatted by default; other extensions preserve raw source, and formatted line numbers may differ from the live page. Use distinctive text plus the original URL with set_breakpoint_on_text for runtime debugging. The returned filename is the resolved local path, while scriptId remains scoped to the current debugger context.

NameRequiredDescriptionDefault
urlNoURL from list_scripts, search_in_sources, or a call stack. Preferred over scriptId because it can be resolved again after navigation; exact match is tried before substring match.
formatNoFormat supported JavaScript/TypeScript extensions for readability (default: true). Set false when exact source bytes or original line layout matter; formatted line numbers cannot be used as live breakpoint locations.
filePathYesDestination path for the complete source, absolute or relative to the server working directory and subject to --allowedRoots. A JavaScript/TypeScript extension enables formatting; use .wasm for bytecode or another extension to preserve raw text.
scriptIdNoDebugger-context-scoped script ID from list_scripts or search_in_sources. Use for unnamed inline/eval scripts; it becomes invalid after reload, navigation, or debugger target/frame change.
confirmOverwriteNoSet true only to authorize replacing an existing filePath. A new file does not require overwrite confirmation.

Output Schema

NameRequiredDescription
okYesWhether the tool completed successfully.
dataNoMachine-readable result payload.
toolYesStable MCP tool name.
errorNo
summaryYesConcise human-readable outcome.
search_in_sourcesA
Read-only

Finds a known function name, endpoint, string literal, token, or code pattern in JavaScript loaded by the selected debugger context—the main frame by default, or the frame chosen with select_frame. It searches external, inline/eval, and minified sources in that context without executing or pausing the page, returning 1-based lines plus context-scoped scriptIds; URLs are the preferred selectors for URL-backed matches. Use select_frame first for iframe-specific source work, get_script_source for nearby context, save_script_source for a whole bundle, or set_breakpoint_on_text when runtime values are needed. For a known captured request, prefer get_request_initiator before a broad source search.

NameRequiredDescriptionDefault
queryYesSource text to locate, or a regular-expression pattern when isRegex=true. Prefer a distinctive function name, endpoint, property, or literal that can also anchor set_breakpoint_on_text.
isRegexNoInterpret query as a regular expression when true. Leave false for literal endpoint, token, and code-text searches.
urlFilterNoCase-insensitive script-URL substring used to narrow matches to a known bundle or domain. It excludes unnamed inline/eval scripts.
maxResultsNoMaximum matches to return (default: 30). Narrow with urlFilter before increasing this for common text.
caseSensitiveNoMatch case exactly when true. Leave false for discovery; set true when choosing exact code text for a breakpoint.
maxLineLengthNoMaximum characters in each matched-line preview (default: 150). Use get_script_source rather than a very large preview when surrounding context is needed.
excludeMinifiedNoSkip sources with very long lines when true. Keep the default false for reverse engineering because relevant code often exists only in compressed bundles.

Output Schema

NameRequiredDescription
okYesWhether the tool completed successfully.
dataNo
toolYesStable MCP tool name.
errorNo
summaryYesConcise human-readable outcome.
select_frameA

Lists or selects frames, including iframes, within the current page. Use it when the target element, page-defined global, script, or execution context may live in an iframe: first list frames, then pass frameIdx before click_element or evaluate_script. Omitting frameIdx lists 20 frames per page without changing context; passing frameIdx changes the shared frame target, with 0 restoring the main frame. It does not switch browser tabs or navigate—use select_page or navigate_page for those actions—and listPageIdx only paginates this listing.

NameRequiredDescriptionDefault
frameIdxNoFrame index from the latest frame listing. Pass it to target later frame-aware tools; 0 restores the main frame. Omit it to list frames without changing context, and re-list after navigation or frame attachment/detachment because indices can shift.
pageSizeNoMaximum frames to list per response. Defaults to 20.
listPageIdxNoZero-based pagination index for the frame listing only. This is not the frameIdx used to select a frame. Defaults to 0.

Output Schema

NameRequiredDescription
okYesWhether the tool completed successfully.
dataNo
toolYesStable MCP tool name.
errorNo
summaryYesConcise human-readable outcome.
select_pageA

Lists or selects open browser pages. Use it without pageIdx to identify the active page or choose the correct tab before inspecting network traffic, scripts, frames, or console output; pass pageIdx to make one listed page the shared target for later tools. It does not navigate or create pages: use navigate_page to change the selected page's URL and new_page when a separate tab is required. listPageIdx only paginates the page listing and never changes selection.

NameRequiredDescriptionDefault
pageIdxNoSnapshot index from the latest page listing. Pass it to make that page the target for later tools; omit it to list pages without changing selection. Re-list after pages open or close because indices can shift.
pageSizeNoMaximum pages to list per response. Defaults to 20.
listPageIdxNoZero-based pagination index for the page listing only. This is not the pageIdx used to select a browser page. Defaults to 0.

Output Schema

NameRequiredDescription
okYesWhether the tool completed successfully.
dataNo
toolYesStable MCP tool name.
errorNo
summaryYesConcise human-readable outcome.
set_breakpoint_on_textA

Sets a restorable URL-backed breakpoint when distinctive code text is known and its runtime values must be observed. Call it directly when the user already supplies precise text plus any URL/occurrence disambiguation; use search_in_sources/get_script_source first only when the location is unknown or ambiguous. For an API with no known code location, start with list_network_requests and get_request_initiator or use break_on_xhr. On a hit, call get_paused_info, optionally evaluate_script, then step or resume. Returns the current breakpointId for remove_breakpoint; list breakpoints again after a rebuilt debugger session, and note that unnamed inline/eval scripts cannot use this URL breakpoint.

NameRequiredDescriptionDefault
textYesExact case-sensitive source text used to locate the breakpoint, such as a distinctive function declaration, call, or statement. Prefer a snippet confirmed by search_in_sources and avoid common tokens.
conditionNoOptional simple synchronous expression evaluated in the future call frame; the breakpoint pauses only when it is true. Use it to reduce repeated hits after the location is precise, never for async work, complex discovery, or side effects.
urlFilterNoCase-insensitive URL substring that limits candidate scripts. Use the URL from search_in_sources/get_script_source to avoid the same text in unrelated bundles.
occurrenceNoOne-based occurrence among matching loaded-source results (default: 1). Use only after reviewing multiple search matches; urlFilter is usually the more stable disambiguator.

Output Schema

NameRequiredDescription
okYesWhether the tool completed successfully.
dataNoMachine-readable result payload.
toolYesStable MCP tool name.
errorNo
summaryYesConcise human-readable outcome.
stepA

Advances JavaScript execution by one debugger operation from an existing pause and returns the next stopped call frame with concise source context. Use after get_paused_info or evaluate_script when control flow still needs tracing; it cannot start from running execution. Each advance invalidates prior callFrameIds, so inspect the new pause again as needed, then use pause_or_resume(action="resume") to finish.

NameRequiredDescriptionDefault
directionYesChoose "over" for the next statement without entering calls, "into" to follow a call, or "out" to continue until the current function returns.

Output Schema

NameRequiredDescription
okYesWhether the tool completed successfully.
dataNoMachine-readable result payload.
toolYesStable MCP tool name.
errorNo
summaryYesConcise human-readable outcome.
take_screenshotA

Captures the visual state of the currently selected page. Use it to verify page layout, visible UI state, selector targets, in-page dialogs/modals, or the effect of a navigation/click; it is not a substitute for DOM values, network evidence, or script inspection. By default it returns the visible viewport, while fullPage=true captures the whole document; oversized captures may be saved as a temporary artifact instead of attached. Pass filePath for a reusable local artifact; existing files require confirmOverwrite=true and remain subject to --allowedRoots.

NameRequiredDescriptionDefault
formatNoImage format for the attachment or saved file. Defaults to png; use jpeg when smaller lossy output is preferred.png
qualityNoCompression quality for JPEG format (0-100). Higher values mean better quality but larger file sizes. Ignored for PNG format.
filePathNoOptional absolute or working-directory-relative path for a reusable screenshot artifact. Omit it to attach the image directly. Subject to --allowedRoots when configured.
fullPageNoCapture the entire scrollable document when true; leave false or omit it for the currently visible viewport.
confirmOverwriteNoMust be true when filePath already exists. New files do not require confirmation.

Output Schema

NameRequiredDescription
okYesWhether the tool completed successfully.
dataNoMachine-readable result payload.
toolYesStable MCP tool name.
errorNo
summaryYesConcise human-readable outcome.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 24 tool updatesv4.0.1
    • First observedbreak_on_xhr
    • First observedclear_network_requests
    • First observedclear_site_data
    • First observedclick_element
    • First observedevaluate_script
    • First observedget_paused_info
    • First observedget_request_initiator
    • First observedget_script_source
    • First observedget_websocket_messages
    • First observedlist_breakpoints
    • First observedlist_console_messages
    • First observedlist_network_requests
    • First observedlist_scripts
    • First observednavigate_page
    • First observednew_page
    • First observedpause_or_resume
    • First observedremove_breakpoint
    • First observedsave_script_source
    • First observedsearch_in_sources
    • First observedselect_frame
    • First observedselect_page
    • First observedset_breakpoint_on_text
    • First observedstep
    • First observedtake_screenshot

TDQS

A4.3/5.0

Scored across 24 tools

Disambiguation3/5

Tools are organized around specific debugging actions, but many overlap in purpose (e.g., multiple breakpoint and pause/resume tools, multiple request inspection tools). While descriptions are precise, an agent could easily confuse which tool to use for a given step, especially with 24 tools.

Naming Consistency4/5

Most tools follow a verb_noun pattern in snake_case (e.g., clear_network_requests, click_element). A few deviate slightly (e.g., 'break_on_xhr', 'get_paused_info'), but overall the naming is predictable and readable.

Tool Count3/5

24 tools is on the higher side for a focused reverse engineering server. The set is comprehensive but some tools could be merged (e.g., clear_network_requests and clear_site_data are distinct but very similar). Still, each tool has a clear role, so the count is borderline but acceptable.

Completeness4/5

The tool surface covers all major aspects of JavaScript reverse engineering: network interception, source inspection, breakpoint management, page control, and evaluation. Minor gaps exist (e.g., no direct DOM query tool), but the set is largely complete for its purpose.

Maintenance

ActivityStale
ResponsivenessMixed handling

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI assistants to debug frontend applications by providing direct access to browser DevTools, React state, DOM inspection, and runtime debugging capabilities. Bridges the gap between AI and complex web applications for autonomous debugging and issue resolution.
    1
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    Enables AI assistants to debug JavaScript and TypeScript applications by connecting to Chrome DevTools Protocol-compatible debuggers, allowing them to set breakpoints, step through code, inspect variables, and evaluate expressions with full source map support.
    18
    8 npm
    2
    Apache 2.0