agent-device runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 17 Sep 2026.
MCP server for mobile app automation: verify, control, and debug iOS, Android, TV, and desktop apps
What the code does
We read the source, 19 h ago · rules 3dff92dd89df
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.
const profileDir = path.join(dir, definition.slug);
const child = spawn([...adb.args], {
vm.runInNewContext(expression, sandbox, {
export type LockedRequestBinding = {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
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.
Alternatives to agent-device
same job, measured the same wayMCP server for iOS and Android Mobile Development, Automation and Testing
MCP server for Appium mobile automation on iOS and Android devices with test creation tools.
MCP server for Android automation with UI interaction, screenshots, and device control
MCP server with WebdriverIO for browser and mobile app automation (iOS/Android via Appium)
MCP server for Roku device automation — deploy, ECP control, screenshots, and debug console
AI-powered mobile device automation for Android and iOS devices, emulators, and simulators
Drive Android & iOS mobile-app automation from your AI agent on locally connected devices.
MCP tools for testing mobile and TV apps on iOS simulators, Android phones, and Apple/Android TV.
agent-device — questions
Answers built from our own checks of this server.