XCRS Mobile & TV Automation

io.github.smbcloudXYZPublished by GitHub account smbcloudXYZv1.1.0Updated Oct 31, 2026

MCP tools for testing mobile and TV apps on iOS simulators, Android phones, and Apple/Android TV.

VerifiedSTDIODesktop onlyBrowser Automation Developer Tools

Server details

Identifier: io.github.smbcloudXYZ/xcrs
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account smbcloudXYZ for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.smbcloudXYZ%2Fxcrs.svg)](https://sourceweft.com/mcp/io.github.smbcloudXYZ%2Fxcrs?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP server that lets an assistant drive iOS simulators, Apple devices, Android phones and TV devices to test mobile and TV apps.

What you can do: Select and manage test targets across Apple simulators, physical Apple devices, Android phones and Android TV
Run app automation workflows on the chosen target through Xcode, ControlKit, CoreDevice and adb
Inspect Android accessibility trees and perform semantic UI taps when the optional AndroidKit companion runner is installed
Fall back to raw adb actions for Android when the companion runner is not installed
When to use it: Useful when you want an assistant to exercise or debug a mobile or TV app on simulators, emulators or connected devices as part of a testing workflow, rather than driving the UI by hand.
Requirements: Runs as a local process installed with cargo install xcrs and started with the --mcp flag. Apple targets rely on Xcode and related Apple tooling; Android tools need adb found via ANDROID_SDK_ROOT, ANDROID_HOME, standard SDK locations or PATH. Android devices must be connected over USB with debugging enabled and authorized by the host. The optional AndroidKit companion runner is needed for accessibility-tree inspection and semantic taps.

Before you install

It controls real devices and simulators, so automation actions can change app state or data on the selected target. Android devices must be explicitly authorized for USB debugging, which grants the host broad control. No credentials or environment variables are declared by the server itself.

Installation

In SourceWeft

Open XCRS Mobile & TV Automation in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

XCRS Mobile & TV Automation

Cross-platform MCP tools for testing mobile and TV apps on Apple simulators, physical Apple devices, Android phones, and Android TV devices. XCRS combines Xcode, ControlKit, CoreDevice, and adb behind one target-aware automation workflow.

MCP Registry name: mcp-name: io.github.smbcloudXYZ/xcrs

Run the MCP server

Android tools use adb from ANDROID_SDK_ROOT, ANDROID_HOME, the standard Android SDK locations, or PATH. Connect a device with USB debugging enabled and authorize the host before selecting it with device_select.

For Android accessibility-tree inspection and semantic ui_tap, install the optional XCRS AndroidKit companion runner. Raw adb actions remain available without it.

The same automation profile is available from the full smbCloud CLI:

Desktop apps

A desktop target drives an application through a W3C WebDriver endpoint, for example tauri-driver for a Tauri app on Linux (it proxies WebKitWebDriver). Select it once:

webdriver_url cannot be combined with an Apple or Android field. The desktop tools then use the stored target.

Tool	Desktop behaviour
`app_install_launch`, `app_launch`	Start a WebDriver session, which launches the binary at `app_path` (`app_id` for `app_launch`). `bundle_id` is ignored.
`app_terminate`	End the session and close the app.
`ui_describe`	The page source.
`ui_element_list`	Visible interactive elements with label, id, role and rectangle, up to 200.
`ui_tap`	Click the one displayed element whose id, name, test id, ARIA label, title or text equals `element`. Zero or several matches are an error.
`input_text`	Type into the focused element.
`screen_capture`	A PNG of the window.

The other tools return an error saying they have no desktop meaning. A running app cannot be attached to: the session is the launched app.

Repository

Source and documentation are available in the smbcloud-cli repository.

Source: crates/xcrs/README.md at commit 6abc38c

Tools

SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

v1.1.0LatestOct 31, 2026
v1.0.0Oct 31, 2026
v0.7.5Oct 20, 2026
v0.5.2Sep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts
Declare a license in the repository or the registry entry.