Android-MCP and androidtvmcp
These are complements designed for different Android automation scopes: the general-purpose Android device automation server pairs with the specialized Android TV remote control server to provide comprehensive coverage from standard devices to TV-specific interfaces.
About Android-MCP
CursorTouch/Android-MCP
MCP Server for interacting with Android Devices.
Implements an MCP server that bridges LLM agents to Android devices via ADB and the Accessibility API, enabling app navigation, UI interaction, and automated testing without computer vision models. Exposes a rich toolset including gesture controls (tap, swipe, drag), text input, view hierarchy inspection, and shell command execution—with typical action latency of 2-4 seconds. Integrates directly with Claude Desktop and any LLM/VLM, supporting Android 10+ devices and emulators.
About androidtvmcp
pigeek/androidtvmcp
A Model Context Protocol (MCP) server that provides Android TV remote control functionality to AI assistants and other MCP clients.
Provides automatic device discovery, app management, and state monitoring through a modular architecture with separate device manager, command processor, and network layer components. Implements stdio-based MCP transport with configurable retry logic and includes developer tools for testing command processing and MCP integration independently.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work