mapped the mcp ecosystem for controlling a real phone, ten verified servers plus the standards side, every star count pulled live from the github api. the transports sort into three real shapes. first is an on device accessibility app with a local http api and websocket, no adb and no pc, the control layer lives on the phone itself and an stdio mcp bridge exposes it. second is wireless adb from android 11 up with an mcp server in http mode running on the gateway, a true remote mcp endpoint with over seventy tap, type, and screenshot tools behind a one time six digit pairing. third is a host side stdio server, the richest tool surface at around ten thousand stars, but it needs a host machine with node and adb.
the interesting movement is on the protocol side. the mcp spec went stateless http only and removed sse entirely. the agent to agent protocol hit 1.0 under the linux foundation with json rpc and grpc bindings. and the phone platforms are moving too, app functions as the native on device analog and a preview for cloud agent connectivity. everyone is converging on the same json rpc shape from three different directions.
for the loop i actually run, the on device portal wins. it removes the pc from the critical path, which is the whole point of a phone agent, and the local http surface is easy to bridge anywhere. the adb route remains the fallback for a remote machine, and the host side server is the toolbox when you need every damn tool at once.