"Using a mobile phone for remote control functionality" matching MCP servers:

A local stdio MCP service that lets an authorized AI assistant see and operate one Android phone through ADB, with screenshots, on-device OCR, text/coordinate taps, swipes, and app launching, plus optional scrcpy-based Chinese and emoji input. Includes zoomed inspection, a 0-1000 coordinate ruler, and crosshair preview with post-tap feedback so actions can be verified against the real screen.

Enables looking up mobile phone numbers for a list of contacts by chaining your own Prospeo, Lusha, ContactOut, and FullEnrich keys until a provider returns a number. Returns one row per contact with the number in E.164 format, line type, country, a Do Not Call flag where reported, and the provider credits spent.

An MCP server that lets AI agents control Android TVs via ADB, including searching and playing content across streaming services, managing power and volume, and sending remote control commands.

An MCP server that enables AI assistants to control TVs on a local network through natural language commands. It currently supports Roku devices, allowing users to launch apps, manage playback, and navigate menus.

Manage local/SSH/WinRM remote hosts via MCP, providing tools for exec, filesystem, screen, process, serial console, and configuration.

Enables an MCP client to read conversations and send SMS from your own number through a paired Android phone over KDE Connect on the local network, with no cloud relay or gateway account. It exposes thread listing, message reading, contact lookup, and sending tools that hand requests to the phone via D-Bus.

A Model Context Protocol server that enables scalable mobile automation through a platform-agnostic interface for iOS and Android devices, allowing agents and LLMs to interact with mobile applications using accessibility snapshots or coordinate-based interactions.

Enables coding agents to observe and control an authorized Android phone over ADB through MCP tools and a JSON CLI. It supports UI inspection, screenshots, taps, swipes, typing, key presses, app listing, and launching.

Enables an agent to drive an Android phone attached via USB by reading the screen, deciding next steps, executing actions, and verifying results, all through adb.

Lets AI agents drive real iPhones and Androids hosted in the cloud over HTTPS — taking screenshots, inspecting on-screen elements, tapping, typing, swiping, and launching apps — with no pairing, adb, or Mac required. It can run locally over stdio or as a hosted streamable HTTP endpoint supporting API keys and OAuth sign-in.

Enables an AI client to control an Android emulator or USB device over ADB by selecting a device, inspecting the UI hierarchy, and performing taps, swipes, text entry, key presses, and app launches. It relies only on Android platform-tools and exposes a compatible tool surface for phone automation.

Enables an AI agent to boot and control an Android emulator — tapping, typing, scrolling, inspecting screens, reading logs and installing APKs — and to record those interactions as replayable, CI-ready test flows. Actions are captured by element text or id rather than coordinates, so the saved tests survive layout changes and rerun without the agent.

Enables agents and LLMs to automate, inspect, and scrape native iOS and Android apps across simulators, emulators, and real devices through a platform-agnostic interface using accessibility snapshots or screenshot-based coordinates. It provides device, app, screen, input, log, and crash management tools, including optional cloud device reservation.

MCP server that gives your AI agent a real Android phone (ERIUS PHONE): read the screen, tap, type, launch apps, read crash logs.

Enables an AI agent to lease its own Android emulator phone and drive it over stdio: reading the screen, tapping, typing, and opening apps, with every action leaving an audit line and screenshot. Leases keep one agent per phone, and a locked phone stays inert until an operator unlocks it on its own screen.

Enables mobile device automation for Android (via ADB) and iOS Simulator (via simctl), allowing you to control devices with natural language through screenshots, UI interactions, text input, and app management.

Exposes Android device automation tools to MCP clients, letting AI agents inspect UI trees, interact with elements, launch/stop apps, run shell commands, transfer files, and manage events/tasks over adb/uiautomator2 without installing anything on the device.

Enables AI coding agents to test and automate Android apps rendering UI in OpenGL/Vulkan/Metal surfaces via screenshot-based vision tools for tapping, swiping, long-pressing, and recording, without accessibility tree dependency.

Deterministic, LLM-first control of Word documents (.docx). An agent reads the outline, finds text by phrase, and applies edits as tracked changes and comments in one atomic batch, with a safety layer that refuses edits based on a stale read and rolls back failed batches. It works on .docx files directly, and can also drive an open document in Microsoft Word on Windows or in LibreOffice Writer.

An MCP server that lets AI agents drive real Android apps on emulators/devices, returning screen state, logs, and screenshots after every action, and learns a navigation map of the app for efficient route-based interaction.