Mobile device interaction automation via MCP
npx -y @kaeawc/auto-mobileAdd this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"dev-jasonpearson-auto-mobile": {
"command": "npx",
"args": [
"-y",
"@kaeawc/auto-mobile"
]
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
AutoMobile is an MCP server for Mobile device interaction automation via MCP. It supports STDIO transport.
Use the generated config in Install. This server runs with npx -y @kaeawc/auto-mobile; add any required environment variables before starting your client.
Choose the Claude Desktop tab in Install and copy the config for npx -y @kaeawc/auto-mobile. Add required environment variables before starting Claude Desktop.
Choose the Claude Code tab in Install and copy the config for npx -y @kaeawc/auto-mobile. Add required environment variables before starting Claude Code.
Choose the Codex tab in Install and copy the config for npx -y @kaeawc/auto-mobile. Add required environment variables before starting Codex.
Choose the Cursor or VS Code tab in Install and copy the config for npx -y @kaeawc/auto-mobile. Add required environment variables before starting Cursor or VS Code.
AutoMobile uses STDIO transport. Use the package or command config in Install.
AutoMobile inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
AutoMobile does not advertise a verified auth requirement. If discovery fails, it may still need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
@kaeawc/auto-mobilestdio | npm | 0.0.13 | None advertised |