Provides tools for connecting to Android devices over WiFi using ADB, taking screenshots, listing connected devices, retrieving device information, and managing device connections.
Used for package management and running the server, with commands for installation, building, and starting the MCP server.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@ADB Screenshot MCP Server take a screenshot of my connected Android device"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A Model Context Protocol (MCP) server that provides ADB tools for connecting to Android devices over WiFi and taking screenshots.
WiFi Connection: Connect to Android devices over WiFi using ADB
Screenshot Capture: Take screenshots of connected devices
Device Management: List devices, get device info, and disconnect
Remote Access: Perfect for accessing devices on the same network
Related MCP server: Android ADB MCP Server
ADB (Android Debug Bridge) installed and in your PATH
Android device with USB debugging enabled
For WiFi connection: Device and computer on the same network
npm install
npm run buildConnect device via USB first
Run: adb tcpip 5555
Disconnect USB and find device IP address
Use the adb_connect_wifi tool with the IP address
adb_connect_wifi: Connect to device over WiFi
ip_address: Device IP address (required)
port: Port number (default: 5555)
adb_screenshot: Take a screenshot
output_path: Save location (default: screenshot.png)
device_id: Specific device (optional)
adb_list_devices: List all connected devices
adb_disconnect: Disconnect from WiFi device
ip_address: Device IP address (required)
port: Port number (default: 5555)
adb_device_info: Get device information
device_id: Specific device (optional)
npm startEnable WiFi ADB: adb tcpip 5555
Connect: Use adb_connect_wifi with device IP
Take screenshot: Use adb_screenshot
Disconnect: Use adb_disconnect when done
Connect to an Android device over WiFi using ADB
Inputs: ip_address (required), port.
Get information about a connected device
Inputs: device_id.
Disconnect from a WiFi ADB device
Inputs: ip_address (required), port.
List all connected ADB devices
Inputs: no named parameters.
Take a screenshot of the connected Android device
Inputs: output_path, device_id.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
An authenticated remote MCP server for user-owned devices and one-shot capability invocation.
MCP server for static security analysis of Android source code
A Model Context Protocol server for Wix AI tools