MCP

Connect your AI agents to OpenControl

OpenControl ships a Model Context Protocol (MCP) server, so agents like Claude Code can list, run, and monitor your iPhone automations directly. The OpenControl window does not need to be open: the background service and a phone plugged in with WDA ready are all it takes.

What your agent can do

connect The way in. If the agent has no access key yet, every other tool tells it to ask you for your key and call this. It verifies your plan, stores the key, and unlocks the rest. Once the installer has run, the key is already stored and this is not needed.
list_automations See every saved automation with its group, step count, and how it chains into the next one. Supports filtering by group, e.g. only your aug23 automations.
run_automation Start an automation by name. If it is part of a chain, the whole chain runs on the connected iPhone in the background.
automation_status Live progress: which automation in the chain is running, step N of M, what it is doing right now, and recent log lines.
stop_automation Halt the running automation and the rest of its chain.
phone_status Which iPhones are attached and which one is active for automation.

Install

One command in your Mac terminal does everything:

curl -fsSL https://opencontrol.cloud/install.sh | bash

It asks for your access key, verifies your plan, then installs the OpenControl skill and MCP server and registers them with Claude Code. When it finishes, start a new agent session and the tools are there. That is the whole setup.

Using opencode

OpenControl runs as a local MCP server on your Mac. It is not a website you connect to: the server is a small program that talks to the OpenControl app on your machine and drives the iPhone plugged into it. So in opencode you add it as a local server, not a remote URL.

Add this to ~/.config/opencode/opencode.jsonc:

{
  "mcp": {
    "opencontrol": {
      "type": "local",
      "command": ["/usr/bin/python3", "/Users/YOUR_USERNAME/.opencontrol-mcp/server.py"],
      "enabled": true
    }
  }
}

Replace YOUR_USERNAME with your Mac username, then start a fresh opencode session. Your key is already stored on this Mac by the installer, so there is no token or URL to add. Common mistake: pointing it at https://opencontrol.cloud/mcp as a remote server. That address is this docs page, not an MCP endpoint, and it will connect to nothing.

Requirements

OpenControl installed and activated Sign in to the app once with your access key so the local backend is set up.
Background service running The OpenControl backend runs on 127.0.0.1:5001 even when the app window is closed. Everything stays on your Mac; nothing is sent to the cloud.
iPhone connected Phone plugged in over USB with WDA running, exactly like a normal OpenControl session. See the in-app Setup Docs for WDA signing.

Where to get your key

Your access key is issued with your OpenControl purchase (Lifetime or Lifetime+) and is the same key you use to sign in. Inside the OpenControl app, open Account Settings to view and manage your keys. Lost it? Ask in our Discord and we will sort you out.

Keep your access key private. The MCP server itself runs locally and never needs the key sent to any agent or third party; the key only activates the OpenControl app.

What to say to your agent

Once connected, plain English does everything. Copy any of these straight into your agent:

"What automation groups do I have in OpenControl?"

"List all my automations and how they chain together"

"List the automations in my aug23 group"

"Create 5 gmail accounts verify them by phone number ping me when its done"

"Run my chrome container automation and watch it until it finishes"

"What automation is running right now and what step is it on?"

"Stop the current automation"

"Is my phone connected and ready?"

Questions? Join the Discord and ask; we are happy to help you wire up your agents.