adb-tv-mcp
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| adb_devicesB | List connected ADB devices with serial + state. |
| adb_pairB | Pair with an Android 11+ device via Wireless debugging (6-digit code + IP:port from 'Pair device with pairing code'). |
| adb_connectB | Connect to a device ADB endpoint host:port (wireless-debug 'connect' port). |
| adb_disconnectC | Disconnect a device (host:port) or all if omitted. |
| adb_screenshotA | Capture the screen as a PNG image so the agent can SEE the device. |
| adb_screenrecordB | Record the screen for N seconds, pull it to a local mp4, return the path. |
| adb_keyA | Press a remote/D-pad key by name (UP DOWN LEFT RIGHT ENTER BACK HOME POWER MENU VOLUME_UP PLAY_PAUSE SEARCH ASSIST ...) or numeric keycode. |
| adb_tapC | Tap the screen at pixel x,y. |
| adb_swipeC | Swipe/drag from x1,y1 to x2,y2 over duration ms. |
| adb_textC | Type a string into the focused field. |
| adb_launchC | Launch an app by package name (e.g. com.spotify.tv.android). |
| adb_open_urlC | Open a URL on the device (cast a webpage/dashboard/game you built to the TV). |
| adb_start_intentA | Fire a generic Android intent via |
| adb_list_appsB | List installed packages; third_party=true for user-installed only. |
| adb_current_appB | Report the foreground app/activity. |
| adb_installB | Install an APK from a local file path onto the device. |
| adb_uninstallC | Uninstall an app by package name. |
| adb_pushB | Copy a local file to the device. |
| adb_pullC | Copy a file from the device to local. |
| adb_getpropB | Read device properties (all, or filter by substring). |
| adb_settingsC | Get or put an Android setting. namespace = system|secure|global. |
| adb_logcatB | Dump recent logcat lines (optionally grep-filtered). |
| adb_rebootC | Reboot the device. mode: normal | recovery | bootloader. |
| adb_shellC | Run a shell command on the device. Use only with devices that you own. |
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 24 tools
Most tools have clearly distinct purposes (screenshot vs screenrecord vs tap vs swipe are all different actions). The only mild overlap is adb_shell vs adb_start_intent vs adb_open_url, since all involve running commands on the device, but their descriptions clarify distinct use cases. Overall agents can distinguish between them well.
The adb_ prefix is applied to all 24 tools, giving a strong and clear prefix pattern. However, the verb portion varies in style: verbs like screenshot, reboot, shell, push, pull are nouns/imperatives mixed together, and there's no action-object convention (e.g. adb_launch vs adb_launch_app). The ubiquitous adb_ prefix creates consistency, but the verb style is somewhat inconsistent.
24 tools is near the high end of what feels appropriate for a device-management server, and the count is justified by the breadth of ADB capabilities (network, input, apps, screen, properties). Each tool addresses a distinct real operation, making the size defensible, though it does edge toward heavy.
The surface covers the core ADB workflows well: connectivity (pair/connect/disconnect/devices), input (tap/swipe/key/text), screen (screenshot/record), app lifecycle (launch/install/uninstall/list/current), file transfer (push/pull), properties/settings, shell, logcat, and URL/intent launching. Minor gaps include no clear reboot/couple of state management helper, but the essential ADB operations are present with no dead ends.