Zum Inhalt springen

Anleitung

Connect Helferlain to Claude

Add Helferlain as a custom connector in Claude.ai or Claude Desktop, authorize your workspace and ask Claude about your Google Ads account.

Diese Anleitung gibt es derzeit nur auf Englisch. Die Kurzfassung auf Deutsch steht im Hilfe-Artikel Helferlain in Claude, ChatGPT oder Cursor nutzen.

Helferlain MCP server URL

https://mcp.helferlain.app/mcp

Prerequisites

  • A Claude plan that allows custom connectors. Depending on the plan, the number of custom connectors is limited.
  • A Helferlain workspace with at least one ad account connected at app.helferlain.app/connectors.

Setup steps

  1. Open Claude, then Settings, then Connectors

    In Claude.ai click your avatar, then Settings and Connectors. In Claude Desktop the path is identical. Click Add custom connector.

  2. Paste the Helferlain MCP URL

    Paste the URL above into the connector field. Claude discovers the server name and the sign-in method on its own.

  3. Authorize on the Helferlain page

    Your browser opens app.helferlain.app/oauth/authorize. Sign in to Helferlain if needed, pick the workspace Claude may access, review the permissions and click Approve. You are redirected back to Claude.

  4. Test it from Claude

    Back in Claude, ask for example:

    “Run a wasted-spend audit on my Google Ads account and show me the top 5 recommendations.”

    Claude calls the Helferlain tools and returns structured findings. Changes go through one tool, google_ads_mutate_with_approval: without further arguments it only runs a dry run (validateOnly) and changes nothing. A real change needs an approval token that is bound to exactly these operations, is time-limited and works once. The app does not show approval tokens for assistants today, so real changes run in the Helferlain app. Hard limits apply on every path (see Troubleshooting).

    To plan a new campaign, try:

    “Plan a Search campaign for Nuremberg with a 20 € daily budget. Look up the location IDs first and check whether an active campaign already targets these areas.”
  5. Claude Code (terminal)

    In a terminal, run:

    claude mcp add --transport http helferlain https://mcp.helferlain.app/mcp

    The first call opens the sign-in in your browser.

Troubleshooting

“Connector failed to authenticate” after approval

Your token may have expired. In Claude, remove the connector and add it again. If the issue persists, check that your workspace has at least one connected ad account at app.helferlain.app/connectors.

Quota exceeded for current period

Each plan has a monthly limit of tool calls: Starter 200, Professional 1,000, Agency 5,000. Wait until the next calendar month or change your plan; the limits per plan are on the pricing page.

Tool returns “r2_approval_required”

High-risk changes (R2) only run with an approval token for exactly these operations (approvalToken). Without one, run the call as a dry run (validateOnly: true, the default) or apply the change in the Helferlain app. Protected accounts reject every change, dry runs included.

Tool returns “cpc_cap_exceeded”, “budget_cap_exceeded” or “mutation_shape_forbidden”

The change hit a hard limit that applies on every path: new campaigns, ad groups and ads must be created with status PAUSED (enable them later with separate status changes); every click, impression and view bid is capped at 10 €; only manual CPC, Maximize Clicks and Percent CPC with a bid ceiling above 0 and at most 10 € are accepted (Target CPA, Target ROAS, Maximize Conversions and other strategies without a ceiling are rejected); URLs must stay on the website in the account profile; a campaign can only use a budget created in the same request; every bidModifier is at most 1.5; budgets are capped (50 € per day unless the operator set another cap) and new budgets must not be shared; keys must be lowerCamelCase; partialFailure must be false (omitted counts as false).

Noch kein Helferlain-Zugang?

Helferlain ist in der geschlossenen Beta. Frag deinen Zugang über das Kontaktformular an.