Skip to main content
Glama
skdonthi

tv-mcp

by skdonthi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to tv-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
      -

    • browser-testbench

      llakie
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to remotely control, debug, and automate real browsers, iOS simulators, and Android emulators, including navigation, element inspection, interaction, screenshots, and mobile gestures.
      1,223 npm
      MIT

    • adb-tv-mcp

      mosesmrima
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to control Android TV/Android devices through ADB, including screen capture, remote control, app management, and more.
      24
      8 npm
      MIT

    • lg-tv-mcp

      OmerLapidot
      A
      license
      Not graded
      quality
      B
      maintenance
      Turns AI assistants like Claude and ChatGPT into a remote control for LG webOS smart TVs, enabling power control, volume, app launching, input switching, and more, all locally without cloud APIs.
      1
      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

    B3.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: discover devices, connect to a device, and access documentation. There is no overlap or ambiguity between these three tools.

    Naming Consistency3/5

    list_devices and connect_device follow a verb_noun pattern, but docs breaks the pattern by using a noun alone without a verb prefix like get_docs or list_topics.

    Tool Count2/5

    With only 3 tools and all descriptions mentioning that connecting 'unlocks app lifecycle tools', the server appears to gate functionality behind an initial connection step rather than exposing it directly. The set feels thin for a TV control server that presumably supports app lifecycle, pairing, and packaging operations that are only referenced in the docs tool.

    Completeness1/5

    The tool surface only covers discovery, connection, and documentation. Descriptions reference 'app lifecycle tools', 'pairing', 'dev mode', and 'packaging' as capabilities, but no tools exist to actually perform these operations—only docs describing them. This is a severely incomplete surface for the implied domain.

    Maintenance

    ActivitySlowing
    ResponsivenessResponsive

    Resources