Roku MCP Server
Related Servers
Alternatives to Roku MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables AI assistants to control Roku TVs on the local network via natural language commands.6-
- FlicenseAqualityDmaintenanceAn MCP server that enables AI assistants to control TVs on a local network through natural language commands. It currently supports Roku devices, allowing users to launch apps, manage playback, and navigate menus.51-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to inspect and control Roku devices—query UI elements, send remote input, launch channels, and run tests—using the Model Context Protocol or a CLI.18 npm6MIT
- FlicenseBqualityCmaintenanceEnables discovery and control of smart appliances (TVs, media devices) on the local network through natural language, supporting providers like Roku, Google TV, and Home Assistant.18-
- AlicenseNot gradedqualityCmaintenanceGives AI coding agents eyes and hands on a TV: capture the screen as an image, press remote keys, type text, read console logs and JS errors, deploy projects, launch apps, and apply or revert system tweaks across Android TV, Google TV, Fire TV, Roku and LG webOS. This lets an agent design, live-check and iterate on a custom ad-free home screen directly on the big screen.MIT
- AlicenseAqualityCmaintenanceMCP server for controlling Google TV devices via natural language. Enables key presses, text input, and app launching on paired devices.51MIT
TDQS
Scored across 8 tools
Most tools are clearly distinct by action and purpose: status, power, app launch, remote key, volume, text input, search, and app listing. There is minor overlap because roku_remote_key can send volume keys while roku_adjust_volume also handles volume/mute, but the descriptions make the intended use reasonably clear.
All tools use the same snake_case style and roku_ prefix, which is readable. However, the verb_noun convention is inconsistent: some tools use verbs (roku_get_status, roku_launch_app), while others use noun-like or ambiguous names (roku_power, roku_remote_key, roku_search).
Eight tools is well-scoped for a Roku TV control server. Each tool covers a distinct control area and there is no excessive tool sprawl.
The surface covers the core Roku control lifecycle: checking status, powering on/off, launching apps, sending remote keys, adjusting volume, typing text, searching, and listing apps. Minor gaps exist around explicit input/source selection and device discovery, but these are largely workable through remote keys and status.