androidtvmcp and mobile-mcp
These two tools are ecosystem siblings, where `pigeek/androidtvmcp` appears to be a specialized implementation of an MCP server providing Android TV remote control, while `runablehq/mobile-mcp` is a more general MCP server for broader mobile automation, both operating within the Model Context Protocol ecosystem.
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.
About mobile-mcp
runablehq/mobile-mcp
A Model Context Protocol (MCP) server that provides mobile automation capabilities.
This project helps developers automate interactions with Android mobile devices using large language models (LLMs). It takes structured UI information from a mobile device and allows an LLM to control the device's actions without relying on visual input like screenshots. Mobile app developers, QA testers, and automation engineers can use this to build intelligent mobile automation workflows.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work