mcp-server-shieldtv
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHIELDTV_HOST | No | The Shield's IP address or hostname. Overrides the value from config.json. When the host is set in more than one place, the most specific wins: `pair --host`, then `SHIELDTV_HOST`, then `config.json`. | |
| XDG_CONFIG_HOME | No | Standard base directory, used when SHIELDTV_CONFIG_DIR is unset. Default is ~/.config. | |
| SHIELDTV_CONFIG_DIR | No | Where the certificate, key and config.json live. Defaults to $XDG_CONFIG_HOME/mcp-server-shieldtv. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Physical role: Media Source. Connects into Onkyo AVR input 'strm-box' (which routes video downstream to the TV display and plays master audio). Controls an NVIDIA Shield TV over the Android TV Remote protocol. Call shield_get_status first to see whether it is on and what app is in the foreground, and shield_get_now_playing for the title and play state. The Shield must have been paired once with mcp-server-shieldtv pair.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| shield_get_statusA | Start here. Query Shield TV power state, reachability, foreground app, and volume. <use_case> Inspect Shield TV power, connectivity, active foreground package, and volume before issuing commands. </use_case> <important_notes>
|
| shield_get_now_playingA | Report what is playing: app, title, subtitle (artist or channel), play state, position in seconds. <use_case> Retrieve playback metadata and playback state of media currently active on the Shield. </use_case> <important_notes>
|
| shield_get_remotesA | List the Shield's Bluetooth remotes (e.g. a Harmony hub) and whether each works. <use_case> Diagnose unresponsive physical or hub remotes paired to the Shield over Bluetooth. </use_case> <important_notes>
|
| shield_rebootA | Restart the Shield TV. <use_case> Reboot the device when software is unresponsive or remotes require a cold reset. </use_case> <important_notes>
|
| shield_list_appsA | List the app names launch_app accepts (friendly name -> the link it opens). <use_case>
Discover valid app names for use with <important_notes>
|
| shield_send_keyA | Press a remote-control key on the Shield, e.g. DPAD_DOWN with repeat=3 to move down three rows. <use_case> Navigate Android TV interfaces, menus, and controls using directional pad, enter, back, and home. </use_case> <important_notes>
|
| shield_launch_appA | Launch an application on the Shield TV. <use_case> Launch streaming media apps (e.g. Netflix, YouTube, Plex) by friendly name. </use_case> <important_notes>
|
| shield_set_powerA | Wake the Shield ('on') or put it to sleep ('off'). <use_case> Manage device power state. </use_case> <important_notes>
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| shield_watch | Wake the Shield, open an app, and get to what you want to watch. |
| shield_remotes_not_working | Check the Shield's Bluetooth remotes and say how to fix one that's connected but dead. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| apps | |
| keys |
TDQS
Scored across 8 tools
Each tool has a distinct resource/action: app discovery vs launching, status vs now-playing vs remote diagnostics, power vs reboot vs key presses. There is no meaningful overlap that would cause misselection, and the descriptions clarify boundaries well.
All tool names use a consistent snake_case shield_ prefix followed by a clear action, e.g. shield_list_apps, shield_get_status, shield_launch_app, shield_set_power. The pattern is predictable throughout the set.
Eight tools is well-scoped for an Android TV/Shield controller: discovery, status, playback, remote diagnostics, power, launch, input, and reboot. Each tool earns its place without excess.
The set covers core lifecycle and control operations well, including discovery, status, playback metadata, launch, key input, power, and reboot. However, volume is reported by shield_get_status but there is no direct volume-setting tool, which is a minor but noticeable gap.