Roku Dev StudioBLOCK
Cross-platform Electron desktop studio for Roku developers: remote control, device queries, sideload, telnet console, RALE/App Connector, BrightScript Fiddle, JSON Action Scripts, an `rds` CLI, an MCP server for AI agents, and an internet relay.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Roku Dev Studio
[](https://glama.ai/mcp/servers/paramount-engineering/roku-dev-studio)
Roku Developer Tools for macOS, Windows, and Linux — Remote Control, App Side-loading, ECP automation, RALE / App Connector, Network Inspector, Action Scripts, MCP server for AI agents (Cursor, Claude, VS Code), and a rds CLI. Supports both local network and internet-bridged devices.
A comprehensive cross-platform desktop application for controlling and developing on Roku devices over your local network or via remote server using the External Control Protocol (ECP).
Why Roku Dev Studio? (vs. official Roku tools)
Roku development is normally split across a pile of separate, single-purpose official tools — the Roku Remote Tool, the browser-based sideload installer, raw telnet, RALE, sca-cmd — that don't talk to each other. Roku Dev Studio doesn't replace Roku's own protocols (ECP, RALE, telnet, sca-cmd) — it wraps all of them in one GUI, one CLI (rds), and one MCP server:
38193bed2431OBSERVED · 2026-10-09Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add roku-dev-studio-remote-server --env RDS_RELAY_TOKEN=${RDS_RELAY_TOKEN} --env ROKU_DEV_PASSWORD=${ROKU_DEV_PASSWORD} -- npx -y [email protected]{
"mcpServers": {
"roku-dev-studio-remote-server": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"RDS_RELAY_TOKEN": "${RDS_RELAY_TOKEN}",
"ROKU_DEV_PASSWORD": "${ROKU_DEV_PASSWORD}"
}
}
}
}Exposed tools (11)
10 read · 1 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
YourFunctionName | read | Description of what it does |
action | read | What the agent should do on the device, in one sentence (e.g. |
action-script-contract | read | Canonical shape for validate_script / send_script_to_builder inputs (root, appFunction params, wait / if conditions). |
authoring-rules | read | Constraints the agent must obey when generating Action Scripts (version, password handling, wait vs delay, ...). |
capability-bundle | read | Every static catalog the agent needs in one JSON: actions, presets, vocabularies, RALE built-ins, authoring rules, op directory, and the agent contract. |
device | read | Optional target device (IP or serial). Omit to use the focused Dev Studio tab. |
goal | read | What the Action Script should accomplish on the device (one or two sentences). Use this prompt only when the task needs ordering, conditions, polling waits, variables, or Builder review. |
quick-start | write | One-page primer: bridge probe, capability loading, device selection, and the validate → send workflow. Read first. |
roku-action-script-quickstart | read | Primes the agent to author an Action Script for multi-step / conditional / saved-or-reviewed flows (bridge probe → capability load → validate → send to Builder). For single actions, prefer |
roku-debug-device | read | Primes the agent to inspect a Roku using read-only tools (probe_bridge → list_devices → get_selected_device → ecp_query / rale_get_node_by_id). |
roku-one-shot-action | read | Primes the agent to perform a single deterministic action (keypress, launch, ecp_query/post, rale_command, screenshot, ...) via a direct op — **not** by authoring an Action Script. |
Trust audit
BLOCKgrade F · trust 55/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | WARN |
| L1 | Static analysis of the code | WARN |
| L2 | Instruction surface (what it tells the agent) | FAIL |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (11 observation(s))
- Network
- declared (20 observation(s))
- Shell
- declared (5 observation(s))
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (25)
<li data-i18n="modals.devMode.step6">Your Roku will restart with Developer Mode enabled</li>
<p data-i18n-html="modals.helpModal.deviceDiscoveryScanHtml">Click <strong>Scan</strong> to automatically discover Roku devices on your network. Devices with Developer Mode enabled will show a green "
<p data-i18n="modals.helpModal.devAppIntro">For Developer Mode enabled devices:</p>
<p data-i18n="modals.helpModal.consoleNote">Requires Developer Mode enabled. Only one telnet connection can be active at a time per device.</p>
<p data-i18n-html="modals.helpModal.sideloadRelayFooterHtml">Requires the targeted devices to have Developer Mode enabled. See <strong>Remote Locations</strong> above for targeting devices at another
icon.icns
this.broadcast('[beacon.signal] |AppCompileComplete --- Sideload Relay dev channel ready');this.broadcast('[beacon.report] |AppExitComplete --- Sideload Relay session ended');const LAUNCH_COMPLETE_RE = /\[beacon\.signal\]\s*\|AppLaunchChainComplete|\[scrpt\.ctx\.run\.enter\]/i;
of static cards. A brand-new finding/crash/beacon card also slides+fades in on top of the flash;
.telnet-an-beacon-avg { flex: 0 0 auto; margin-left: auto; font-size: 12px; font-variant-numeric: tabular-nums; color: var(--text-secondary); font-family: var(--font-mono, ui-monospace, monospace); }win.loadURL('http://127.0.0.1:5173/').catch((err: unknown) => {'[Roku Dev Studio] Vite dev server not reachable at http://127.0.0.1:5173/. Run `npm run dev:solid` in apps/roku-dev-studio (or `npm run start:solid` from repo root).',
origin === 'http://127.0.0.1' ||
origin.startsWith('http://127.0.0.1:'){ id: 'loc-1', name: 'QA Lab', serverUrl: 'http://10.0.0.5:4951', host: '10.0.0.5', port: 4951 }, // relay: no accountappTileTitle: (name: string, id: string): string => `${name}\nID: ${id}\nНатисніть, щоб запустити`,`CONNECT ${host}${port} (HTTPS — зашифровано)\n\nЗахоплення через точку доступу бачить лише рукостискання TLS (SNI + IP), а не тіла JSON.\n\nУвімкніть MITM у Налаштуваннях і спрямуйте канал через Roku`Видалити плагін «${appId}»?\n\nЦе видалить програму з цього пристрою та з усіх пристроїв, прив’язаних до того самого облікового запису Roku.`,return createHash('md5').update(value).digest('hex');return createHash('md5').update(value).digest('hex');.createHash('sha1')import { IPC } from '../../shared/ipc/channels';import { S } from '../../shared/strings/index';import { IPC } from '../../shared/ipc/channels';Gates applied: instruction_override, no_behavioural_pass.
38193bed2431full audit observations/trust-audit/mcp-server/paramount-engineering__roku-dev-studio.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-09 | 38193bed2431 | BLOCK | F | 55 | first audit |
Questions
What is the Roku Dev Studio MCP server?
Cross-platform Electron desktop studio for Roku developers: remote control, device queries, sideload, telnet console, RALE/App Connector, BrightScript Fiddle, JSON Action Scripts, an `rds` CLI, an MCP server for AI agents, and an internet relay.
What tools does Roku Dev Studio expose?
11 in total: 10 read-only, 1 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Roku Dev Studio safe to connect to an agent?
No — not without reading the findings first. The audit graded it F (55/100) and found 5 critical or high issues in the source. Each one is listed on this page with the file and line it is on.
What credentials does Roku Dev Studio need?
It reads RDS_RELAY_TOKEN and ROKU_DEV_PASSWORD from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How current is this page?
The grade is for one exact copy of the source (38193bed2431), read on 2026-10-09. The repository is watched and re-audited when it changes.