ADB Screenshot MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| adb_connect_wifiB | Connect to an Android device over WiFi using ADB |
| adb_screenshotB | Take a screenshot of the connected Android device |
| adb_list_devicesB | List all connected ADB devices |
| adb_disconnectC | Disconnect from a WiFi ADB device |
| adb_device_infoC | Get information about a connected device |
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 5 tools
Each tool has a clearly distinct purpose with no ambiguity: connecting, disconnecting, listing devices, getting device info, and taking screenshots. The actions and targets are well-defined and non-overlapping, making it easy for an agent to select the correct tool.
All tools follow a consistent 'adb_verb_noun' pattern (e.g., adb_connect_wifi, adb_device_info). The naming is uniform, using snake_case throughout, with clear verbs that describe the action and nouns specifying the target or resource.
With 5 tools, the server is well-scoped for its purpose of managing ADB connections and taking screenshots. Each tool earns its place, covering essential operations without being overly sparse or bloated, making it efficient for the domain.
The toolset covers core workflows for ADB device management and screenshot functionality, but there are minor gaps such as missing tools for advanced device interactions (e.g., adb_shell for commands) or file transfer. However, agents can likely work around these for basic use cases.