MCP and API

Everything you do in the dashboard day to day, you can also hand to Claude or to your own code. Both are included with every plan.

Run your fleet from Claude

AutoGrowth runs a hosted MCP server. Connect Claude, Cursor or any other MCP client to it, approve the connection once in your browser, and you can ask Claude things like:

• "Which of my phones are offline, and which accounts live on them?"
• "Warm up every Instagram account on Rack A for 20 minutes tonight at 9."
• "Why did yesterday's posts fail on phone 12? Show me the screen where it stopped."
• "Upload these five videos to the Summer collection and schedule one Reel a day."
• "How do I set up a DoritoY phone?" (Claude can read these docs too.)

Claude can read your phones and accounts, schedule and stop runs, read why a run failed and see the screenshots, manage your content and workflows, and even look at a phone's screen and tap it. There's nothing to install: it's one URL Claude connects to.

It operates your fleet, but it can't administer it. Billing, your team, licenses and settings stay in the dashboard, for you.

Build on the REST API

The REST API lets your own code do what the dashboard does: list phones and accounts, upload content, schedule runs one at a time or a hundred at a time, follow them and read their logs. Every call uses an API key you create in the dashboard, and every key acts with its owner's permissions.

Use it to plug AutoGrowth into your own scheduling tools, reporting or client dashboards.

Good to know

• Work still happens on your phones. A run scheduled by Claude or by the API waits in the same queue as one scheduled from the dashboard, and the phone carries it out while its Companion is open.
• Same rules as the dashboard. Running an automation needs Phone Control and an automation seat on the phone, whoever schedules it.
• No live video. Claude sees one screenshot at a time. The live screen stays in the dashboard.

Set it up