Scrcpy Mcp
Control a physical or emulated Android device from your agent via ADB and scrcpy for UI checks and automation during mobile ship prep.
Overview
io.github.JuanCF/scrcpy-mcp is a MCP server for the Ship phase that controls Android devices via ADB and scrcpy for agent-driven mobile testing.
What is this MCP server?
- Stdio MCP npm package scrcpy-mcp v0.2.3
- Android control through ADB plus scrcpy server integration
- ANDROID_SERIAL for multi-device targeting
- Optional ADB_PATH and SCRCPY_SERVER_PATH environment overrides
- Server version 0.2.3
- Three documented environment variables: ANDROID_SERIAL, ADB_PATH, SCRCPY_SERVER_PATH
- Stdio npm identifier scrcpy-mcp
What problem does it solve?
Mobile builders waste time switching between the IDE and adb/scrcpy terminals when an agent cannot see or act on a real device.
Who is it for?
Solo developers shipping Android apps who already use adb and scrcpy and want MCP-mediated device control from Claude Code or Cursor.
Skip if: iOS-only workflows, teams without physical devices or emulators, or builders who only need unit tests with no on-device UI.
What do I get? / Deliverables
After configuration, your agent can target a device serial and run ADB and scrcpy-backed actions for faster pre-release Android checks.
- Agent-initiated ADB commands against a selected Android serial
- scrcpy-backed screen mirroring and interaction hooks via MCP
- Repeatable device steps documented in the agent thread
Recommended MCP Servers
Journey fit
How it compares
MCP device automation layer, not a cloud device farm or mobile analytics SDK.
Common Questions / FAQ
Who is io.github.JuanCF/scrcpy-mcp for?
Android-focused solo builders and QA-minded developers who want their coding agent to operate phones and emulators through ADB and scrcpy.
When should I use io.github.JuanCF/scrcpy-mcp?
Use it during ship-phase testing and build-phase integration debugging when you need on-device reproduction steps driven from chat.
How do I add io.github.JuanCF/scrcpy-mcp to my agent?
Install scrcpy-mcp via npm stdio, set ANDROID_SERIAL if multiple devices appear in adb devices, optionally set ADB_PATH and SCRCPY_SERVER_PATH, then register the server in your MCP client.