AutoAdy's connector reads Google Ads: read-only GAQL queries over the selected customer, and Google's own keyword ideas. The write tools are built and switched off until Google's OAuth verification completes, so today nothing here can change a Google campaign.
Last updated: September 24, 2026
AutoAdy connects to Google Ads and the connector serves it. run_gaql takes a Google Ads Query Language statement, accepts only SELECT over an allowlisted set of resources, caps the rows, and runs it against the workspace's selected customer. research_keywords returns Google's keyword ideas with monthly search volume, competition and top-of-page bid range.
The write tools are there too: campaign budget and status, negative keywords, Google's recommendations, and image assets. Each one is built behind a preview, an approval, a journal and, where Google allows it, a 60-second undo. They are all switched off in production until Google's OAuth verification completes. Called today, every one refuses with GOOGLE_WRITES_DISABLED and changes nothing.
In the AutoAdy app the same connection also gives a fixed 30-day report of campaigns, ad groups, keywords and search terms. The table below is generated from the server's tool registry, so it is what your assistant sees.
Tools
8 tools: 2 that read and change nothing, 4 that make a change, and 2 that stop live delivery and are annotated destructive so a well-behaved assistant asks first.
Read-only, against the workspace's selected Google Ads customer. A different customer id is refused. run_gaql: Costs 4 credits per run on the Solo, Growth and Agency credit plans; existing Pro and Agency subscriptions get 100 and 500 runs a day free instead, per workspace, resetting at midnight UTC. Not available on the free plan.
run_gaql
readRun a read-only Google Ads Query Language (GAQL) query against the workspace's selected Google Ads customer and return the rows. USE THIS when the user asks for Google Ads data that the named tools do not cover, or asks for a specific GAQL query by name. Only SELECT is accepted, over exactly one of these resources: ad_group, ad_group_ad, ad_group_criterion, asset, campaign, campaign_budget, conversion_action, customer, keyword_view, recommendation, search_term_view. A row cap is applied for you (max 5000). Costs 4 credits per run on the Solo, Growth and Agency credit plans; existing Pro and Agency subscriptions get 100 and 500 runs a day free instead, per workspace, resetting at midnight UTC. Not available on the free plan. Prefer a named tool when one exists. This tool cannot change anything; use the Google write tools for that.
research_keywords
readGet Google keyword ideas with average monthly search volume, competition and top-of-page bid range, from seed keywords, a landing page URL, or both. USE THIS when the user asks what to bid on, what people search for, or wants to expand an ad group. Volumes are Google's own twelve-month averages for the language and locations given. Read-only.
Built and listed, and disabled in production until Google's OAuth verification completes. Every call refuses with GOOGLE_WRITES_DISABLED and changes nothing.
set_google_campaign_budget
writeChange the daily budget on a Google Ads campaign budget. Shows a preview with the exact API payload and the current amount, requires approval, and is undoable for 60 seconds. A change of 50% or more needs the customer id typed to confirm.
set_google_campaign_status
stops deliveryPause or enable a Google Ads campaign. Shows a preview with the current status, requires approval, and is undoable for 60 seconds. Refused outright when the request comes from a cron, Slack or Telegram: automated pauses require an explicit user preview.
add_google_negative_keywords
writeExclude search terms from a Google Ads campaign or ad group. Up to 500 per call and 2000 per customer per day. Shows every term in the preview, requires approval, and is undoable for 60 seconds. Use EXACT to exclude the one term that wasted money and nothing broader.
apply_google_recommendation
stops deliveryApply one of Google's own recommendations. ALWAYS requires the customer id typed to confirm, because Google decides exactly what changes and there is no undo afterwards. Read them first with run_gaql over the recommendation resource.
dismiss_google_recommendation
writeDismiss one of Google's recommendations so it stops being suggested. Changes nothing in the account itself.
upload_google_image_asset
writeUpload an image from a public URL as a reusable Google Ads image asset. Maximum 5MB, PNG, JPEG or GIF. An uploaded asset cannot be removed from here, and the preview says so.
This table is generated from the server's own tool registry, so it is what your assistant sees. Check it yourself by pointing any MCP client at the endpoint and reading the tools list.
Connect
Opens Claude's add-custom-connector dialog with the name and URL already filled in. Claude still asks you to press Add, then signs you in to AutoAdy with OAuth.
Add AutoAdy to Claude (claude.ai)If you would rather do it by hand: Settings, Connectors, Add custom connector, and paste this.
https://www.autoady.io/api/mcp
Paste into your terminal, then run /mcp to confirm autoady is connected.
claude mcp add --transport http autoady https://www.autoady.io/api/mcp --header "Authorization: Bearer YOUR_KEY"
Replace YOUR_KEY with a key from Settings, API Keys. Keys are shown once and can be revoked at any time.
Open the downloaded file and Claude Desktop installs the extension, including the interactive views.
Download the extensionOr edit claude_desktop_config.json by hand and restart Claude Desktop.
{
"mcpServers": {
"autoady": {
"type": "http",
"url": "https://www.autoady.io/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_KEY"
}
}
}
}Replace YOUR_KEY with a key from Settings, API Keys. Keys are shown once and can be revoked at any time.
Availability depends on your ChatGPT account and workspace policy. ChatGPT's custom MCP connections use OAuth and cannot present your manual API key. See Settings → Agents for current steps and the conditional OpenAI dot path.
Create a custom MCP connection in ChatGPT developer mode, paste this URL and sign in to AutoAdy through OAuth. Choose dynamic client registration (DCR) if prompted.
https://www.autoady.io/api/mcp
Grok web, Grok Build and Grok Bot have different setup flows. These artifacts cover web and Build. Settings → Agents documents the conditional Grok Bot path with official sources; live client sign-in has not been tested here.
On grok.com/connectors, choose New Connector → Custom, paste this URL and complete AutoAdy account sign-in.
https://www.autoady.io/api/mcp
For Grok Build: add the remote server, authenticate when prompted and check grok mcp doctor autoady.
grok mcp add --transport http autoady https://www.autoady.io/api/mcp
This configuration is for Meta's Muse Code. It does not establish custom connector support in the personal Muse app. Settings → Agents explains the distinction and links Meta's exact configuration and OAuth documentation.
Add this hosted endpoint to your Muse Code user settings, then run muse mcp login autoady.
https://www.autoady.io/api/mcp
Merge into ~/.config/muse/settings.json, preserving your settings. Keep one root MCP spelling and start a new Muse Code process after editing.
{
"schema_version": 1,
"mcpServers": {
"autoady": {
"type": "streamable-http",
"url": "https://www.autoady.io/api/mcp"
}
}
}Paste into Cursor's MCP settings, then reload the window.
{
"mcpServers": {
"autoady": {
"type": "http",
"url": "https://www.autoady.io/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_KEY"
}
}
}
}Replace YOUR_KEY with a key from Settings, API Keys. Keys are shown once and can be revoked at any time.
Paste into your MCP servers settings and reload the window.
{
"servers": {
"autoady": {
"type": "http",
"url": "https://www.autoady.io/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_KEY"
}
}
}
}Replace YOUR_KEY with a key from Settings, API Keys. Keys are shown once and can be revoked at any time.
Step by step
Open autoady.io and connect a Meta ad account, then go to Settings and connect Google Ads. Discovery lists the customer accounts your Google login can reach and you pick the one the tools will read. The connector runs every call in the context of a Meta account, so a Google-only workspace cannot use it yet.
On claude.ai, Settings, Connectors, Add custom connector, and paste https://www.autoady.io/api/mcp. Approve access with OAuth. In Claude Code, add the same URL with an API key header.
Say "which Google search terms spent the most last week with no conversions". The assistant writes a read-only GAQL query against your selected customer and answers from the rows it gets back.
If you ask it to pause a Google campaign or move a budget, the tool answers that Google Ads changes are disabled and that nothing was executed. Make the change in Google Ads for now.
What it costs
The alternatives
| Alternative | What it is | Where it beats AutoAdy | Where AutoAdy is the better choice |
|---|---|---|---|
| Google's own Ads MCP tooling and the Google Ads API | Google publishes the Google Ads API, and community and first-party MCP servers wrap it for assistants. | It reaches the whole API rather than a chosen subset, and a server you run with your own developer token can make changes today. If changing Google Ads from the chat is the requirement, this is the answer for now. | The same connector also serves your Meta account, reads are bounded to one selected customer with a row cap, and the write path, once it is on, runs through a preview, an approval and a journal rather than straight at the API. |
| Exporting reports from the Google Ads UI | Download a report and attach it to the chat. | Free, immediate, and no access is granted to anything. For a one-off question it is hard to beat. | The assistant can ask the next question itself with another query instead of waiting for another export, and the answer sits next to the Meta numbers for the same period. |
| Looker Studio on the Google Ads connector | Google's free dashboard tool, wired to Google Ads and usually to GA4. | Genuinely good reporting, shareable, and free. For a client dashboard it is the sensible default. | A dashboard answers what happened. It does not take a question in plain words, and no assistant can query it. |
We sell one of the options in that table, so the column that cost us something to write is the third one. If a row is wrong or out of date, tell us and we will correct it.
Limits worth knowing before you connect anything.
FAQ
Yes. The same endpoint that serves Meta, https://www.autoady.io/api/mcp, lists Google Ads tools: run_gaql and research_keywords for reads, and six write tools that are switched off in production. Point any MCP client at it and read the tools list to confirm.
Read. It can run a read-only GAQL query against the Google Ads customer selected in the app, and pull keyword ideas with search volume, competition and bid ranges. It cannot change anything yet.
Not today. The tool exists, but Google Ads writes are built and switched off until Google's OAuth verification completes. A call returns GOOGLE_WRITES_DISABLED and nothing is executed. Meta ad accounts do have a live write path, on a paid plan and behind a capped, journalled boundary.
Yes, for now. The connector runs every call in the context of a connected Meta ad account, so a workspace with only Google Ads connected gets an account error from the Google Ads tools.
Related
Connect the account, ask your assistant what is wrong with it, and read the evidence behind the answer before anything changes.