emu-lab
Related Servers
Alternatives to emu-lab
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables an AI agent to lease its own Android emulator phone and drive it over stdio: reading the screen, tapping, typing, and opening apps, with every action leaving an audit line and screenshot. Leases keep one agent per phone, and a locked phone stays inert until an operator unlocks it on its own screen.10MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to lease clean or signed-in Android emulator clones as adb-accessible devices, list and release them, and optionally open a scrcpy mirror, with short-lived leases that can be reclaimed after a client reconnects.MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents and humans to lease exclusive Android emulator sessions for bounded periods via MCP or HTTP, with a live web UI for watching or taking over active sessions.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create and control isolated Android emulator sessions through MCP, including app launch, UI interaction, screenshots, and audio/screen recording. It supports session-keyed device allocation, recording retrieval, and optional local-only WebRTC viewing.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables an AI agent to safely drive Android emulators for app testing, including installing and launching apps, inspecting screens, tapping labeled UI elements, capturing screenshots, and running Flutter integration tests with strict device, argument, and job safeguards.MIT
- AlicenseAqualityCmaintenanceEnables an AI agent to boot and control an Android emulator — tapping, typing, scrolling, inspecting screens, reading logs and installing APKs — and to record those interactions as replayable, CI-ready test flows. Actions are captured by element text or id rather than coordinates, so the saved tests survive layout changes and rerun without the agent.181MIT
TDQS
Scored across 9 tools
Most tools target a distinct resource+action: status/screenshot are read-only, start/renew/release manage the lease, clock manages time, job polls async work. The only blur is between emu_smoke (which includes a notification shade check) and emu_check_notification, but the descriptions explain when to use each (self-test pipeline vs. externally triggered notification after a clock forward).
All tools share a consistent emu_ prefix and snake_case formatting, which makes the set highly predictable. There is minor mixing between noun-style names (emu_status, emu_clock, emu_screenshot, emu_job) and verb-style names (emu_start, emu_renew, emu_release, emu_check_notification), but the pattern is still readable.
Nine tools is well-scoped for an emulator lab server: lease lifecycle (status/start/renew/release), test operations (smoke/notification/clock/screenshot), and async job polling. Each tool earns its place with no obvious filler.
The surface covers the full lease lifecycle plus testing, time control, screenshots, and job polling, so core automation workflows have no dead ends. Minor gaps exist: no standalone install-APK tool outside emu_smoke, and no reboot/wipe/reset-device operation, though these are workaroundable or out of scope.