Enables wireless screenshot capture from Android devices over WiFi for UI debugging and visual inspection during development, with automatic device detection and connection capabilities.
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., "@Android Screenshot MCP Server screenshot my Android phone"
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.
MCP server for taking screenshots of Android devices over WiFi. Useful for UI debugging and visual inspection during development.
Wireless screenshot capture via ADB
Automatic device detection and connection
Smart pairing for first-time setup
UI/UX debugging and layout inspection
Related MCP server: Android MCP Server
Install dependencies:
npm installAdd to Claude Code:
claude mcp add android /path/to/android-screenshot-mcp/src/index.jsEnable wireless debugging on your Android device:
Settings → Developer Options → Wireless Debugging
Note the IP address and ports shown
The tool automatically detects connected devices. If no device is connected, it will guide you through the setup.
For already connected devices:
screenshot phoneFor new connections, provide the IP and port shown in your device's wireless debugging settings:
screenshot phone with 192.168.1.100:41737If this is your first time connecting, you'll need to pair first:
screenshot phone with 192.168.1.100:41737 and pairing code 123456 port 54321The tool accepts several formats:
deviceIP: "192.168.1.100:41737" - IP with port included
deviceIP: "192.168.1.100", debugPort: 41737 - Separate parameters
Natural language like "192.168.1.100:41737 and pairing: 123456 port 54321"
Android 11+ device with wireless debugging
ADB installed on your computer
Same WiFi network for both devices
This error has been fixed in the latest version. If you still encounter it, ensure you're running the latest code.
Verify wireless debugging is enabled on your device
Check that the IP address and port match what's shown on your device
Make sure both devices are on the same WiFi network
Try disabling and re-enabling wireless debugging
Note: The wireless debugging port changes when you toggle it off/on
Pairing codes expire quickly (usually within 2 minutes)
Generate a fresh pairing code right before using it
The pairing port is different from the wireless debugging port
Once paired, you shouldn't need to pair again unless you reset connections
The tool uses wireless ADB connections and remembers your last successful connection for convenience. Each screenshot session will:
Check for already connected devices first
If none found, try to reconnect to the last used device automatically
If that fails, prompt for connection details
Successfully connected devices are saved to ~/.android-screenshot-mcp/config.json
This means after your first successful connection, the tool can often reconnect automatically without needing the IP and port again.
Connect to an Android device and take a screenshot. Use when no device is connected.
Inputs: deviceIP (required), debugPort, pairingPort, pairingCode, +1 more.
Take a screenshot of any connected Android device. Uses existing ADB connections or connects wirelessly if device info provided.
Inputs: deviceIP, debugPort, pairingPort, pairingCode, +1 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 2 tools
The two tools have overlapping purposes with unclear boundaries. Both are focused on taking Android screenshots, with 'connect_and_screenshot' implying connection and capture, while 'screenshot' can also handle connections if needed. This creates ambiguity about when to use each tool, as their descriptions suggest similar functionality with minor variations in connection handling.
The tool names follow a consistent snake_case pattern and use clear verbs ('connect_and_screenshot', 'screenshot'). While the naming is technically consistent, the inclusion of 'connect_and_' in one name versus not in the other creates a minor deviation in structure, but overall the naming is readable and follows a predictable style.
With only 2 tools, the server feels thin for its purpose of Android screenshot management. While it covers basic screenshot functionality, the limited tool count may restrict more advanced operations or device management tasks, placing it in the borderline range where the scope seems underdeveloped.
The tool set is significantly incomplete for Android device interaction. It only provides screenshot capabilities without covering essential operations like listing devices, managing connections, handling multiple devices, or performing other common ADB commands. This creates gaps that could lead to agent failures when broader device control is needed.
Drive real devices from your AI Coding tool. Embed a client SDK (Unity, Godot, Flutter, iOS/macOS, Android, React Native, Web) in your app, then capture screenshots, traverse the UI tree, inject taps and key events, and run automated test tasks on the physical device over a secure relay.
Give your AI agent a real cloud Android phone: push APKs, drive it, get screenshots and logs.
remote debug iOS/Android/Unity/Godot/Flutter/RN/Web on real-device.ui-tree/screenshots/taps,tests.
Rent a real Android phone: install your build, see the screen, tap, type and read Logcat.
