MCP server

The Growth Method MCP server lets you run the plan, launch, analyse workflow for your campaigns from the AI client you already use, such as ChatGPT, Claude or Copilot. Your client reads and updates your campaigns directly, so you don’t switch into the Growth Method app to keep them current.

Growth Method acts as a headless backend here: it provides the data and actions, and your AI client does the work.

Who it’s for

Teams that use our MCP server tend to:

• Spend a lot of time in AI tools like ChatGPT, Claude and Copilot
• Have a relatively modern marketing stack and are comfortable connecting data sources via MCP

What you can do

Once connected, you can chat with your campaigns and with any integration connected to your Growth Method workspace, from analytics and ad platforms to email tools and your CRM. Your client uses your workspace’s existing connections, so you don’t hand it a separate key for each provider. Reads run straight away, and anything that could change something waits for your approval. Integration questions need integration access switched on.

For example:

• “What happened in Growth Method last week, and what’s waiting on me?”
• “How did ‘get started’ conversions last month compare to the month before? Come up with a new campaign idea to boost our conversion rate further and add it to our backlog.”
• “Check our GA4 data from last week and tell me if there were any anomalies I should be aware of.”
• “Which ad campaigns are currently running, and how are they performing?”
• “How many people completed our email onboarding sequence last week? Which email in the sequence performed best, and why?”

Connect your AI client

Every client connects to the same URL:

https://app.growthmethod.com/mcp

Most clients sign in through OAuth, so there is no token to create or manage. Follow the steps for your client below.

Growth Method is also listed in the official MCP Registry as com.growthmethod/growth-method, so clients and directories that read the registry can find it by name.

Claude on the web, desktop or mobile

1. In Claude, go to Settings, then Connectors, and select Add custom connector.
2. Name it Growth Method and enter the URL above. Leave the client ID and secret fields empty.
3. Select Connect.
4. Growth Method opens and asks you to approve the connection. Sign in if you aren’t already, then select Authorize.

If you previously connected Claude Desktop through the mcp-remote bridge, remove that entry from your claude_desktop_config.json. The custom connector replaces it.

Claude Code

1. Run this in your terminal:

   claude mcp add --transport http growth-method https://app.growthmethod.com/mcp --scope user

2. Type /mcp inside Claude Code, select growth-method, and choose Authenticate.

3. Your browser opens and Growth Method asks you to approve the connection. Select Authorize.

Once it’s connected, /mcp lists the Growth Method tools.

--scope user makes Growth Method available in every project you work on. This is what most people want, because your campaigns aren’t tied to one codebase. Leave it out and the connection is saved to the current project only.

ChatGPT

1. In ChatGPT, go to Settings, then Apps & Connectors.
2. Under Advanced settings, switch on Developer mode.
3. Select Create, name it Growth Method, and enter the URL above.
4. Choose OAuth for authentication, then select Create.
5. Growth Method opens and asks you to approve the connection. Sign in if you aren’t already, then select Authorize.

Cursor

1. Add Growth Method to your mcp.json file, in ~/.cursor/ for every project or in a project’s .cursor/ folder for that project only:

   {
     "mcpServers": {
       "growth-method": {
         "url": "https://app.growthmethod.com/mcp"
       }
     }
   }

2. Open Cursor’s MCP settings, where Growth Method shows as needing sign-in, and select it.

3. Approve the connection in Growth Method and select Authorize.

VS Code and Copilot

1. Open the Command Palette and run MCP: Add Server.
2. Choose HTTP, enter the URL above, and name it growth-method.
3. When VS Code asks to sign in, allow it.
4. Growth Method opens and asks you to approve the connection. Select Authorize.

Once connected, the Growth Method tools appear in Copilot Chat’s agent mode.

Another client

Any client that supports MCP over the Streamable HTTP transport can connect. Clients that support OAuth can add the URL above and sign in, the same way Claude does. Clients that only take an API key should send an API token in an Authorization: Bearer header.

Create an API token

Tokens are for connections that can’t sign in through a browser: scripts, automations, or clients that only take an API key.

1. In Growth Method, switch to the workspace you want your AI client to work with.
2. Go to User settings and select the API Tokens tab.
3. Enter a name, then select Create Token.
4. Copy the token. For your security it’s shown only once.

Note: each token works with one workspace only, the one you were in when you created it. Switching workspaces in the app later doesn’t move it. To work with more than one workspace, create a token for each; the API Tokens tab shows which workspace each token can access. A token expires one year after you create it, and stops working if you leave its workspace.

Available tools

Tools that change your data ask you to confirm before they act: every create, update, extend, archive, prioritise, comment, edit, delete and save tool above.

Some rules protect your team’s work:

• Edits don’t overwrite a teammate’s. update-campaign can check that the campaign hasn’t changed since your client last read it. If a teammate edited it in the meantime, the change is refused, so your client reads the latest version and tries again.
• Campaigns move one stage at a time. update-campaign moves a campaign forward one stage at a time, the same as the stage button on its page, so a Backlog campaign goes to Planning before Live. Moving back to any earlier stage still works.
• Archived campaigns are read-only for comments. You can’t comment on them or change their comments.
• Workspace questions have an hourly limit. query-workspace answers up to 100 queries an hour per workspace.

Use your connected integrations

Your AI client can use the integrations your workspace has already connected, such as Google Search Console, Google Analytics or PostHog. It uses your workspace’s existing connection, so there is nothing extra to set up in the client and no second sign-in with each provider.

This is off until a workspace manager switches it on:

1. In Growth Method, go to Settings, then Integrations.
2. Below the list, switch on Let AI apps use these integrations through MCP.
3. If your client was connected before this was switched on, reconnect it once so it picks up the new tools.

Then ask in plain language, for example “Get last week’s top five queries from Search Console.” Your client first asks Growth Method which tools the integration offers, then runs the one it needs.

A few limits keep this safe:

• Changes wait for you. Reads run straight away. Anything that could change something follows the same rules as Growth Method’s own chat (see How approvals work): if it needs approval, your client shows you a Growth Method link instead of running it. Open the link, check what it will do, and select Approve or Reject. Only you can open your own link, and it expires after 24 hours. Then tell your client, and it picks up the result. In AI apps that can show interactive cards, the same approval card appears right in the chat instead, and your client carries on as soon as you choose.
• Approved changes show on the campaign. When the work is for a campaign, an approved change appears in that campaign’s Live section, the same as a change made from Growth Method’s own chat.
• Your choices still apply. Tools you have switched off for an integration stay off, and an integration connected to one site or property can only be asked about that one.
• There is an hourly limit. Each integration answers up to 500 requests an hour per workspace, so a runaway client can’t use up your allowance with the provider.
• Very large results are trimmed. Your client is told when this happens, so it can ask for a narrower date range or fewer rows.

The AI doing the work is your own client, so its usage counts against your plan with Claude or ChatGPT, not against Growth Method.

Use skills and prompts

Each of your team’s skills is also offered as a prompt, so clients that support prompts show it as a ready-made command. In Claude Code, type / and pick the entry named after the server and the skill, for example /mcp__growth-method__copy-editing. ChatGPT doesn’t show prompts, so ask for the skill by name there and it loads it with load-skill.

The server also offers built-in prompts. Five of them take a campaign through its stages with the same steps as the matching command in chat. Give them a campaign’s id, or leave it out and your client asks which one:

• create-campaign shapes a new campaign from your data or an idea you already have. Give it a finished campaign’s id to start its next version.
• plan-campaign writes the campaign’s plan and saves it once you agree.
• launch-campaign checks the campaign is ready, records its starting numbers, works through the plan with your connected integrations, and moves it to Live.
• analyse-campaign checks whether the result can be trusted, gives a verdict and a next step, and saves the result.
• prioritise-campaign explains a Backlog campaign’s priority score and re-runs it when the campaign or your goal has changed.

The launch and analysis steps that read or change your integrations need integration access switched on. Without it, your client treats those steps as ones you do yourself.

Two more built-in prompts help you stay on top of your workspace:

• catch-up summarises what changed in your workspace over a period you choose, the last 7 days unless you say otherwise. It works the same way as /catch-up in chat.
• sync-skills compares the skills kept in your client with the team’s, and saves any that are new or changed after you confirm each one. See Reuse instructions with skills.

Permissions and limits

Connections and tokens act on your behalf as a signed-in user, so the tools see exactly the campaigns you’d see in the app.

• Workspace: an OAuth connection acts on whichever workspace you have selected in Growth Method, and moves with you when you switch. A token stays with the workspace it was created in. Each answer about your campaigns or integrations names the workspace it came from, so your client can tell you which one it used.
• Rate limit: requests are limited to 30 a minute.
• Disconnecting: go to User settings, open the API Tokens tab, and use the Connected Apps list to disconnect any client.
• Expired tokens: when a token expires after a year, create a new one and update your client.

Next steps

• MCP client: add analytics results to campaigns from inside Growth Method.
• MCP overview: how Growth Method thinks about MCP.
• Integrations: connect the data sources your AI client can read from.