Skip to main content
Glama
dominick253

roku-debug-mcp

by dominick253
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to roku-debug-mcp

No user-submitted related servers found.

    Related Servers

    • roku-dev-mcp

      voidxela
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to develop, deploy, navigate, inspect, and debug Roku BrightScript and SceneGraph applications with direct hardware control.
      -

    • Roku MCP Server

      maskelog
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to develop, test, and certify Roku applications by providing direct control over device functions like app deployment, remote input, and SceneGraph inspection. It supports automated workflows including real-time log collection, media monitoring, and certification verification.
      1
      -

    • MCP Debugger

      debugmcp
      A
      license
      C
      quality
      A
      maintenance
      Enables AI agents to perform step-through debugging of Python, JavaScript/Node.js, and Rust programs using the Debug Adapter Protocol, with support for breakpoints, variable inspection, and stack traces.
      21
      166
      MIT

    • mcp-debug-tools

      hwanyong
      A
      license
      Not graded
      quality
      C
      maintenance
      Bridges AI agents with VS Code's debugger, enabling breakpoint management, step execution, variable inspection, and stack tracing via CLI commands.
      24
      GPL 3.0
    • DebugMCP by microsoft

      DebugMCPofficial

      microsoft
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to debug code inside VS Code by setting breakpoints, stepping through execution, inspecting variables, and evaluating expressions across multiple languages.
      501
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools are clearly separated by domain (device control, debugging, breakpoints), but there are several debugger control tools (continue, step, stop) and multiple breakpoint tools that could be confused if descriptions were skimmed. The overlap is mild and the descriptions are specific enough to disambiguate in most cases.

    Naming Consistency4/5

    The tool names consistently use a 'roku_' prefix followed by a category and action (e.g., roku_debug_breakpoints_add, roku_debug_variables, roku_key). There are some minor inconsistencies like roku_sideload_and_connect versus the more structured debugger tools, and roku_postback is less descriptive, but the overall pattern is predictable.

    Tool Count4/5

    21 tools is on the high end but each tool serves a distinct purpose in the Roku debugging workflow. The count is justified given the breadth: device info, app control, screenshot, postback, and a full debugger suite. It feels slightly heavy but well-scoped for the domain.

    Completeness5/5

    The tool surface covers the full Roku development/debugging lifecycle: device discovery, app launching, remote control, scene graph inspection, breakpoint management, execution control, stack/variable inspection, and console output. There are no obvious missing operations for the stated debugging purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources