Mobile Agent Harness runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 4 Oct 2026.
Android device automation for AI agents: MCP server, CLI, and plugin runtime over adb.
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
subprocess.run(["adb", "connect", s], capture_output=True, timeout=10)
out_dir = os.path.join(engine.harness_dir, pkg)
exec(compile(src, path, "exec"), mod.__dict__)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
MCP server for Safari DevTools — browser debugging and automation for AI coding agents
MCP server for Android emulator automation via ADB.
MCP server for Android automation with UI interaction, screenshots, and device control
MCP server for iOS and Android Mobile Development, Automation and Testing
MCP server for browser automation via Vercel's agent-browser CLI
MCP server for browser automation with AI agent
Android launcher with an embedded MCP server for owner-controlled device automation.
MCP server for Appium mobile automation on iOS and Android devices with test creation tools.
Answers built from our own checks of this server.