Roku MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROKU_WORKSPACE | No | The absolute path to the workspace directory where Roku projects are stored. The directory must already exist. Can also be provided via the --workspace CLI argument. If not set, the server uses its working directory. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| roku_doctorB | Report installed Roku development capabilities and limitations. |
| roku_projectC | Create a NEW Roku project or inspect an existing project; never overwrite an existing project. |
| roku_checkB | Check a Roku project; diagnostics and nonzero exit codes indicate failures. |
| roku_buildA | Build a Roku project into a NEW ZIP; existing output must not be overwritten. |
| roku_testC | Run BrightScript test files in the headless simulator, not on a physical Roku device. |
| roku_previewA | Preview a project directory, ZIP, or BRS file in the simulator with bounded remote-key steps; output must be a NEW directory. |
| roku_referenceB | Search bundled Roku/BrightScript reference material. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool maps to a distinct phase or resource: environment diagnostics, project create/inspect, static checks, build, tests, reference search, and simulator preview. The closest pair is check vs test, but their descriptions (diagnostics vs running BrightScript tests) clearly separate them.
All tools share the roku_ prefix and lowercase snake_case, making the set predictable. Minor deviation: roku_project and roku_reference use nouns rather than the imperative verb style of check/build/test/preview, but this is easy to learn.
Seven tools is well within the ideal range and each covers a necessary step in the Roku development workflow. The set is neither bloated nor too thin.
The tools cover the full local Roku project lifecycle: create/inspect, check, build, test, and preview, plus reference and capability reporting. There is no update/delete or device deployment tool, but those may be intentionally out of scope for a simulator-focused MCP.