scrcpy-mcp
Provides full vision and control over Android devices via ADB and scrcpy, enabling AI agents to take screenshots, tap, swipe, type, launch and manage apps, inspect UI elements, transfer files, run shell commands, manage clipboard, stream/record audio and video, and perform device management tasks.
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., "@scrcpy-mcptake a screenshot of my Android screen"
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.
scrcpy-mcp
MCP server that gives AI agents full vision and control over Android devices via ADB and scrcpy.
Connect any MCP-compatible AI assistant (Claude Code, OpenCode, Cursor, VS Code Copilot, etc.) to your Android device. The AI can see the screen, tap, swipe, type, launch apps, inspect UI elements, transfer files, and run shell commands.
Features
44 tools covering screenshots, input, apps, UI automation, shell, files, clipboard, video streaming, and audio streaming/recording
scrcpy-first: uses scrcpy's binary control protocol for 10-50x faster input and near-instant screenshots (~33ms)
ADB fallback: interaction tools work without scrcpy — slower but always available (the audio tools
start_audio_stream/audio_record_startand the video stream require scrcpy)Image-returning screenshots: the AI actually sees the screen, not just a file path
UI element finding:
ui_find_elementreturns tap coordinates so the AI can act on what it seesAudio streaming & recording: stream device audio to host speakers (
start_audio_stream) or capture to.wav/.opus(audio_record_start)Clipboard that works on Android 10+: scrcpy bypasses the restrictions that break ADB-only solutions
Related MCP server: adb-mcp
Prerequisites
Required
Requirement | Install | Verify |
Node.js 24+ | nodejs.org or |
|
ADB (Android Platform Tools) |
| |
Android device with USB debugging (Android 11+ for audio) | Settings → Developer Options → USB Debugging |
|
Optional (for enhanced performance)
Requirement | Install | Benefit |
scrcpy | 10-50x faster input, ~33ms screenshots | |
ffmpeg |
| Required for scrcpy video stream decoding, audio recording, and audio clip capture |
ffplay | Usually packaged with ffmpeg | Required for audio playback and the MJPEG viewer window |
Device setup
Enable Developer Options: Settings → About Phone → tap "Build Number" 7 times
Enable USB Debugging: Settings → Developer Options → USB Debugging
Connect device via USB
Accept the RSA fingerprint prompt on the device
Verify:
adb devicesshould show your device asdevice(notunauthorized)
Installation
# Run directly with npx (no install needed)
npx scrcpy-mcp
# Or install globally
npm install -g scrcpy-mcpMCP Client Configuration
Claude Code
claude mcp add android -- npx scrcpy-mcpOr add to .mcp.json in your project root:
{
"mcpServers": {
"android": {
"command": "npx",
"args": ["scrcpy-mcp"]
}
}
}OpenCode
Add to .mcp.json:
{
"mcpServers": {
"android": {
"command": "npx",
"args": ["scrcpy-mcp"]
}
}
}Cursor
Settings → MCP → Add Server:
{
"android": {
"command": "npx",
"args": ["scrcpy-mcp"]
}
}Claude Desktop
Edit ~/.config/Claude/claude_desktop_config.json (Linux) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"android": {
"command": "npx",
"args": ["scrcpy-mcp"]
}
}
}VS Code (GitHub Copilot)
Add to .vscode/mcp.json:
{
"servers": {
"android": {
"command": "npx",
"args": ["scrcpy-mcp"]
}
}
}Customizing Environment Variables
If you need to configure custom options (such as pointing to a non-standard scrcpy-server path), you can add the "env" object to your server configuration. For example:
{
"mcpServers": {
"android": {
"command": "npx",
"args": ["scrcpy-mcp"],
"env": {
"SCRCPY_SERVER_PATH": "C:\\path\\to\\scrcpy-server"
}
}
}
}Note: only set SCRCPY_SERVER_VERSION if version auto-detection fails — it overrides detection, so a stale value causes the version mismatch described in Troubleshooting. Match it to your installed scrcpy (scrcpy --version).
Note: On Windows, remember to double-escape backslashes (\\) in your configuration paths.
OpenCode users: OpenCode uses
"environment"instead of"env"for passing environment variables to MCP servers. Replace"env"with"environment"in the example above if you're configuring scrcpy-mcp inopencode.json.
Tool Reference
Session Management
Tool | Description |
| Start a scrcpy session. When active, input and screenshots use the fast path (10-50x faster). |
| Stop the scrcpy session. Tools fall back to ADB. |
| Report which scrcpy-server version the session pushes and where that version was resolved from. |
start_session options:
Option | Default | Description |
|
| Max video frame dimension in pixels |
|
| Max frames per second |
|
| Capture audio (see the heads-up below) |
|
| Audio source ( |
|
| Keep device playback audible with |
|
| Keep the device on for the whole session (scrcpy |
| (device setting) | Screen-off timeout in seconds for the whole session (scrcpy |
Both screen-awake options are temporary: scrcpy restores the device's original values when the session ends, including when a tool restarts the session to turn audio on.
Video Streaming
Tool | Description |
| Start an HTTP MJPEG video stream and open a viewer window (ffplay). Auto-starts a scrcpy session if needed. |
| Stop the video stream and close the viewer window. |
Audio Streaming & Recording
Heads up: Audio capture is opt-in and requires Android 11+. The default source
outputusesREMOTE_SUBMIX, which mutes the device's own speakers while capturing — the audio is moved to the host, not copied. UseaudioSource: "playback"withaudioDup: true(Android 13+) to keep the device audible. Recordings are saved on the host filesystem.
Tool | Description |
| Stream device audio to the host's speakers via ffplay. Restarts the scrcpy session if it was started without audio. |
| Stop streaming audio to the host. |
| Start recording device audio to |
| Stop the recording and finalise the host-side file. |
| Capture a bounded clip of device audio and return it as an audio content block. Restarts the scrcpy session if needed. |
Device Management
Tool | Description |
| List all connected devices with serial, state, and model |
| Get model, Android version, screen size, SDK level, battery |
| Wake the device screen |
| Turn the screen off |
| Rotate the screen (requires active session) |
| Pull down the notification panel (requires active session) |
| Pull down the quick settings panel (requires active session) |
| Collapse notification/settings panels (requires active session) |
| Enable WiFi ADB and connect to the device wirelessly. Returns the connection address. |
| Disconnect from a wireless ADB device |
Vision
Tool | Description |
| Capture the screen and return it as an image. ~33ms with scrcpy, ~500ms via ADB. |
| Start recording the screen to a file on the device |
| Stop recording and optionally pull the file to the host |
Input Control
All input tools use scrcpy (~5-10ms) when a session is active, otherwise fall back to ADB (~100-300ms).
Tool | Description |
| Tap at screen coordinates |
| Swipe from one point to another |
| Long press at coordinates |
| Drag from one point to another |
| Type a text string into the focused field |
| Send a key event: HOME, BACK, ENTER, VOLUME_UP, VOLUME_DOWN, POWER, etc. |
| Scroll at a position (dx=horizontal, dy=vertical) |
App Management
Tool | Description |
| Launch an app by package name. Prefix with |
| Force-stop an app |
| Install an APK from the host machine |
| Uninstall an app |
| List installed packages, optionally filter by name or system/third-party |
| Get the current foreground app and activity |
UI Automation
Tool | Description |
| Dump the full UI hierarchy as XML |
| Find elements by text, resource ID, class name, or content description. Returns tap coordinates. |
Shell & Files
Tool | Description |
| Execute an arbitrary ADB shell command and return the output |
| Push a file from the host machine to the device |
| Pull a file from the device to the host machine |
| List directory contents on the device |
Clipboard
Tool | Description |
| Get clipboard content. Uses scrcpy to bypass Android 10+ restrictions. |
| Set clipboard content. Pass |
Performance
Operation | scrcpy (session active) | ADB fallback |
Screenshot | ~33ms | ~500ms |
Tap / Swipe | ~5-10ms | ~100-300ms |
Text input | ~5ms | ~100-300ms |
Clipboard | ~10ms | unreliable on Android 10+ |
Start a session once at the beginning to unlock the fast path:
start_session → take screenshots → tap → swipe → ...Environment Variables
Variable | Default | Description |
|
| Path to the ADB binary |
| (none) | Default device serial, overrides auto-detection |
| (auto) | Path to the scrcpy-server binary |
| (auto) | Version of the scrcpy-server binary |
|
| Path to the ffmpeg binary |
|
| Path to the ffplay binary (video stream viewer and audio playback) |
When only one device is connected, tools auto-detect it. With multiple devices, pass the serial parameter explicitly or set ANDROID_SERIAL.
Troubleshooting
adb devices shows unauthorized
Accept the RSA fingerprint prompt on the device. If the prompt doesn't appear, revoke USB debugging authorizations in Developer Options and reconnect.
start_session fails
Make sure scrcpy is installed and the scrcpy-server binary is accessible. On Windows, add the folder containing both scrcpy.exe and scrcpy-server to your PATH, or set SCRCPY_SERVER_PATH to the full path of the scrcpy-server file.
File vs Directory: Ensure
SCRCPY_SERVER_PATHpoints directly to thescrcpy-serverfile itself (e.g.C:\path\to\scrcpy-server), NOT to its parent folder.Android Directory Conflict: If you previously pushed a directory to the server path,
/data/local/tmp/scrcpy-server.jaron the Android device might have been created as a folder. Runadb shell rm -rf /data/local/tmp/scrcpy-server.jarto delete it.Version Mismatch: The client must send the exact version of the
scrcpy-serverfile it pushes. To guarantee that, the server and the version are never resolved separately — one scrcpy install is resolved as a pair, and the version comes from the client belonging to that same install. The install is found in this order:SCRCPY_SERVER_PATHif set (its client is then located beside the server, or one prefix step away at../../bin/scrcpy); otherwise thescrcpyon your PATH, whose server is located beside it or at../share/scrcpy/scrcpy-server; otherwise whatever your package manager reports (dpkg,pacman,rpm,apk,brew). A symlinked client is resolved to its real directory before its counterpart is derived, so a link farm such as Homebrew'sbin/scrcpypairs with the install it points at rather than with the link's own directory.SCRCPY_SERVER_VERSIONoverrides the detected version if set. So on Windows, or when a GUI app launches the MCP without your shell PATH, pointingSCRCPY_SERVER_PATHat a server inside a complete scrcpy install is enough on its own, and it wins even if a different scrcpy comes first on your PATH — note that reading the version runs that install's executable, so pointSCRCPY_SERVER_PATHonly at an install you trust (the same trust the server file itself already requires, since it gets pushed to your device and executed there). If no client can be found for the resolved server (for example a lonescrcpy-serverdownloaded from the releases page), the client falls back to the default version and the server may exit with a version-mismatch error; setSCRCPY_SERVER_VERSIONto your installed version (e.g.,"4.1"). Run theversiontool to see which version is in use and where it was resolved from. See the Environment Variables table above.
Screenshots are slow (~500ms)
Start a scrcpy session with start_session to enable the fast video stream path. Requires scrcpy and ffmpeg.
expand_notifications / expand_settings / collapse_panels fail
These tools require an active scrcpy session. Run start_session first.
The device screen keeps turning off during long automations
Start the session with stayAwake: true (plugged in only) or screenOffTimeout: <seconds>, which also works on battery. Both are restored when the session ends.
start_audio_stream says ffplay was not found
Install ffmpeg (ffplay ships with it), or set FFPLAY_PATH to the binary. The same applies to audio_record_start and FFMPEG_PATH.
Audio recording is silent
REMOTE_SUBMIX only captures what apps are actually playing — a recording made while nothing plays is digital silence, which is expected. Also check the device is not muted, and remember the default output source moves the audio to the host, so the device goes quiet while capturing. Use audioSource: "playback" with audioDup: true (Android 13+) to keep it audible.
Audio tools report audio as unavailable Audio capture needs Android 11+ (SDK 30). On older devices the session still works for video, input, and clipboard.
Clipboard doesn't work on Android 10+ ADB clipboard access is restricted on Android 10+. Start a scrcpy session — the scrcpy clipboard protocol bypasses this restriction.
Multiple devices connected
Pass serial to each tool or set the ANDROID_SERIAL environment variable.
Security
This server provides full control over connected Android devices. The shell_exec tool can run arbitrary commands, and file_push/file_pull can read and write any file accessible to the shell user.
The server runs locally over stdio — it is not exposed to the network
ADB requires USB debugging to be explicitly enabled on the device
The device must accept your host's RSA key on first connection
Only connect devices you own and trust the AI agent you are using
License
MIT — see LICENSE
This server cannot be deployed
Maintenance
Related MCP Connectors
Melaya is a remote MCP server. It gives an assistant hands on your own Android phone and browser: it reads the screen through the accessibility tree, then taps, types and navigates inside the apps and sites you allow-list, with no per-app API. It also builds, schedules and runs agent pipelines across 6k+ connected tools. OAuth 2.1, nothing to install.
Control real Android and iOS devices with LLM agents — tap, swipe, type, automate flows.
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.
A real Android phone in the cloud for MCP agents: observe the screen, act, reset to a saved state.
Related MCP Servers
- AlicenseAqualityAmaintenanceMCP server that gives AI agents full vision and control over Android devices via ADB and scrcpy. Supports screenshots, input, apps, UI automation, shell, files, and clipboard.38254 npm115MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to control Android devices via ADB, providing tools for screen capture, tap/swipe/input, app management, and diagnostics. Works locally over USB or WiFi and integrates with MCP clients like Claude and Cursor.1MIT
- AlicenseAqualityCmaintenanceEnables AI agents to control, inspect, and automate Android devices, Waydroid containers, and AVD emulators over ADB. Provides tools for screenshots, UI-hierarchy text-based tapping, gestures, key presses, text input, app management, and raw shell commands.12MIT
- AlicenseNot gradedqualityCmaintenanceEnables Android device control over ADB through MCP tools that mirror CLI subcommands, including taps, swipes, text input, app launch/stop, screenshots, UI inspection, and running action sequences. Coordinates from screenshots are converted to screen coordinates automatically.MIT