
Ghost in the Droid
io.github.ghost-in-the-droidPublished by GitHub account ghost-in-the-droidv1.3.2Updated Oct 24, 2026
Give any LLM agent a real Android or iPhone as its body. 62 MCP tools for mobile automation.
The publisher's own server: droid.monster — specs
Overview
Gives an AI assistant 62 MCP tools to see and control a real Android or iPhone screen: tap, swipe, type, launch apps, and run saved skills.
- What you can do
- Ghost in the Droid exposes 62 MCP tools for real-device mobile automation. Tools cover screen reading (screenshot, screen tree, OCR, element lookup), touch input (tap, swipe, long press, typing, hardware keys), app control (launch, list, force stop, intents), browser and iOS actions, clipboard and notifications, plus skills and batch flows. Android is driven over ADB; iOS is driven over Appium XCUITest and WebDriverAgent. It also ships a local dashboard, a scheduler, and a skill registry.
- When to use it
- Use it when an assistant needs to operate a physical phone rather than a simulated page: repeating app workflows, UI testing, scraping app screens, or running scripted multi-step tasks on one device or a device farm. It is a poor fit if you only need web browsing or if no phone or Mac is available.
- Requirements
- Local Python 3.10+ process, installed via uvx or pipx from the ghost-in-the-droid PyPI package. Android needs a phone with USB debugging and ADB on PATH; iOS needs macOS with Xcode, Appium 2 with the XCUITest driver, and a trusted device or booted simulator, enabled with GITD_ENABLE_IOS=1. Node.js 18+ is needed for the frontend dev server. Optional LLM keys include ANTHROPIC_API_KEY, OPENAI_API_KEY, and OPENROUTER_API_KEY; iOS settings use IOS_DEVICE_UDID, IOS_APPIUM_URL, IOS_BUNDLE_ID, and…
Installation
In SourceWeft
- Open Ghost in the Droid in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Ghost in the Droid
Summon a ghost into your phone.
It sees the screen. It taps the buttons. It never sleeps.
Website · Docs · Skill Hub · Releases
[License: MIT] [Python 3.10+] [62 MCP tools] [Android + iOS] [cloud or on-device] [MCP Toplist: Top 1% of 95K]
[Ghost driving nine real phones]
▶ Watch full HD with sound on YouTube · Download mp4
Nine agents. Nine real devices. One ghost. (Click to watch.)
The pitch, in one breath
Every AI agent can think. Almost none can touch a phone.
Ghost is the body. It gives any LLM agent a real Android phone or iPhone: it reads the screen, taps, swipes, and types through a clean tool surface, and it scales from one device on your desk to a whole phone farm. Point Claude Code, Codex, Antigravity, Cursor, your LangChain app, or a model running inside the phone itself at it, and your agent grows hands.
Bring your own brain. Keep the same body. MIT, forever.
Mix and match: the Ghost matrix
Ghost 1.3 is the only Android + iOS agent framework where platform, brain, and driver are all swappable. Pick one from each column. They all compose.
The Docker + KVM emulator pool is Android-only; iOS uses Apple's own simulator and Xcode signing, which are macOS-native.
The body stays the same 62 MCP tools no matter what you plug in. Every new model release is a free upgrade to your phone agent.
See it in action
Nine demos, one per feature, each recorded on real devices. Click any clip for the full mp4.
What It Does
Open-source Python framework for controlling Android and iOS devices from one agent harness. Android runs through ADB. iOS runs through Appium XCUITest and WebDriverAgent, with real iPhones as the target path and simulators for development and CI.
Define skills for any app, run them from the dashboard or API, scale across a phone farm.
The ghost taps what you'd tap
- Android control through ADB: tap, swipe, type, clipboard, shell, intents, and stealth variants
- iOS control through WebDriverAgent: screenshot, accessibility tree, tap, swipe, type, app launch, clipboard, browser actions
- Live phone screen streaming: Android MJPEG/WebRTC, iOS WDA MJPEG with screenshot fallback
- Interactive touch-to-tap on the streamed screen
- Multi-device phone farm with per-device job queues
Forge reusable skills for any app
- YAML-based UI element definitions per app
- Platform-specific selectors with
elements.yamlfor Android andelements_ios.yamlfor iOS - Python action classes with precondition checks
- Multi-step workflows that chain actions together
- Built-in skills for TikTok and Play Store
- iOS browser/news demo skill and smoke-level TikTok iOS workflows
- Skill Hub: browse, search, and install skills from the community registry
- Install from CLI:
android-agent skill install tiktok
Teach the ghost new tricks
- BFS-based auto app explorer: discovers every screen and transition
- LLM-assisted Skill Creator: chat with AI while viewing the live device stream
- The AI identifies UI elements and generates action/workflow code
Scale the haunting
- Multi-device phone farm with per-device job queues
- Bot runner: queue, schedule, and monitor automation jobs
- Per-device integration tests with Android screen recording or iOS WDA MJPEG recording
Platform Support
Why it is built this way
Skills cost $0. Thinking costs tokens. An agent should not pay an LLM to tap a button it has tapped a thousand times. Known workflows compile to skills: deterministic YAML + Python recipes that replay in seconds with zero LLM calls. Use AI for the unknown task, replay for the known one.
The phone is the easiest sandbox there is. Give the ghost an old Android with its own SIM and its own accounts, physically separate from your life. You already know how to set up a phone.
Zero-app by default. A fresh install touches nothing on the Android device: screen reads go through uiautomator, actions through adb shell input, no root, no accessibility service. Want it faster? The optional Portal companion app gives roughly 30x quicker UI reads. Want it private? On-device mode runs the whole loop inside the phone, nothing leaves it. All opt-in.
Local-first, cloud-optional. The server and dashboard run on your machine. With a local or on-device brain, your screenshots never leave your network. Pick a cloud brain and prompts go to that provider, same as any tool. Your call, always.
Requirements
- Python 3.10+
- Android: Android phone with USB debugging enabled and ADB on PATH (
adb devicesshould list your phone) - iOS: macOS with Xcode, Appium 2 + XCUITest driver, and a trusted iPhone or booted simulator
- Node.js 18+ (for the frontend dev server)
iOS Support
Ghost drives iPhones through Appium/WebDriverAgent with the same tool
surface: ios:<udid> device refs route tap/swipe/type/screenshot to WDA, and
iOS-aware browser primitives (open_url, read_news, extract_visible_text)
cover web tasks. Android-only tools (shell, launch_intent, Portal overlay)
return a clear platform error instead of failing silently.
iOS is opt-in: enable it with GITD_ENABLE_IOS=1 (or ios_platform_enabled=true
in .env). Wireless drive rides your Tailscale tailnet, so treat the tailnet as
the trust boundary. See docs/SETUP_IOS.md for Appium/WDA
setup, and on-device on iPhone
to run the model on the iPhone itself.
Quick Start
Zero-install with uvx (or pipx):
doctor prints a checklist with fix hints instead of a stack trace when something is missing (e.g. adb not on PATH). Prefer pipx? pipx install ghost-in-the-droid gives you the ghost-in-the-droid / android-agent commands.
Sign in with your Claude subscription (no API key)
If you have a Claude Max/Pro subscription, you don't need an API key. android-agent login signs you in through the claude CLI's own Anthropic OAuth flow and points Ghost at the claude-code provider:
Ghost never handles or stores your token; the claude CLI owns it, refresh included. doctor shows a green Claude subscription check once you are signed in. To use an API key instead, set ANTHROPIC_API_KEY (or OPENAI_API_KEY / OPENROUTER_API_KEY) and pick that provider.
Run fully local with Ollama (no keys, no cloud)
Select Ollama in the Phone Agent tab. Runs entirely on your machine with Ollama:
From a clone (for development)
iOS Quick Start
iOS support requires a Mac because Appium uses Xcode's XCUITest/WebDriverAgent stack. Real iPhones also require trust, Developer Mode, UI Automation permission when prompted, and WDA signing with an Apple development team.
For full real-device signing, simulator, WDA MJPEG, health recovery, scheduler, and MCP setup details, see docs/SETUP_IOS.md.
Environment Variables
Copy .env.example to .env (if provided) or create a .env file in the project root. The server reads configuration via Pydantic Settings. Optional variables include:
Give any AI agent a mobile body (MCP)
Ghost ships an MCP server with 62 tools for real-device control. Any MCP-compatible client can use them. Android serials receive the Android implementation; ios:<udid> refs route to the iOS backend where supported and return stable unsupported-platform errors for Android-only tools. One command wires it up:
uvx installs the package, builds an isolated env, and runs the server. No clone, no venv.
Other clients (Codex, Claude Desktop, Cursor, VS Code, Windsurf)
Claude Desktop (claude_desktop_config.json), Cursor (.cursor/mcp.json), Windsurf (mcp_config.json):
VS Code Copilot (.vscode/mcp.json) uses the same block under a "servers" key. Contributors who clone the repo get a ready .mcp.json, all 62 tools live on first claude launch.
The 62 tools, by category:
toggle_overlay, launch_intent, Android shell helpers, wireless ADB, and Play Store helpers remain Android-only and return stable platform errors on iOS.
Run the brain inside the phone
New in 1.3: the model can live on the device. The Ghost companion app embeds real inference engines, so the phone is both the body and the brain. Airplane mode on, agent still working, nothing leaving the device.
On iPhone, Qwen2.5 1.5B runs through llama.cpp on Metal and drives the phone's own UI, with an opt-in MLX engine for faster decode on Apple Silicon. Small models are kept honest with grammar-constrained decoding so tool calls always parse. Full detail on the on-device LLM page.
Skill Hub CLI
The skill registry lives in registry/ in this repo. Community skills are auto-discovered nightly from repos tagged android-agent-skill.
Teach the Ghost a New App
Two ways to forge a skill:
Community skill (your own repo): create a repo with skill.yaml, elements.yaml, actions, and workflows, tag it android-agent-skill, and it appears on the Skill Hub automatically (nightly scraper).
Official skill (PR to this repo): build and test as a community skill first, then open a PR adding it to registry/. CI validates, a maintainer reviews, and it gets the "Official" badge.
Each skill needs:
skill.yaml: metadata (name, version, app package or iOS bundle ID, supported platforms, actions, workflows)elements.yaml: Android UI element resource IDs and descriptionselements_ios.yaml: optional iOS selectors for XCTest accessibility treesactions/: Python classes extendingActionwithprecondition()andexecute()workflows/: Python classes extendingWorkflowwithsteps()
Prefer to let AI do it? The Skill Creator watches a live device stream and generates the action and workflow code while you narrate. Full guide in CONTRIBUTING.md.
The dashboard
A local-first control room at http://localhost:5055 (or :6175 in dev). WebRTC and MJPEG live streams, tap-on-screen, tracing, and every tab below.
Architecture
The flow: FastAPI backend on :5055 exposes device control, skills, bots, scheduling, and streaming. The Vue SPA talks to it over /api/*. Skills define per-app interaction (elements + actions + workflows). Device backends route by ref: bare serials use bots/common/adb.py, ios:<udid> refs use bots/common/ios.py and Appium/WDA. State lives in SQLite via SQLAlchemy 2.0 and Alembic.
Benchmark (sneak peek)
Early result, with the full methodology writeup still cooking: driven by Claude Code, Ghost completes 115 of 116 tasks (99.1%) on AndroidWorld, Google Research's benchmark for Android agents, on the unmodified upstream harness. Treat this as a preview rather than a citable number. The detailed writeup and trajectories are coming. Watch the releases.
Tech Stack
Running Tests
Most tests are unit/API tests and run without a live device. Live Android and iOS integration tests require the relevant device stack.
For iOS live smoke tests:
Get your Android device serial from adb devices.
Database Migrations
The project uses Alembic for schema migrations:
Contributing
The ghost gets stronger with every skill. See CONTRIBUTING.md for adding app skills (highest impact), writing actions and workflows, backend architecture, and the PR process. Join the community on the Skill Hub.
License
MIT. The ghost is free. The ghost is open source. The ghost is yours.
Source: README.md at commit 7c09f6c
Tools
0Version history
1- v1.3.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Droid integrations
droid.monster — specs
monster.droidOfficial publisher
A remote MCP server for looking up sourced specifications of commercial robots, comparing models, and finding compatible spare parts.
CodeDroid
Published by GitHub account codedroid-team
Lets an MCP client drive your real Android phone: read the screen, tap, type, swipe, take screenshots, install APKs and run adb commands.

ZennoDroid: tasks
com.zennolab
Local Windows MCP server that lets an assistant create, configure, start and monitor ZennoDroid automation tasks and their sessions.

ZennoDroid: ProjectMaker
com.zennolab
Connects an AI assistant to ZennoDroid ProjectMaker so it can read and edit the open project, run it, and record actions.

ZennoDroid: devices of running tasks
com.zennolab
ZennoLab sidecar that lets an assistant inspect and drive the Android devices of running ZennoDroid tasks: screen, elements, apps and gestures.