XCRS Mobile & TV Automation — Claude Code MCP server
This MCP server lets an agent drive tests for mobile and TV apps across Apple simulators, Apple devices, Android phones, and Android TV.
Open on GitHubWhat XCRS Mobile & TV Automation does
XCRS gives an agent target-aware tools for exercising apps on Apple simulators, physical Apple hardware, Android phones, and Android TV devices. Its workflow puts Xcode, ControlKit, CoreDevice, and adb behind one MCP server.
Install the package with cargo install xcrs, then start the server using xcrs --mcp. Android support finds adb through ANDROID_SDK_ROOT, ANDROID_HOME, common Android SDK locations, or PATH. A device must have USB debugging enabled, and the host must be authorized before device_select can select it.
Android accessibility inspection and semantic ui_tap depend on the optional XCRS AndroidKit runner. Direct adb actions remain available without that companion. The same automation profile can also be started through the full CLI with smb --mcp --scope automation.
What it helps with
- test a mobile app on an Apple simulator
- exercise Android screens through
adb - select an authorized device for a run
- drive an Android TV application
- inspect an Android accessibility tree
Example prompts for the agent
- Use
device_selectto choose the connected Android device, then test the app launch. - Run a test flow against the app on an Apple simulator.
- Inspect the Android accessibility tree and use
ui_tapon the target control.
How to install XCRS Mobile & TV Automation
Install
The MCP registry has no launch command for it: see the repository README
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about XCRS Mobile & TV Automation
How do I install XCRS Mobile & TV Automation in Claude Code?
Run cargo install xcrs, then start the MCP server with xcrs --mcp.
What does XCRS Mobile & TV Automation do?
It gives an agent automation tools for app testing on Apple simulators, Apple devices, Android phones, and Android TV hardware.
What is required for Android testing?
adb must be reachable through ANDROID_SDK_ROOT, ANDROID_HOME, a standard Android SDK location, or PATH. Enable USB debugging and authorize the host; XCRS AndroidKit is also needed for accessibility inspection and semantic ui_tap.