Skip to main content
Glama
SDNick484

mcp-server-shieldtv

by SDNick484
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-server-shieldtv

No user-submitted related servers found.

    Related Servers

    • phone-control

      sheear
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables controlling an Android device from an MCP client via ADB, including wireless debugging discovery, UI-tree inspection, and performing taps, swipes, typing, app actions, and shell commands without relying on screen coordinates.
      1 npm
      MIT

    • ios-control-mcp

      als0m3
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables a macOS MCP client to control a real iPhone through CoreDevice services, including screenshots, normalized taps and swipes, text entry, hardware-button presses, and app launching or listing.
      MIT

    • vvd

      fortemate
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to operate and view the Vega Virtual Device through MCP: press remote keys, take screenshots, record video with sound, wait for screen changes, and check the TV safe area.
      46 npm
      MIT

    • scrcpy-mcp

      natalie59825
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible AI assistants to see and control Android devices through ADB and a fast device-control protocol, including screenshots, touch input, typing, app management, UI inspection, file transfer, shell commands, and audio/video streaming.
      365 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct action/resource: input (send_key, launch_app), power (set_power), reads (get_status, get_now_playing, get_remotes, list_apps), and lifecycle (reboot_shield). The only near-overlap, get_status vs get_now_playing, is clearly delineated (device state vs playback content).

    Naming Consistency5/5

    All eight tools follow a consistent snake_case verb_noun pattern (send_key, launch_app, set_power, get_status, get_now_playing, get_remotes, reboot_shield, list_apps). No mixing of conventions or vague verbs.

    Tool Count5/5

    Eight tools is well-scoped for a media-device controller, covering input, power, status, playback, remotes, and reboot without bloat. Each tool earns its place.

    Completeness4/5

    Core lifecycle (power, input, launch, status, playback, reboot) is well covered, and volume/pause are reachable via send_key. Minor gaps exist for explicit volume setting or text entry, but no dead ends for typical control workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources