RokuHarness MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| create_webdriver_sessionA | Create a new Roku WebDriver session. This must be called before any other commands. Requires the Roku WebDriver server to be running. |
| end_webdriver_sessionA | End the current Roku WebDriver session and clean up resources. |
| get_ui_sourceA | Get the current UI hierarchy as SceneGraph XML. Essential for understanding what elements are on screen and writing element queries. |
| find_elementB | Find a UI element on screen using text, tag, and/or attributes. Returns element details if found. |
| verify_element_presentB | Verify that a specific element is present on screen. Returns true/false. Critical for acceptance criteria validation. |
| verify_screen_loadedA | Wait for a specific screen to load by checking for a marker element. Returns true when screen loads or false on timeout. |
| press_keyA | Press a remote control button. Common keys: Home, Back, Up, Down, Left, Right, Select, Play, Pause. |
| navigateB | Execute a sequence of key presses for navigation flows. |
| send_textA | Send text input (for search fields, forms, etc.). |
| take_screenshotB | Capture a screenshot of the current screen state. Returns base64-encoded PNG. |
| launch_appC | Launch a specific app with optional deep linking parameters. |
| get_player_stateA | Get current media player state (position, duration, state, buffering info). |
| get_installed_appsA | Get list of all installed apps on the device. |
| run_acceptance_testA | Run a complete acceptance test with multiple verification steps. Returns detailed pass/fail results. |
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 14 tools
Most tools have clearly distinct purposes, but there is some overlap among find_element, verify_element_present, and verify_screen_loaded since they all deal with UI state. Descriptions clarify their different return types and use cases.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_webdriver_session, press_key, verify_element_present). No mixing of conventions.
14 tools is well-scoped for a device automation server, covering session lifecycle, UI interaction, verification, and media state without being excessive.
The tool set covers the full lifecycle of device testing: session management, app control, UI inspection and interaction, verification, screenshots, and media state. No critical gaps for the stated purpose.