TVWizard

Control Android TV from any AI. 21 MCP tools: keys, apps, titles, playback, volume, observe.

TVWizard is an MCP server published by ai.djwizard that exposes twenty-one tools for controlling an Android TV device. It communicates over streamable_http transport. The tool set covers six functional areas: keypress input, application management, reading on-screen titles, playback control, volume adjustment, and observation of device state. An AI agent can use the key tools to simulate remote button presses and navigate the interface. The app tools let the agent launch, switch, or manage installed applications. The title tools allow the agent to read what text appears on screen, identifying the current content or menu. The playback tools provide play, pause, stop, and related media controls. The volume tools enable adjustment of audio levels. The observe tools let the agent poll or monitor device state without physical interaction. Once installed, an AI agent can operate the television through conversational commands and automated routines, making it possible to build text or voice-driven automations for entertainment systems. The canonical name is ai.djwizard/tvwizard and the registry slug is aidjwizard-tvwizard. Source code is available in the GitHub repository fizzious1/TVWizard-mcp. No required environment variables are declared.

Use cases

  • use it to send remote keypresses to an Android TV from a conversational agent
  • use it to launch or switch applications on a television programmatically
  • use it to read on-screen titles to understand what content is currently displayed
  • use it to play, pause, or otherwise control media playback via AI commands
  • use it to raise or lower TV volume through automated routines
  • use it to observe device state and build reactive entertainment workflows

When to use it

  • you need an AI agent to act as a remote control for Android TV
  • your automation runs over HTTP and can use streamable_http transport
  • you want to integrate TV commands into a voice or chat assistant
  • you need programmatic access to playback and volume without a physical remote

When not to use it

  • you need to control non-Android TV platforms such as webOS, Tizen, or Roku
  • you require transport mechanisms other than streamable_http
  • you need an officially maintained or licensed package, as none is declared
  • you need tools that interact with content providers rather than the TV device itself