Skip to main content
AutoGrowth runs a hosted MCP server at https://mcp.autogrowth.farm. Point an MCP client at that URL, approve the connection in your dashboard, and the assistant on the other side can read your fleet and schedule work on it. There is nothing to install. It is not an npm package, it does not run on your Mac, and it is not part of the Companion. It is a URL your client connects to.
The MCP server schedules work. It does not perform it. A run an assistant schedules sits in the queue exactly like one scheduled from the dashboard, and the phone only carries it out while the Companion is open.

​
What an assistant can do

Eleven tools in total. MCP tools documents each one’s parameters. Running an automation requires Autogrowth MAX, the same as it does in the dashboard. Listing them does not.

​
What it cannot do

The tool set is narrower than the dashboard and narrower than the REST API. An assistant cannot cancel or delete a run it scheduled, cannot read run logs, cannot manage collections or prompts, and cannot pause an account. It never gets a live screen or control of a phone — those are dashboard-only. MCP limitations is the full list. Read it before you plan around an assistant.

​
How authorization works

You never paste an API key into your client. The connection is authorized in your browser, once.
1

The client registers itself

On first connection your MCP client registers with the server and receives a client ID. Nothing about your account is involved at this point.
2

You approve it in the dashboard

Your browser opens an Authorize Access page on dash.autogrowth.farm naming the client that asked. Press Allow Access and you are sent back to the client.
3

The client gets a token

The token lasts 30 days and the client refreshes it on its own. If it lapses, connect again.
Connect to the MCP server has the per-client setup.

​
What the connection can see

An authorized connection acts as you, with your role and your permissions. Anything you can do to your own accounts, content and phones, the assistant can do — including scheduling runs that post.
Approving a client creates a developer API key owned by your user, named MCP: <client name>. Every tool call goes through that key, so the same scoping rules apply as on the REST API:
  • Your rows only for accounts, content, scripts and executions. Even as the organization’s owner you see what you own, not what your teammates own.
  • Organization-wide for devices and tags, filtered by what you can reach: an owner sees every phone, anyone else sees the phones assigned to them or carrying one of their tags.
  • Global for the automation catalog. It is the same for every organization.
To revoke a connection, open Settings → Developer API in the dashboard and delete the key named after the client. Tool calls stop working immediately. Seeing that list needs the Manage API keys permission.

​
Next

Connect

Setup for Claude Code, Claude, Cursor and everything else.

Tools

All eleven tools, their parameters and their quirks.

Limitations

What the tool set will not do yet.