Skip to main content
The server URL is:
That is the whole configuration. There is no package to install, no API key to paste and no local process to run.

Before you start

  • An AutoGrowth user that belongs to an organization. A user with no organization can approve the client and still get no working connection.
  • A browser signed in to dash.autogrowth.farm, on the same machine as the client.

Add the server

Then run /mcp inside Claude Code and pick autogrowth to start the sign-in. Your browser opens the consent page.
Whichever client you use, the sign-in is the same:
1

Your browser opens the dashboard

The page is titled Authorize Access and names the client that asked, along with what it is requesting: view your devices, view and schedule scripts, view and schedule automations, view and upload media.
2

Press Allow Access

Deny sends the client away with an error and creates nothing. Approving hands the client a one-time code that is good for 10 minutes, so let the client finish rather than closing it mid-flow.
3

You land back in the client

The tools appear. Nothing else is needed on your side.
Afterwards, a key named MCP: <client name> shows up under Settings → Developer API in the dashboard. That key is the connection — deleting it disconnects the client. See what the connection can see.

Troubleshooting

Tokens last 30 days. Clients normally refresh in the background, but one that was closed for longer, or that lost its stored credentials, has to redo the consent. Remove the server from the client and add it again.
The connection needs a user who is a member of an organization. If you were invited to one and have not accepted, or you were removed, the authorization cannot be completed. Check with your organization’s owner — see Team.
That is scoping, not a fault. Accounts, content, scripts and executions are limited to rows you own, and phones to the ones you can reach. Full rules in What a key can see.