Termux MCP Server
Related Servers
Alternatives to Termux MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables text-based control of Android devices through Claude Code using accessibility tree automation. Supports UI interaction, app launching, text input, gestures, and navigation without requiring screenshots.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude or any MCP agent to see and operate a real Android phone over adb, with fast screen reads, tap/type/swipe actions, app launching, deep links, and brand-aware setup guidance, all without admin rights or an Android SDK.MIT
- AlicenseCqualityBmaintenanceEnables AI agents to control Android phones, emulators, redroid containers, iOS devices, and cloud-hosted devices through a perceive-act-verify loop of screen reading, taps, gestures, typing, and app launching. Exposes 138 tools for driving screens, elements, and files over adb, Portal APIs, and ios-portal without running ARM-only code on the device.9401MIT
- AlicenseAqualityDmaintenanceEnables AI agents to fully control Android devices through over 30 tools for app management, UI automation, and vision-based analysis via ADB. It supports multi-device management, action recording, and smart execution strategies ranging from UI hierarchy parsing to coordinate-based interaction.37182 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables programmatic control of Android devices via ADB, supporting UI automation, app management, screen capture with OCR, and file transfers through the Model Context Protocol. It allows MCP-compatible clients like Claude Desktop and Cursor to interact directly with physical or emulated Android devices.3Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to remotely control Android devices in the cloud via P2P WebRTC, providing tools for screenshots, touch input, file management, and automation scripts.6 npmMIT
TDQS
Scored across 57 tools
Each tool has a clearly distinct purpose, even when covering similar domains (e.g., input_text vs. input_chinese_text, list_android_packages vs. list_installed_packages). Detailed descriptions eliminate ambiguity, making it easy for an agent to select the correct tool.
All tools follow a consistent verb_noun pattern in snake_case (e.g., get_battery_status, take_screenshot, send_sms). The naming is predictable and logically structured, adhering to a single convention throughout.
With 57 tools, the count is high but justified by the extensive domain coverage (device info, UI automation, file operations, communication, sensors, etc.). While a few tools could potentially be merged, the overall scope earns its size.
The tool set comprehensively covers the core needs of an Android phone automation server: device information retrieval, UI interaction, input methods, app management, file operations, media, communication, and system actions. There are no obvious gaps for typical use cases.