Skip to main content
Glama
AaronGoldsmith

MCP Remote Control

by AaronGoldsmith
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MCP Remote Control

No user-submitted related servers found.

    Related Servers

    • remote-control-tv

      Hustawek
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that lets AI agents control Android TVs via ADB, including searching and playing content across streaming services, managing power and volume, and sending remote control commands.
      6
      11 npm
      3
      MIT

    • mcp-gtv

      kud
      A
      license
      A
      quality
      D
      maintenance
      MCP server for controlling Google TV devices via natural language. Enables key presses, text input, and app launching on paired devices.
      5
      MIT

    • ha-mcp

      osrd-gh
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI assistants to control Home Assistant via natural language, including device control, automation management, and system configuration.
      MIT

    • tuya-infrared-mcp

      1124823599331l-boop
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI assistants to control devices via Tuya infrared remote control, supporting actions like toggling power and setting modes through natural language.
      6
      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

    A4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: get_device_info retrieves device metadata, list_apps enumerates available applications, launch_app starts a specific app, power_on turns on the TV, and press_key simulates remote button presses. The descriptions explicitly differentiate their functions, eliminating any ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case: get_device_info, list_apps, launch_app, power_on, and press_key. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming conventions.

    Tool Count5/5

    With 5 tools, this server is well-scoped for remote control functionality. Each tool serves a specific, essential purpose (device info, app management, power control, and key simulation), and none feel redundant or missing for basic TV operations. The count is appropriate for the domain.

    Completeness4/5

    The tool set covers core remote control operations effectively, including power management, app launching, and key presses. However, minor gaps exist, such as the lack of a power_off tool (though press_key can simulate PowerOff) and no explicit volume control beyond key presses, which agents can work around but might slightly hinder seamless automation.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources