Connect chiliad to Claude — on the web, desktop, mobile, or Claude Code — and run your whole script workflow in a conversation. Create, configure, debug, and deploy without leaving the chat. Sign in with your chiliad account; no API keys.
Your connector URL
https://app.chiliad.io/api/mcpPaste this into Claude's Add custom connector field. Find it anytime in chiliad under Settings → Claude.
Add the connector once. It stays linked until you disconnect it.
Run this, then use /mcp to authenticate:
claude mcp add --transport http chiliad https://app.chiliad.io/api/mcpEverything happens in your chiliad workspace — with hosted loaders, execution analytics, and version history behind it.
Describe what you need in plain language. Claude writes the script, validates it against chiliad's loader contract, and saves it to your workspace — versioned and ready to deploy.
Set per-account variables — caps, thresholds, labels — across all your client accounts from one chat. Claude assigns the script and writes each account's config.
Claude reads your actual execution history and error messages, pinpoints why a script failed, and ships the fix — no copy-pasting between tabs.
Claude runs read-only GAQL queries to pull real campaign IDs, budgets, and labels, so the scripts it configures match what's actually in the account.
Ask Claude to find and install ready-made automations — budget pacing, negative keyword mining, placement cleanup — straight into your workspace.
List, archive, and restore scripts. Archiving keeps a still-installed script running in Google Ads while hiding it from your active library.
Say it in plain language. Here's what Claude does with it once connected.
“Write a budget pacing script that pauses campaigns once they hit 90% of the monthly budget, and push it to chiliad.”
Claude writes and validates the script, saves it to your workspace, and hands back the one-line loader plus the Google Ads setup steps.
“Assign the Budget Pacing Monitor to all my e-commerce accounts and set the monthly cap to €5,000 for each.”
Claude assigns the script to each account and writes the MONTHLY_CAP variable per account — no spreadsheet, no per-account clicking.
“The ROAS Bid Adjuster failed on GrowthLab Store last night — what happened and can you fix it?”
Claude reads the execution log and error message, identifies the cause, edits the hosted script, and the fix goes live on the next run.
“Which campaigns in ClickSmart SaaS spent over €1,000 last week with a ROAS below 2?”
Claude runs a read-only GAQL query against that account and returns the campaigns — so you can configure thresholds against real numbers.
“Find a negative keyword mining script in the marketplace and install it.”
Claude searches the marketplace, installs the script to your workspace, and (on a paid plan) returns the loader to deploy it.
“Show me every script that's failed in the last 7 days and how many times.”
Claude pulls execution analytics across your workspace and summarizes the failing scripts, their error counts, and health.
The AI assistant runs under its own terms. See how we handle this in our Privacy Policy (Section 7) and Terms of Service (Section 6).