A
licenseB
qualityD
maintenanceElectron debugging MCP server for both renderer (via Chrome DevTools Protocol) and main process (via V8 Inspector Protocol), enabling automation, debugging, and network capture.
31
7 npm
MIT
debugtron-mcp
by xrntkk
Related Servers
Alternatives to debugtron-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for interacting with and debugging Electron apps, providing tools for window automation, IPC, logs, and main-process state via CDP and Node inspector.205 npmMIT
- AlicenseBqualityBmaintenanceA Model Context Protocol server that provides comprehensive Electron application automation, debugging, and observability capabilities through Chrome DevTools Protocol integration.4260 npm71MIT
- AlicenseNot gradedqualityCmaintenanceEmbedded MCP server for Electron apps that exposes BrowserWindow surfaces and lets MCP clients drive renderers through Chrome DevTools Protocol.2 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server that connects to your browser to capture screenshots, inspect console logs, network requests, and more via Chrome DevTools Protocol.4 npm2MIT
- AlicenseAqualityDmaintenanceMCP server for controlling Chromium/Chrome via Chrome DevTools Protocol. Supports cross-platform automation, auto-launch, and automatic reconnection.251MIT
TDQS
A3.8/5.0
Scored across 44 tools
Disambiguation5/5
Each tool targets a specific context or action (e.g., evaluate_in_main vs evaluate_in_renderer, monitor_events vs monitor_ipc), with clear boundaries between DOM, network, debugging, and profiling tools. No two tools overlap in purpose.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern using underscores, such as get_dom_snapshot, list_pages, set_breakpoint, and stop_cpu_profile. There are no deviations or mixed conventions.
Tool Count4/5
44 tools is high but justified by the broad scope of Electron debugging (main process, renderer, workers, profiling, IPC, network). The count is appropriate for a comprehensive debugger, though a few utilities might be consolidated.
Completeness5/5
The tool set covers the full lifecycle of debugging: launch, navigation, DOM inspection, network, console, process logs, breakpoints, stepping, profiling, heap snapshots, and IPC monitoring. There are no obvious gaps for the domain.
Maintenance
ActivitySlowing
ResponsivenessNo issues