Mobile Xray MCP
Related Servers
Alternatives to Mobile Xray MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to view and analyze screenshots from React Native/Expo applications for AI-powered mobile UI development. Integrates with Claude, Cursor, VS Code and other MCP-compatible editors.6 npm15MIT

Argentofficial
AlicenseAqualityAmaintenanceEnables AI assistants to interact with iOS Simulators and Android Emulators, allowing autonomous app development, UI interaction, profiling, and debugging through natural language.762,849Apache 2.0- AlicenseBqualityDmaintenanceEnables AI agents to capture screenshots from Android devices and emulators, and manage connected devices for UI analysis and testing. Supports device listing, screenshot capture, and integrates with Claude Desktop, Gemini CLI, and GitHub Copilot.238 npm24MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to write and run mobile UI tests on Android and iOS simulators via natural language, supporting native and WebView apps without Appium.38318 npmMIT
- AlicenseAqualityCmaintenanceEnables AI assistants to build, drive, and observe Android/KMM apps end-to-end through ADB and Gradle, with tools for UI automation, error capture, and testing.3320 npmMIT
- AlicenseCqualityDmaintenanceEnables comprehensive control of Android devices via ADB for Flutter development, UI testing, and visual QA workflows. Provides 60+ tools for device management, UI inspection, app testing, performance profiling, and debugging through natural language.77MIT
TDQS
Scored across 3 tools
Each tool targets a distinct concern: capturing screenshots, listing simulators, and checking platform support. There is no overlap or ambiguity between them.
Most tools follow a get_ pattern, but check_supported_platforms uses check_ instead. This is a minor deviation from an otherwise clear verb_noun convention.
Three tools is a reasonable count for a focused utility server. It is not overly sparse, though it could benefit from one or two more related tools to feel more substantial.
The tool set covers basic simulator operations and platform discovery, but lacks common related operations such as booting a simulator or retrieving device details. It feels incomplete for broader mobile testing workflows.