Skip to main content
Glama
vynxc

Roku MCP

by vynxc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Roku MCP

No user-submitted related servers found.

    Related Servers

    • roku-mcp

      danecodes
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to inspect and control Roku devices—query UI elements, send remote input, launch channels, and run tests—using the Model Context Protocol or a CLI.
      14 npm
      4
      MIT

    • 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-dev-doc-mcp

      artemisaiev
      A
      license
      A
      quality
      C
      maintenance
      Provides local, offline searchable access to Roku and BrightScript development documentation via MCP tools and resources, including full-text search, sectioned reading of large docs, and background syncing from the upstream repo.
      4
      1
      -

    • brs-docs-mcp

      bblietz
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Roku BrightScript documentation and device control, enabling doc search, device introspection, keypress/keysequence input, app launch, and sideloading.
      -

    • roku-debug-mcp

      dominick253
      A
      license
      A
      quality
      C
      maintenance
      Provides AI agents with Roku BrightScript debugging tools, including log reading, scene graph inspection, breakpoint management, variable inspection, and execution control.
      21
      1
      Apache 2.0
    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 7 tools

    Disambiguation5/5

    Each tool maps to a distinct phase or resource: environment diagnostics, project create/inspect, static checks, build, tests, reference search, and simulator preview. The closest pair is check vs test, but their descriptions (diagnostics vs running BrightScript tests) clearly separate them.

    Naming Consistency4/5

    All tools share the roku_ prefix and lowercase snake_case, making the set predictable. Minor deviation: roku_project and roku_reference use nouns rather than the imperative verb style of check/build/test/preview, but this is easy to learn.

    Tool Count5/5

    Seven tools is well within the ideal range and each covers a necessary step in the Roku development workflow. The set is neither bloated nor too thin.

    Completeness4/5

    The tools cover the full local Roku project lifecycle: create/inspect, check, build, test, and preview, plus reference and capability reporting. There is no update/delete or device deployment tool, but those may be intentionally out of scope for a simulator-focused MCP.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources