Skip to main content
Glama
paramount-engineering

Roku Dev Studio MCP Server

by paramount-engineering
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Sideload Channel Package

sideload
Destructive

Upload and install a Roku channel .zip package on a device, replacing the current sideloaded dev app. Accepts a local file path or base64-encoded zip content for remote execution.

Instructions

Upload and install a .zip channel package on the device. Destructive: replaces any currently sideloaded Dev App (readOnly false; not safe for autonomous use without user intent). Provide the zip via filePath — an absolute path to a .zip on the SAME machine that runs Roku Dev Studio. Do NOT use this when running in a remote agent sandbox (Claude.ai, ChatGPT web) where files only exist inside the agent's container — the path will not resolve on the user's machine. OR via contentBase64 + filename — the .zip bytes inline; this server writes them to a temp file on the user's machine, sideloads, and cleans up. Use this whenever the agent has file content but no shared filesystem with Roku Dev Studio. Password is optional when Dev Studio has remembered it for this device.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceNoTarget device — IP (e.g. "192.168.1.137") or serial (e.g. "X0004EX9Q7M"). Omit to use the focused device.
filePathNoAbsolute path to a .zip on the same machine that runs Roku Dev Studio. Mutually exclusive with `contentBase64`. Will fail with an actionable error if the path looks like an agent sandbox path (e.g. /mnt/user-data/...).
filenameNoSuggested filename for the temp file when using `contentBase64` (e.g. "my-app.zip"). Optional but recommended; if omitted, "agent-upload.zip" is used.
passwordNoDeveloper password. Omit if Roku Dev Studio has saved it for this device (Remember on the device tab).
contentBase64NoZip bytes encoded as base64. The server writes them to a temp file on the user's machine, sideloads, then deletes the temp file. Use this when running in a remote agent sandbox so file content travels through MCP rather than relying on a shared filesystem. Provide `filename` alongside.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • addedInput schema / oneOf
      Added value: +[
+  {
+    "required": [
+      "filePath"
+    ]
+  },
+  {
+    "required": [
+      "contentBase64"
+    ]
+  }
+]
    • changedInput schema / properties / device / description
      Previous value: -"Target device — IP (e.g. \"192.168.1.154\") or serial (e.g. \"X00046N6S6F\"). Omit to use the focused device."New value: +"Target device — IP (e.g. \"192.168.1.137\") or serial (e.g. \"X0004EX9Q7M\"). Omit to use the focused device."
  2. First observedv1.0.1

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already include destructiveHint: true and readOnlyHint: false, but the description adds specific behavioral detail: it replaces the currently sideloaded Dev App, writes base64 content to a temp file, sideloads, then cleans upaint. This meaningfully exceeds the structured annotation hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is longer than average, but its length is justified by two mutually exclusive input modes and a meaningful destructive warning. The flow is logical: core purpose, destructive warning, filePath pathway, contentBase64 pathway, then password nuance. Every sentence earns its place, though it could be trimmed slightly without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no output schema)Skip, but the description covers prerequisites, both input modes, cleanup behavior, destructive effects, and edge-case path failures. It omits what the success response looks like, which an agent might want, but the invocation guidance is thorough enough that this is a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds beyond the schema by explaining the real-world constraint that filePath only works on the same machine as Roku Dev Studio)Skip, and by giving a decision rule for choosing contentBase64 over filePath. This adds semantic value, but some sentences mostly restate the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Upload and install a .zip channel package on the device.' It further distinguishes the operation by noting it replaces the currently sideloaded Dev App, which separates it from sibling tools like delete_sideload or launch_app.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says when not to use this tool ('Do NOT use this when running in a remote agent sandbox') and when to use it ('Use this whenever the agent has file content but no shared filesystem'). It also warns that the operation is destructive and not safe for autonomous use without user intent, giving clear usage boundaries.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools