AirPlay Screen

airplay-mcp (MIT, on PyPI) turns this computer into an AirPlay receiver. The user mirrors their iPhone or iPad to it, and you get the screen through MCP tools. Everything stays on this machine. The receiver only listens on the local network and makes no outbound connections.

It only works when this machine is on the same Wi-Fi as the phone. A cloud VM or VPS can't see the phone. Neither can a network behind a VPN or a guest network, because they block mDNS. If that's the setup, tell the user so and stop.

One-time setup

Tell the user what you are about to install or download before you run each step.

1. Install the server: uv tool install --upgrade airplay-mcp or pip install --upgrade airplay-mcp (0.1.4 or later includes the emulator libraries the native receiver needs). Note the absolute path of the airplay-mcp executable for step 4, because its install folder is often not on the gateway's PATH. Check it with airplay-mcp --help.

2. Pick a receiver with the user. Recent iOS sends no video until the receiver passes Apple's FairPlay check, and there are two ways to handle that:

   • native (default): run the FairPlay code from the user's own iPhone firmware in a local emulator. Any OS, but extraction reads ~2.5 GB of firmware and needs ~20 GB free disk while it runs. The extracted files must never be uploaded or shared.
   • uxplay: install UxPlay 1.73 or later, which handles FairPlay itself. Easy on macOS (brew install uxplay). Linux distro packages are often older (Ubuntu 24.04 ships 1.68), so check the version before choosing it. On Windows it has to be built with MSYS2: follow the README steps.

3. native only: extract the FairPlay files.

   1. Install ipsw: brew install blacktop/tap/ipsw on macOS. Elsewhere, download the release build for the OS and CPU from its GitHub releases and put it on PATH. On Linux, ipsw also needs apfs-fuse to read the firmware's APFS image (7-Zip is not a substitute: it can't decompress the LZBITMAP files in the dyld cache). Install it from the distro if packaged, or build it from source, and set IPSW_APFS_FUSE_PATH if it isn't on PATH.
   2. Ask the user for the phone model (Settings > General > About) and map it to an identifier such as iPhone17,3 with ipsw device-list.
   3. In a POSIX shell, in a folder the user wants to keep (for example ~/airplay-fp), run the commands below. Replace MODEL with the identifier. --remote reads only the system image from Apple's CDN (~2.5 GB) instead of downloading the whole IPSW (~13 GB); it takes a few minutes.

      URL="$(ipsw download ipsw --device MODEL --latest --urls | head -1)"
      ipsw extract --dyld --dyld-arch arm64e --remote -o fw "$URL"
      ipsw dyld extract fw/*/dyld_shared_cache_arm64e -o fpdir AirPlayReceiver AirPlaySupport CoreUtils AirPlaySender
      

   4. Check that fpdir/ holds four files, then delete fw/ (~7 GB).

4. Register the MCP server with absolute paths for the command and the FairPlay folder:

   • native:

     openclaw mcp set airplay '{"command":"/absolute/path/to/airplay-mcp","env":{"AIRPLAY_FP_EMU_DIR":"/absolute/path/to/airplay-fp/fpdir"}}'
     

   • uxplay:

     openclaw mcp set airplay '{"command":"/absolute/path/to/airplay-mcp","env":{"AIRPLAY_RECEIVER":"uxplay"}}'
     

     Add AIRPLAY_UXPLAY_PATH if uxplay isn't on PATH.

   Confirm it with openclaw mcp list. The tools appear in a new session, or after the gateway reloads.

5. Firewall: the first time the receiver runs, allow it through the firewall. The phone connects over TCP and mDNS (UDP 5353).

Using it

1. start_receiver, then tell the user: Control Centre > Screen Mirroring > "AI Screen" (PIN 3939 if asked). With native, the first connection takes about 35 seconds while the emulator warms up.
2. wait_for_change blocks until the first frame arrives, and afterwards until the screen next changes. Pass since_frame=N for the frame you hold.
3. get_screen to look, or save_screen to write a full-resolution file and return only its path. Use mode='changes' after the user acts, and region to read small detail. read_screen_text is cheaper for text-heavy screens, if it is installed.
4. Repeat 2 and 3, then stop_receiver when done.

Troubleshooting

• The phone doesn't list "AI Screen". Check the network and the firewall (see above).
• It pairs but the screen stays blank (native). AIRPLAY_FP_EMU_DIR is wrong or incomplete, or airplay-mcp is older than 0.1.4 (uv tool upgrade airplay-mcp).
• To see the log: airplay-mcp --autostart -v (plus --fp-emu-dir <path> or --receiver uxplay).