Log inSubmit server
RokuMCP logo

RokuMCP

Automates Roku devices through MCP with remote control, app deployment, UI inspection, screenshots, and debugging tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install RokuMCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "rokumcp": {
      "command": "npx",
      "args": [
        "-y",
        "roku-mcp"
      ],
      "env": {
        "ROKU_DEVICE_HOST": "YOUR_VALUE_HERE",
        "ROKU_DEVICE_PASSWORD": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 42 tools correctly (1d ago).

Overview

RokuMCP MCP server connects AI agents to Roku devices through the standard MCP stdio transport. It supports SSDP discovery, ECP remote control, app sideloading, screenshots, SceneGraph inspection and editing, media state queries, and BrightScript console access. The server runs with npx and can use a configured device host or discover Roku devices on the local network. Reach for it when you need an agent to test, inspect, operate, or debug a Roku app.

Use cases

  • Deploy and test a sideloaded Roku channel
  • Navigate Roku apps and verify screens with screenshots
  • Inspect and edit running SceneGraph nodes
  • Analyze BrightScript profiles for performance regressions

Key features

  • SSDP Roku device discovery
  • ECP remote control and text entry
  • Channel deployment and launch
  • UI tree and SceneGraph inspection
  • BrightScript debug console access
  • BrightScript profile analysis and comparison

Tools42

What RokuMCP lets your agent do. Expand a tool for its parameters.

Verified live~6.3k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

5/5 checks healthy over the last 42d

What it can do

From the 42 tools this server returned when we ran it.

Can delete or modify data · 2Handles credentials · 2Makes network requests · 1Read-only tools · 40
Network at startup3 connections
Files written at startupNone
Install scriptsprepare
npm provenanceNot published
Package age211 days
Maintainers1

Observed 2026-10-23 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · roku-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars4Stargazers on the source repository.
npm downloads715Package downloads in the last 30 days.
Last commit9d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed42Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How RokuMCP works

What RokuMCP MCP server does

RokuMCP MCP server exposes Roku device operations as MCP tools for an AI client. It can discover devices on the local network, retrieve device and application state, control navigation, launch channels, enter text, and capture screenshots. The tool set also covers developer workflows: deploying or removing a sideloaded channel, reading the running UI as XML, inspecting SceneGraph nodes, and interacting with the BrightScript debug console.

Runtime UI editing tools can change node fields, visibility, position, focus, and hierarchy while a channel is running. Agents can read values, wait for field changes, and use node searches to build an observe, act, wait, and verify workflow. Separate profiling tools analyze .bsprof files for memory and CPU findings or compare two profiles for regressions and improvements.

How it works

The server communicates with MCP clients over stdio. A client launches it with npx -y roku-mcp, after which the available roku_* and profiling tools can be called. Device operations use a Roku host and, where required, the developer password. Host and password values may be supplied through the process environment or passed on individual tool calls; call-level values override the environment configuration.

If no host is supplied, the server uses SSDP to find Roku devices on the local network and selects the first result. The roku_discover tool can list devices explicitly. Passwords are not discovered automatically. Console operations connect to the Roku BrightScript debug console on TCP port 8085, while app and remote-control operations use the Roku device interfaces supported by the tool.

Setup and configuration

Install the package globally with npm or let the MCP client fetch it on demand:

Terminal
npm install -g roku-mcp

A client configuration needs the npx command and -y roku-mcp arguments. ROKU_DEVICE_HOST can contain a Roku IP address or hostname, and ROKU_DEVICE_PASSWORD contains the device developer password. Both variables are optional at process startup if equivalent values are provided on tool calls; omitting the host enables SSDP discovery. The server also loads these variables from a .env file in the current working directory.

The documented client configurations cover Cursor, VS Code with GitHub Copilot Agent mode, Claude Desktop, Windsurf, and other MCP-compatible clients. Node.js 18+ and an available npx command are required by the documented launch setup. After changing configuration, reload or restart the client as appropriate and verify that the Roku tools are listed.

Tools and capabilities

  • Discover Roku devices and query model, firmware, serial, and network information.
  • Send individual or sequenced remote-control keys, type text, launch channels, and wait between actions.
  • Read the active app, media-player state, app UI XML, focused node, and SceneGraph nodes.
  • Capture screenshots and search nodes by ID or attributes such as subtype or text.
  • Deploy or delete a developer channel and connect to, read from, send commands to, or disconnect from the BrightScript console.
  • Edit runtime node fields, visibility, position, focus, parentage, and creation; read values and observe field changes.
  • Analyze or compare BrightScript profiler files for leaks, hot paths, and performance changes.

Limitations and notes

RokuMCP MCP server is intended for Roku devices reachable from the machine running the MCP client. Automatic discovery depends on local-network SSDP visibility, and the developer password still must be supplied separately. Runtime node editing depends on the relevant Roku runtime tooling and requires the running channel to expose the nodes being targeted.

The README recommends following an observe-before-action workflow for UI automation and notes that runtime editing may require the node's uiElementId. Console access uses port 8085, so network access and device-side debugging availability affect those tools. The server is documented as a stdio service rather than a hosted HTTP endpoint.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about RokuMCP

RokuMCP is an MCP server that connects AI clients to Roku devices for automation and development. Its main tools discover devices, send remote-control keys, launch channels, type text, capture screenshots, inspect and edit SceneGraph UI nodes, deploy developer channels, and access the BrightScript debug console.

Install it with npm or launch it on demand using npx. Use `npm install -g roku-mcp` for a global installation, or configure your MCP client to run `npx -y roku-mcp` with Node.js 18+ available on PATH.

Yes, RokuMCP works with Cursor 0.45 or newer in Agent mode. Add an MCP entry that runs `npx -y roku-mcp`, optionally set the Roku host and developer password, then reload the window and confirm the server in Cursor's MCP settings.

RokuMCP uses the configured `ROKU_DEVICE_HOST` or a host supplied to a tool call when available. If no host is provided, it uses SSDP on the local network, and `roku_discover` can list the Roku devices it finds.

Yes, RokuMCP can edit fields, visibility, position, focus, and hierarchy on runtime SceneGraph nodes. Use UI inspection and node-search tools to identify a target, then use the runtime editing tools and value queries to verify the change.

Related MCP servers

All in Home Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewRokuMCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/rokumcp?style=directory)](https://allmcps.com/mcp/rokumcp)
HTML Embed
<a href="https://allmcps.com/mcp/rokumcp"><img src="https://allmcps.com/api/badge/rokumcp?style=directory" alt="RokuMCP on AllMCPs" /></a>