A
licenseNot graded
qualityA
maintenanceMCP server for remote debugging of Apps in Toss mini-apps, providing CDP relay and test runner capabilities.
109 npm
BSD 3-Clause
tv-debug-mcp
by Ediand11
Related Servers
Alternatives to tv-debug-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for debugging Electron apps: discover, launch, and control apps via Chrome DevTools Protocol and Node inspector, enabling JavaScript evaluation, network/console monitoring, screenshots, profiling, and breakpoints.441MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that connects to your browser to capture screenshots, inspect console logs, network requests, and more via Chrome DevTools Protocol.4 npm2MIT
- FlicenseNot gradedqualityBmaintenanceModular testing and automation MCP servers for Android devices, desktop browsers, canvas games, and visual regression.-
- AlicenseNot gradedqualityBmaintenanceMCP server for safety-first automation and app QA, exposing deterministic tools to control graphical apps, browsers, terminals, Android devices, VMs, and SSH hosts.2 npmApache 2.0
- AlicenseAqualityDmaintenanceMCP server for controlling Chromium/Chrome via Chrome DevTools Protocol. Supports cross-platform automation, auto-launch, and automatic reconnection.251MIT
TDQS
A4.4/5.0
Scored across 15 tools
Disambiguation5/5
Each tool targets a clearly distinct aspect of the TV app debugging workflow: state inspection, waiting, input, navigation, video, profiling, heap, etc. There is no meaningful overlap; even similar tools like tv_state and tv_video_state differ in scope (whole app vs. media playback).
Naming Consistency5/5
All tools use the 'tv_' prefix and snake_case naming, with a consistent verb-oriented pattern for actions (install, launch, press, goto, evaluate) and noun-style for state/snapshots. The naming convention is uniform and predictable across the entire set.
Tool Count5/5
15 tools is at the upper edge of the 'well-scoped' range but every tool serves a distinct purpose for TV debugging, covering setup, interaction, verification, and performance analysis. None are redundant, and the count feels appropriate for the domain.
Completeness4/5
The surface covers the full workflow: discover devices, install, launch, interact, inspect state, capture screenshots/video, wait for conditions, run sequences, evaluate JS, and profile/heap. Minor gaps exist (e.g., no dedicated network traffic tool, no uninstall without reinstall), but agents can work around these with the provided tools.
Maintenance
ActivityActive
ResponsivenessNo issues