Icemoon
← Home
AI copilot
Control a real iPhone with AI — the Icemoon MCP server
Last updated: July 16, 2026
Icemoon gives AI assistants hands. Its built-in MCP server exposes every iPhone connected to your Mac as a set of tools Claude can call: read the screen, tap, swipe, type on the real keyboard, navigate apps, run batches, schedule jobs. You describe the goal in chat — the AI plans and executes it on the physical device, and you watch the plan progress live on your dashboard. Stock iOS, no jailbreak.
What is MCP?
The Model Context Protocol is an open standard, introduced by Anthropic, that lets AI assistants call external tools and data sources. A weather MCP server lets the AI check the forecast; Icemoon's MCP server lets it operate a real iPhone. Anything you could do with your thumb, the AI can now do on your behalf — with the same human-like touch synthesis Icemoon uses everywhere: unique Bezier-curve swipes, natural timing, typing on the real iOS keyboard.
Connect your iPhone
Icemoon runs on your Mac; iPhones connect over USB. The one-time setup installs a signed automation runner on the device — no jailbreak, the phone stays on stock iOS.
The MCP server registers itself
Icemoon configures Claude Desktop automatically — open Claude and the device tools are simply there. Any other MCP-compatible client (Claude Code, Cursor, and others) can connect to the same local server.
Describe the goal
The AI reads the screen, identifies where it is, builds a step-by-step plan, and executes it — while the plan and each step's status stream live to your dashboard. If the app changes mid-task, the AI sees the new screen and adapts.
What the AI can do
| Category | Tools | What it means |
|---|---|---|
| See the screen | get_visible_elements · identify_screen · get_screen_info · screenshot_save | The AI reads real UI elements — buttons, labels, fields — not just pixels, so it understands what it's looking at. |
| Touch & type | tap · swipe · double_tap · touch_hold · pinch · scroll · type_text · smart_type · press_button | Every gesture is synthesized human-like: unique curves, natural timing, the real iOS keyboard. |
| Navigate | open_app · navigate_to · wait_for_screen · get_app_list | One call takes the AI to a target screen: it detects where it is, finds the path, walks it, and verifies arrival. |
| Go fast | run_batch · plan_create · plan_update_step | Multi-step sequences execute in one round-trip; plans stream progress to your dashboard as they run. |
| Device control | lock_device · unlock_device · pasteboard_set · video_record · set_location | Lock, unlock, clipboard, screen recording, and simulated GPS location for testing location features. |
| Orchestrate | list_devices · connect_device · schedule_task · list_saved_scripts | Pooled connections across the fleet — the AI switches devices instantly, runs saved automations, and schedules future jobs. |
Things you can just ask
Why a real device matters
Simulators don't run most real-world apps, don't have real cameras or push tokens, and behave differently under load. An AI agent that operates an actual iPhone works with the truth: the app store build, the real keyboard, the actual network conditions. For testing, that's fidelity; for daily workflows, it's the only option — your accounts and apps live on real hardware.
How this differs from other iOS MCP servers
It is worth being straight about this: Icemoon is not the only MCP server that can drive a physical iPhone. Open-source projects do it too, and they work — they wrap Appium or go-ios and talk to WebDriverAgent, and if you want one iPhone under an AI assistant they are a reasonable free choice.
The difference shows up at the second device, and then at the twentieth.
- A fleet, not a target. The open-source servers list your devices and let the AI pick one to drive. Icemoon treats the whole set as the unit of work: the same goal can fan out across every connected iPhone, each with its own account, its own proxy and its own pace.
- You never touch WebDriverAgent. With the DIY stacks, WDA has to be built and signed for each device, every session needs its own port, and a signing certificate that expires takes the setup down. Icemoon builds, signs and installs the runner for you, and does it again when it needs to. You still install Xcode once — that part is Apple's rule, not ours.
- Human-like touch. A raw WDA tap is an instantaneous, perfectly straight event at exact coordinates. Icemoon moves along curved paths with varied timing and pressure, because the gestures are the part that has to look real.
- State that survives the chat. Accounts, proxies, schedules and recorded flows live in the app, not in the conversation. The AI is one way to drive Icemoon — the schedule keeps running when nobody is talking to it.
If you are automating one iPhone for development, take the free option. If you are running a farm, the plumbing is the product.
Get started
Setup takes about 15 minutes end to end: install Icemoon, connect an iPhone over USB, open Claude. The AI copilot and MCP server are included on every plan — Solo, Farm and Scale.
FAQ
What is an MCP server for iOS?
MCP (Model Context Protocol) is an open standard that lets AI assistants like Claude call external tools. Icemoon's MCP server turns real iPhones into such tools: the AI can read the device screen, tap, swipe, type, navigate apps, and schedule tasks — on stock iOS, no jailbreak.
Which AI assistants work with Icemoon?
Icemoon registers itself with Claude Desktop automatically on setup. Because MCP is an open standard, any MCP-compatible client — Claude Code, Cursor, and others — can connect to the same server.
Does the AI see my phone's data? Where does it run?
The MCP server runs locally on your Mac, and devices connect over USB — Icemoon sends nothing to its own servers. Screen content is shared with the AI assistant you connect (for example Claude) only while you're actively giving it tasks, under that assistant's privacy terms.
Can the AI control several iPhones at once?
Yes. Device connections are pooled: the AI can switch between connected iPhones instantly or target a specific device for a single action, and you watch progress for the whole fleet on the dashboard.
Do I need to write code to use the AI copilot?
No. You describe the goal in plain language in the chat. The AI reads the screen, builds a step-by-step plan (visible live on your dashboard), and executes it. Anything it does can also be recorded and saved as a repeatable automation.
Which plans include the MCP server?
Every paid plan includes the AI copilot and MCP server — Solo, Farm and Scale. The plans differ by how many iPhones you connect (1 / 5 / 20) and by the Farm and Scale extras — captcha solving, the accounts and proxy manager, and HTTP API access. See pricing for the full breakdown.
Why not use a free open-source iOS MCP server?
For a single iPhone under an AI assistant, a free open-source MCP server is a reasonable choice — several of them drive real devices through Appium or go-ios and WebDriverAgent. The difference appears at scale: those servers pick one device from a list, while Icemoon fans a goal out across a fleet with an account and proxy per device, builds and signs WebDriverAgent for you instead of leaving it to you per device, moves along curved gesture paths rather than firing instant taps, and keeps accounts, proxies and schedules running when no chat session is open.