remote-control-tv
Related Servers
Alternatives to remote-control-tv
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceA MCP server that enables AI assistants to control Android devices via ADB, supporting device info, screen control, input simulation, app management, shell execution, file transfer, and UI parsing.20-
- AlicenseAqualityBmaintenanceMCP server for Android device control via ADB and scrcpy, enabling AI agents to see and interact with Android devices.46214MIT
- AlicenseAqualityAmaintenanceMCP server that gives AI agents full vision and control over Android devices via ADB and scrcpy. Supports screenshots, input, apps, UI automation, shell, files, and clipboard.3821493MIT
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that enables AI assistants to control Android TV devices, providing remote control functionality like navigation, playback control, app management, and device status monitoring.9MIT
- FlicenseNot gradedqualityDmaintenanceA powerful MCP server that provides comprehensive Android device automation capabilities through ADB, enabling AI agents to interact with Android devices for testing, automation, and device control tasks.1-
- AlicenseNot gradedqualityBmaintenanceA comprehensive MCP server for Android Debug Bridge, enabling AI agents to control Android devices through structured tools like launching apps, UI automation, file operations, and log capture.1MIT
TDQS
Scored across 6 tools
Most tools have clear boundaries: tv_play handles playback with deep linking, tv_search only returns results, tv_app launches apps without deep linking, and tv_key sends raw key presses. Some overlap exists between tv_volume and tv_key (both can send volume commands), and tv_play/tv_app can both launch content, but descriptions clarify when each should be used.
All tools follow a consistent tv_ prefix and snake_case convention, making the set predictable. The second part is mostly an action noun (power, volume, key, app) rather than a strict verb_noun pattern, but the naming remains coherent and easy to navigate.
Six tools is a well-scoped set for a TV remote control server. Each tool covers a distinct major function: playback, power, volume, key input, app launching, and search — no unnecessary bloat or redundant duplicates.
The core remote control lifecycle is well covered: power, volume, navigation, playback, app launch, and content discovery. Obvious gaps like input/source switching or querying current playback status are missing, but the tool surface is still sufficient for most common TV control workflows.