mait.sh1.132.1

Private beta: features and content may change. No warranty; use at your own risk.

Install and configure mcp-scrcpy

Check that MCP Scrcpy and the Android connection tools are installed, connect it to your agent, find your device and see its screen.

Beta
OverviewGet startedUse casesToolsProblems and fixesAll components
Steps

Five steps from install to your first screenshot.

MCP Scrcpy is an MCP tool: you check it is installed, point your agent at it, and then ask in plain language. Use a device or an emulator whose state you may change. These steps only press Home and record the screen: nothing here installs an app or reboots the device.

  1. Capturedmcp-scrcpy 0.3.5
    Check the version
    $ mcp-scrcpy --version
    mcp-scrcpy 0.3.5
    Check that adb sees the device
    $ adb devices
    Step 1 of 5

    Check that it arrived

    The MAIT image ships mcp-scrcpy and updates it with the image. mcp-scrcpy is a Linux program. On macOS and Windows, mcp-scrcpy runs in the managed Linux environment that AIDC Launch provides. Check that it runs, and that adb can see your device.

    The device must show the state device. If it shows unauthorized, accept the prompt on the device screen; if it shows offline, reconnect it. See mait-image.

    What you get

    A version that answers and a device in the device state.

  2. mcpServers entry
    {
  "mcpServers": {
    "scrcpy": {
      "command": "mcp-scrcpy",
      "args": ["serve"]
    }
  }
}
    Step 2 of 5

    Connect it to your agent

    Any client that accepts an mcpServers launch entry uses this shape. Place it where your client keeps server configuration and restart the client.

    Keep one session open: control belongs to the session that adopted the device, so separate one-off commands cannot share it. If you reach your tools through the registry instead, add scrcpy once with mcp_registry_add and the tools carry the scrcpy__ prefix (registry guide).

    What you get

    A client that starts the service on its own, and an agent that can call the 31 scrcpy tools.

  3. Capturedmcp-scrcpy 0.3.5
    YouWhich Android devices can you see?
    Tool calllist_devices {}
    What happensReturns {"devices":[]}: ADB answered and no device is attached to this machine.
    AgentI can reach ADB, but no device is connected. Attach one, or start an emulator, and ask me again.
    Step 3 of 5

    Find the device

    Ask your agent which devices it can see. It calls list_devices and answers with each device's identifier, state and model. With more than one device, the agent passes the identifier as deviceSerial in every later call.

    With a device attached, the same call returns one record per device with its identifier, state, model and transport_id.

    What you get

    The identifier of the device to work on, or a clear answer that none is connected.

  4. Illustrative conversation
    YouShow me the screen, press Home, and show me again.
    Tool callscrcpy_screenshot { "deviceSerial": "<serial>", "inlineImage": true }
    What happensReturns the text Screenshot captured from the device model with its size, an inline PNG and the saved file's path.
    Tool callscrcpy_adopt { "deviceSerial": "<serial>" }
    What happensReturns "adopted <serial> for control". From now on control calls may leave the serial out.
    Tool callscrcpy_key { "key": "home" }
    What happensReturns "key sent".
    Tool callscrcpy_screenshot { "inlineImage": true }
    AgentThe first picture showed an app; the second shows the home screen, so the key worked.
    Step 4 of 5

    See the screen and press a key

    The agent takes a screenshot, claims the device, presses Home and takes a second screenshot. A successful key result proves the device accepted the key; only the second picture proves the screen changed.

    Screens larger than 1920 pixels on the longer side are scaled down in the picture, but taps use real device pixels. The first screenshot on a machine without the decoder takes longer while it downloads.

    What you get

    A picture of the device's own screen, and a first input you have checked yourself.

  5. Illustrative conversation
    YouI am done. Release the device.
    Tool callscrcpy_unadopt {}
    What happensReturns "unadopted <serial>".
    AgentThe device is released. Screenshots stay on this machine under the cache folder until you delete them.
    Step 5 of 5

    Release the device

    Control lasts until you release it or the session ends. Ask the agent to release the device when it is done.

    Releasing the claim does not undo what you changed on the device, such as a rotation lock, the display power or the clipboard.

    What you get

    The device free for the next session, with the files it produced still on your machine.

Result

An agent that can see and use a device.

MCP Scrcpy is installed, connected to your agent, and able to show you the device and press its keys. Treat screenshots, recordings, clipboard text and logs as confidential: they stay on your machine until you delete them. Keep the socket in a private directory only your account can enter.

Next

Where to go next.