roku-debug-mcp
Provides tools for debugging Roku devices, including reading device info, inspecting scene graphs, reading console logs, managing breakpoints, stepping through BrightScript code, and executing code in stopped frames.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@roku-debug-mcpread the current console logs"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
roku-debug-mcp
MCP server giving AI agents the full VS Code Roku debug experience.
Exposes Roku's BrightScript debugging capabilities as MCP tools so AI agents can read logs, inspect the scene graph, step through code, read variables, and set breakpoints — the same info a developer sees in the VS Code Roku extension.
Architecture
graph TB
subgraph "AI Agent (Hermes, VS Code, etc.)"
MCP[<b>MCP Client</b><br/>stdio JSON-RPC]
end
subgraph "roku-debug-mcp (MCP Server)"
Server[<b>MCP Server</b><br/>21 tools]
Config[<b>Config</b><br/>ROKU_* env vars]
Server --> Config
end
subgraph "Roku Device"
direction LR
subgraph "Port 80 — HTTP"
Installer[<b>Sideloader</b><br/>Digest auth<br/>Expect: 100-continue]
end
subgraph "Port 8060 — ECP"
ECP[<b>ECP Client</b><br/>Device info<br/>Scene graph<br/>Postback/keys]
end
subgraph "Port 8081 — Binary Debug"
Debug[<b>Debug Client</b><br/>Binary protocol<br/>BSDBG magic]
end
subgraph "Port 8085 — Telnet"
Console[<b>Text Console</b><br/>Fallback logs]
end
end
MCP --> Server
Server --> Installer
Server --> ECP
Server --> Debug
Server --> ConsoleProtocol Layers
Port | Protocol | Auth | Purpose |
80 | HTTP | Digest + Expect: 100-continue | Channel sideloading |
8060 | ECP HTTP | None | Device info, scene graph, screenshots |
8081 | Binary | None | Primary debug protocol (VS Code uses this) |
8085 | Telnet | None | Text console (fallback) |
Binary Debug Protocol (Port 8081)
sequenceDiagram
participant C as Client (roku-debug-mcp)
participant R as Roku Device (port 8081)
C->>R: Handshake<br/>[magic(8)][protocol_version(4)]
R-->>C: [magic(8)][protocol_version(4)][packet_len(4)][revision]
Note over C,R: Request/Response Format:<br/>[packet_length(4)][request_id(4)][cmd_code(4)][payload]
C->>R: GET_THREADS (cmd=3)
R-->>C: THREADS response
C->>R: STACKTRACE (cmd=4, thread_index)
R-->>C: Stack frames
C->>R: ADD_BREAKPOINTS (cmd=7)
R-->>C: Confirmation
Note over C,R: Update notifications (request_id=0):<br/>CONNECT_IO_PORT, ALL_THREADS_STOPPED, etc.Handshake Magic: 0x0067756265647362 (b"bsdebug\0" little-endian)
Sideloading Flow (Port 80)
sequenceDiagram
participant C as Client
participant R as Roku (port 80)
C->>R: POST /plugin_package (Expect: 100-continue)
R-->>C: 401 Unauthorized (WWW-Authenticate: Digest)
C->>C: Compute digest hash
C->>R: POST /plugin_package (Authorization: Digest)
R-->>C: 100 Continue
C->>R: [ZIP payload]
R-->>C: 200 OK [chunked response with Dev Kit HTML]Related MCP server: Node.js Debugger MCP
What AI Can Do With This
Read device info — model, version, app currently running
Inspect scene graph — the full node hierarchy of the running app
Read console logs — stdout from the running BrightScript channel
List threads — see all execution threads and their stop states
Read stack traces — frame-by-frame call stack for any stopped thread
Inspect variables — locals, globals, and scene graph component state
Execute code — run arbitrary BrightScript in a stopped frame
Manage breakpoints — add, list, remove breakpoints by file/line
Step execution — step over, step into, step out, or continue
Sideload channels — upload and install test channels with remote debug
Quick Start
1. Install
cd /home/dom/src/roku-debug-mcp
pip install -e .2. Configure Environment
export ROKU_DEVICE_IP=192.168.1.10 # Roku device IP
export ROKU_DEV_USER=rokudev # Dev channel username
export ROKU_DEV_PASSWORD=your-password # Dev channel password3. Register in Hermes
Add to ~/.hermes/mcp-servers.json:
{
"roku-debug-mcp": {
"command": "roku-debug-mcp",
"args": []
}
}4. Use in a Hermes Session
The AI agent will now have access to 21 new tools:
roku_device_info()
roku_scene_graph()
roku_debug_threads()
roku_debug_stacktrace(thread_index=0)
roku_debug_variables(thread_index=0, frame_index=0)
roku_debug_execute(thread_index=0, frame_index=0, code="x = 42")
roku_debug_breakpoints_add(breakpoints=[{...}])
roku_debug_console_output()Available Tools
Device / UI Tools (ECP — port 8060)
Tool | Description |
| Device model, version, etc. |
| Currently running app |
| Full scene graph node hierarchy |
| Send postback to channel |
| Launch a URI |
| Send remote control key |
| Capture screen image |
Debug Tools (Binary Protocol — port 8081)
Tool | Description |
| List all threads |
| Get stack frames |
| Read variables in a frame |
| Run BrightScript code |
| Add breakpoints |
| List active breakpoints |
| Remove specific breakpoints |
| Clear all breakpoints |
| Resume execution |
| Step execution |
| Pause execution |
| Get stdout lines |
| Debug protocol version |
Installer Tools (HTTP — port 80)
Tool | Description |
| Sideload a channel ZIP |
| Launch with remote debugging enabled |
Testing
Unit Tests (Mock Roku Server)
# Run all tests (uses mock server on ephemeral ports)
pytest tests/ -v
# Mock server runs automatically via conftest fixtures
# No manual setup requiredIntegration Tests (Real Roku Device)
# Requires env vars set
ROKU_DEV_IP=10.71.71.151 \
ROKU_DEV_PASSWORD=your-password \
pytest tests/test_integration_real_device.py -vCI/CD
Unit tests run on GitHub Actions Ubuntu runners
Integration tests run on self-hosted runner (10.71.71.90) with LAN access to real Roku
Project Structure
src/rokumcp/
config.py # Environment-based configuration
protocol.py # Binary protocol constants and Stream I/O
debug_client.py # Synchronous binary debug client (port 8081)
text_console.py # Telnet text console client (port 8085)
ecp.py # ECP HTTP client (port 8060)
installer.py # HTTP Digest-auth sideloader (port 80)
server.py # MCP server entrypoint — 21 tools
tests/
conftest.py # Pytest fixtures (mock server setup)
mock_roku_server.py # Mock Roku device simulator
test_protocol.py # Stream round-trips, ProtocolVersion
test_config.py # Config defaults, from_env
test_ecp.py # ECP HTTP client
test_text_console.py # Telnet console client
test_installer.py # Digest auth + multipart
test_debug_client.py # Full E2E vs mock binary server
test_integration_real_device.py # Real device (gated on env vars)
fixtures/ # Test channel ZIP fixturesProtocol Reference
Implementation derived from Roku's official reference:
See AGENTS.md for the full protocol specification and wire formats.
Development
Debugging the Protocol
# Run mock server manually
python tests/mock_roku_server.py
# Test specific protocol interaction
ROKU_DEVICE_IP=127.0.0.1 ROKU_DEBUG_PORT=8081 python -m rokumcp.serverBuilding
pip install -e .
roku-debug-mcp # runs MCP server over stdioLicense
Apache-2.0
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseBqualityDmaintenanceProvides Node.js debugging capabilities with process management for AI agents, allowing them to start/stop Node.js processes, set breakpoints, step through code, and evaluate expressions.816MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to debug Node.js applications using Chrome DevTools Protocol. Provides comprehensive debugging capabilities including breakpoints, stepping, variable inspection, expression evaluation, and console monitoring.180348MIT
- AlicenseCqualityAmaintenanceEnables AI agents to perform step-through debugging of Python, JavaScript/Node.js, and Rust programs using the Debug Adapter Protocol, with support for breakpoints, variable inspection, and stack traces.21159MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to develop, test, and certify Roku applications by providing direct control over device functions like app deployment, remote input, and SceneGraph inspection. It supports automated workflows including real-time log collection, media monitoring, and certification verification.1
Related MCP Connectors
Live browser debugging for AI assistants — DOM, console, network via MCP.
Agent Replay Debugger MCP — record every agent step + deterministic replay. Step-debugger for
Shared debugging memory for AI coding agents
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/dominick253/roku-debug-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server