MCP server for managing GeeLark Cloud Phones and preparing them for Android automation over ADB.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"geelark-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# geelark-mcp An MCP (Model Context Protocol) server for managing **GeeLark Cloud Phones** through the official GeeLark OpenAPI and preparing running devices for **Android automation over ADB**. > **Unofficial / community project.** > This project is not affiliated with or endorsed by GeeLark. High-level Android **UI** automation (screenshots, UI hierarchy, selectors, clicks, text input, swipes) is handled by [`uiautomator2-mcp-server`](https://github.com/tanbro/uiautomator2-mcp-server), a separate package you register as a second MCP server alongside this one. The two share a local ADB server and device serial. Running geelark-mcp on its own is not a supported setup: without the UI server you can only drive the screen by raw coordinates. > **"Hey Claude, create a fresh GeeLark phone, install TikTok, open it, skip > onboarding, scroll the For You feed for two minutes and stop the phone."** > > `geelark-mcp` provisions the phone, installs the app, and establishes ADB; > `uiautomator2-mcp-server` handles the on-screen interaction. --- ## Features - List, create, start, stop, delete and inspect GeeLark cloud phones. - Install apps from the GeeLark catalog; start/stop/uninstall apps. - Enable ADB and retrieve normalized ADB connection info (secret withheld by default). - Connect a phone to the local ADB server, including the GeeLark `glogin` flow. - Install local APKs over ADB (sandboxed to an allowed directory, size-limited). - Execute allowlisted ADB diagnostics/UI input as argv lists; raw commands require two flags. - Bounded logcat, file push/pull, and low-level coordinate fallbacks. - Query / cancel / retry GeeLark automation tasks (read + lifecycle only). - Readiness and setup tools to hand a shared serial to `uiautomator2-mcp-server`. - A one-shot `prepare_phone_for_automation` workflow with per-stage results. ## Project boundaries geelark-mcp handles GeeLark authentication and requests, cloud phone lifecycle, application/file/automation-task management…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.