Smart Appliance MCP
Related Servers
Alternatives to Smart Appliance MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to discover and control smart TVs on the local network, including power, volume, navigation, and app launching across multiple brands.MIT
- FlicenseAqualityDmaintenanceEnables AI assistants to control Roku TVs on the local network via natural language commands.6-
- AlicenseBqualityAmaintenanceControl any smart TV with natural language — play Netflix/YouTube/Spotify by name, cast URLs, scene presets, multi-room audio, and multi-TV sync. Supports LG, Samsung, Android TV, Roku.2373 PyPI58MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to discover and control IoT devices on local networks and via Bluetooth LE.71MIT
- AlicenseBqualityBmaintenanceEnables an AI assistant to control and diagnose TVs, including Miracast, Samsung Tizen, and Android TV over ADB, with remote keys, app launching, wake-on-LAN, and scrcpy mirroring.18MIT
- 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.63 npmMIT
TDQS
Scored across 18 tools
Most tools target a distinct action/resource (discovery, pairing, device control, media recommendations). Minor overlap exists between suggest_content and recommend_content, and between search_content and search_apps, but descriptions clarify different inputs and purposes.
All tools use a consistent snake_case verb-first naming convention (list_, discover_, get_, control_, pair_, search_, suggest_, etc.). No mixed styles or arbitrary names; resource nouns follow verbs predictably.
At 18 tools the surface is on the heavy side for a single server, covering several subdomains (discovery, pairing, media, device control). The tools are not redundant enough to cut, but the count is above the ideal 3-15 range.
The server covers the full pairing lifecycle and core discovery/control/media workflow with no dead ends. Minor gaps like explicit device forgetting or media playback commands are absent, but adapters likely make those device-specific.