mcp · handle iphone_control_toolkit
iOS Control MCP · job 80%Android Autopilot MCP · job 72%Karagöz · job 77%icemoon_mcp · job 81%idb_mcp · job 72%MobileMCP · job 75%android-adb-mcp · job 75%Android Use · job 73%mobilenext_mcp · job 77%phone-mcp · job 76%phoneos · job 85%thumbs · job 79%Agent Phone Harness · job 75%TrollMCP · job 80%jb-p1lot · job 73%iphone-mcp · job 86%iphone-control · job 93%AureDroid · job 74%Askew · job 71%ios-device-mcp · job 76%iPhone Use · job 78%DroidMCP · job 73%aCelery · job 71%bridge4simulator · job 72%rPlay SDK · job 84%Thumbly · job 84%android-lite · job 75%ESP32 to iPhone · job 78%mirroir_mcp · job 83%LemonMCP · job 75%android_remote_control_mcp · job 74%omnidebuglink · job 75%AutoMobile · job 80%Mobilerun MCP · job 77%Zeptap · job 86%xcodebuildmcp · job 75%OpenPhone · job 76%Phone for AI · job 75%iPhone Mirror MCP · job 75%DSH Phone Control · job 71%expo-mcp-bridge · job 75%DroidBridge · job 75%Percentages are graph-similarity metadata, not suitability scores. A graph edge answers “is it connected” — plan fit and comparable cost are checked below.
Pick the exact reference and alternative series. Each history is separate; gaps stay gaps.
This view calls the same get_evidence tool your agent would — chart, table and MCP response describe the same records. Watch the reference series