Apple Cluster ControliEasyRunAI Automation

Apple Cluster Control with iEasyRun: Driving a Batch of iPhones with AI

How EasyClick Apple cluster control and the iEasyRun AI workstation work together: what each piece does, how to install both, how devices get connected, and how to choose between AI chat, workflows, and MCP. Includes install links and a troubleshooting checklist.

7 min read

Someone asked me last week whether iEasyRun is redundant. He had been using the central control for a while, saw another tool sitting next to it in the same folder, and figured it was the same thing with a different name.

He is not the only one who asked. The two programs live on the same PC, their icons sit side by side, and both look like tools for operating phones. But the work they do is split fairly cleanly.

Let me start with the division of labor, then get into how they work together.


1. What each piece actually does

EasyClick iOS USB central control handles devices and connections. You plug an iPhone into a USB cable, and it detects the phone, mirrors the screen, lists dozens of devices in one view, starts and stops scripts in bulk, pushes files, and shows runtime status. That is all execution-layer work.

iEasyRun is a phone automation AI workstation, and it handles decisions. You describe what you want in plain language, and it breaks the task into steps, decides where to tap, how long to wait, and when to take a screenshot and look. That is the thinking part.

The official docs put the relationship plainly: iEasyRun takes over the AI agent capability that used to live inside the central control and upgrades it into a standalone workstation, while script development, cluster control, and screen mirroring still follow the EasyClick documentation.

In other words, the AI agent that used to be buried in the central control was pulled out into its own program and given more room.

As for why they were split, my read is that the two iterate at different speeds. The central control touches USB drivers, mirroring pipelines, and device compatibility, so every update needs care. AI capabilities shift every few months, and a slow release cadence falls behind. Split apart, each moves at its own pace.

What that means in practice: you install both, and you run both.


2. What you are installing

The install entry point is here. Run the downloader and pick your options:

https://ieasyclick.com/downloader

On the welcome screen, select the iOS USB version plus the AI workstation. On the next screen, tick three packages:

First, the iOS USB central control and mirroring, which detects devices. Second, the iOS developer image archive, which the central control needs to run. Third, the iEasyRun phone automation AI workstation.

That covers the PC. The phone still needs an IPA or automation will not run. The free enterprise-signed build is at https://ieasyclick.com/ec-tj-mainapp and installs through i4Tools.

A few details are easy to miss:

Before installing and on first launch, temporarily disable antivirus, Windows Security real-time protection, and the firewall. Turn them back on once everything runs. Skip this and the central control service can get blocked, which shows up later as devices that mysteriously will not connect.

Two programs need to be started manually: new-central-control.exe in the central control folder, and iEasyRun-AI-Agent.exe in the workstation folder. If the workstation does nothing on double-click, install MicrosoftEdgeWebview2Setup.exe from the same folder and retry.

Both programs need to be signed in with the same account. You can open each interface with only one signed in, but device syncing will misbehave.

The full illustrated walkthrough is at https://www.ieasyrun.com/docs/install-ios-usb/. It is screenshot by screenshot, and following it beats reading text when you get stuck.


3. From plugging in to the device showing up

This is where beginners usually stall. Following the order makes it much easier.

Connect the cable, then tap Trust This Computer on the phone. Open i4Tools and confirm it can see the device. If i4Tools sees it, your cable, port, and drivers are fine. If it cannot, stop and fix that first.

Now open the central control and bind your license in the license center. Choose the USB device license, not the mirroring license. A mirroring license only shows you the screen; it cannot run automation tasks. The symptom of getting this wrong is tasks that go out and then nothing happens.

Once the license is bound, the device should show as online inside the central control. Only then start iEasyRun, open Devices on the left, and the same phone should appear in the list with an online status.

A few phone-side permissions also need attention, or things will fail later in strange ways. Turn on all three keep-alive settings in the main program and confirm the floating window appears. Enable photo library access, or steps that save and read images will fail. The custom keyboard is optional and only needed when a task has to type on a keyboard. Chat, tapping, pasting, and image recognition do not need it.


4. Three ways to drive iPhones with AI

Once installed, there are three ways to work, and the differences matter.

The most direct is AI chat. Click Chat on the left, start a new conversation, pick one online phone, and type what you want in the box at the bottom, something like open Settings and wait three seconds. Send it and the phone moves.

There is also a refinement mode inside chat, and it is worth understanding. It suits the case where you only have a vague idea. You describe it loosely, and the AI asks back about the layout, how long to wait after a tap, and what to do if a dialog appears. After a few rounds it turns your request into a clearly ordered script, and you confirm before it executes. For multi-step tasks on complex screens, talking it through first lands far more reliably than firing off one vague instruction. Refined text can also be saved as a prompt template for next time.

The second way is workflows. You draw fixed steps on a canvas, then pick a phone and parameters at runtime. When you repeat the same job, this is steadier than opening a chat each time. The canvas lets AI help generate or revise steps, and validation catches broken connections or bad parameters before you run.

The third is MCP, which exposes the workstation to external AI assistants. Open the capabilities page, find local MCP, copy the address, usually http://127.0.0.1:9866/mcp, and add it to Cursor or WorkBuddy to look up devices and send tasks from those tools.

One boundary is worth stating clearly. MCP currently exposes mostly query tools: list devices, list groups, list workflows. The actual tapping and swiping still happens inside the workstation. Getting from “chat in my AI assistant” to “phones start moving” still routes through workflows.

One detail matters a lot for multi-device setups. Since version 1.2.0, each device has its own session, so dozens can execute concurrently without fighting over the same context. That used to be a real source of interference, and it is now fixed.


5. The honest cost picture

The software itself is free, ready to use after download, with no premium tier behind a paywall.

Two costs are unavoidable, though.

The first is the EasyClick USB device license. Devices cannot run automation without it, and it is priced per device. This is the only hard requirement in the whole setup.

The second is the language model. iEasyRun does not sell models. You supply the API key and pay your chosen provider. To keep it cheap, turn repeating work into workflows, which costs less than opening a chat each time, and use refinement mode on complex tasks to cut down on trial and error.

Hardware depends on what you already have. You need one PC, and the phones themselves. If you have a couple of spare iPhones, get the flow working on two before buying ten and discovering the approach was wrong.


6. A standard I would apply

Together, these two programs solve one problem: replacing a person staring at a screen and tapping with saying one sentence and checking the result.

They do not solve not knowing what you want. If you cannot say what you need to repeat every day, this will sit unused. Conversely, if you already have one task you repeat daily with fixed steps, the payoff is immediately calculable.

So my usual advice: start with two devices and one task you already do every day. Expand once that runs smoothly, not the other way around.

Install entry points and the docs, when you need them:


About EasyClick: A phone automation AI-agent platform covering Android no-root, iOS no-jailbreak and HarmonyOS Next, offering script development, Apple cluster control, local central control & mirroring, and cloud control systems. → Explore all products

Ready to build it for real?

Every approach in this article can be built on the EasyClick phone automation platform — full documentation, developer tools and cluster/cloud-control products, free to try.

Visit EasyClick →