Smart TV MCP
Related Servers
Alternatives to Smart TV MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to operate an Android device through constrained ADB tools for device discovery, screenshots, UI inspection, taps, swipes, text entry, key presses, and app package control, without cloud APIs or a built-in language model.1MIT
- AlicenseAqualityBmaintenanceLets an MCP client control an NVIDIA Shield TV over the Android TV Remote protocol v2 by pressing remote keys, launching allow-listed apps, waking or sleeping the device, and reading its power state and foreground app.8MIT
- AlicenseNot gradedqualityBmaintenanceEnables controlling an Android device from an MCP client via ADB, including wireless debugging discovery, UI-tree inspection, and performing taps, swipes, typing, app actions, and shell commands without relying on screen coordinates.12 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables control of a paired Android TV or Google TV through a relay: list devices, send remote keys, launch apps and intents, resolve and play titles via streaming providers, and observe the screen.MIT
- AlicenseNot gradedqualityBmaintenanceEnables bounded, local-first Android device perception and interaction over ADB, including screenshots, UI hierarchy inspection, allowlisted key/app/URI actions, and guarded verified taps. It also exposes passive health, runtime status, capability, permission, and unified device-contract surfaces.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI assistants to see and control Android devices through ADB and a fast device-control protocol, including screenshots, touch input, typing, app management, UI inspection, file transfer, shell commands, and audio/video streaming.374 npmMIT
TDQS
Scored across 10 tools
Most tools have clearly distinct purposes: connection, status, package discovery, launching, navigation, text entry, logs, UI metadata, and playback control. There is some potential confusion among tv_status, tv_playback_status, and tv_playback, but the descriptions make their boundaries reasonably clear.
All tool names use a consistent tv_ prefix and snake_case, which makes them predictable. However, some names are action-oriented (tv_connect, tv_launch) while others are resource-oriented (tv_packages, tv_logs, tv_ui_metadata), so the verb_noun pattern is not fully uniform.
Ten tools is well-scoped for a Smart TV control server, covering connection, status, app discovery, launching, input, playback, logs, and UI inspection without obvious redundancy. Each tool appears to earn its place in the surface.
The core lifecycle for Smart TV interaction is covered: connect, inspect status, discover packages, launch apps, navigate, type text, send media keys, read logs, and inspect UI metadata. Minor gaps exist around explicit disconnect, power control, volume control, and app termination, but most workflows can likely be handled through the available navigation and media-key tools.