Google Ads MCP connector
The Google Ads connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi agent list and create campaigns, ad groups, ads, assets, and audiences, with every action running as the signed-in person and recorded in an audit log.
- Connects over OAuth
- Free 14-day trial
- No credit card
List every live campaign across our Google Ads accounts
Working in Google Ads with Elaichi
-
List all Google Ads customers
-
Get single Google Ads customer by ID
-
Google Ads customers list accessible customers
How to connect Google Ads to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Google Ads MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Google Ads MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Google Ads MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Google Ads MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Google Ads MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Google Ads to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Google Ads through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Google Ads is logged.
-
Paid media
Build a campaign without opening the console
Describe the campaign, the ad groups under it, and the first ads, and the agent creates them in Google Ads in the right order. You review the result instead of clicking through five setup screens.
-
Marketing
See what is live across every account
Ask which campaigns are running across all the Google Ads accounts you manage and get one list back. No switching between customer accounts to piece it together.
-
Finance
Review campaign budgets before month end
Pull every campaign budget in Google Ads into one view and check it against what was approved. The agent can read budgets but cannot change them through this connector.
-
Creative
Add new assets and see what exists
Upload the new headline, image, or video asset to Google Ads and ask what assets are already in the account so nothing gets duplicated.
-
Growth
Keep custom audiences current
Create a custom audience for a new segment, or update an existing one when the targeting changes, and list every audience to see what is available for the next campaign.
-
Account management
Set up a new client account
Create the Google Ads customer for a new client, then list the users on the account to confirm the right people have access before work starts.
Try asking
- “List every live campaign across our Google Ads accounts”
- “Create an ad group for the spring sale campaign”
- “Show me the budget for the brand search campaign”
What connecting Google Ads gets you
6 screens from Elaichi, each doing one job for your Google Ads account.
Ask Elaichi to work across your apps.
List every live campaign across our Google Ads accounts
Create an ad group for the spring sale campaign
Show me the budget for the brand search campaign
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask Google Ads questions in plain language.
Three starter prompts pull live campaigns, ad groups, and budgets straight from Google Ads.
Copy the endpoint
AI apps
One endpoint brings Google Ads to every client.
Claude, ChatGPT, Cursor, Microsoft Copilot, and Microsoft Copilot connect over OAuth, with no SDK and no shared API key.
Tool catalog
198 Google Ads tools, no custom code needed.
Campaigns, ad groups, ads, budgets, assets, and audiences, each listed with its resource and method.
Toolboxes
Every team gets its own Google Ads toolbox.
Paid media builds campaigns while Finance only sees budgets, each from a toolbox scoped to them.
Shared connections
Share Google Ads access without sharing a credential.
One person connects the account, teams work through it, and nobody else sees a secret.
Audit log
Every Google Ads action names who did it.
When, who, what happened, type, and resource, logged for every campaign and audience change.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Google Ads digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch campaigns
Google Ads
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Google Ads
Queued
Workflows
Google Ads digests run themselves, you approve.
A schedule fetches campaigns, groups them, drafts a digest, waits for approval, then posts back.
Google Ads health
Refreshed 4 minutes ago · every 15 minutes · from the campaigns collection
Campaigns
1,284 ↓ 12%
Ad groups
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Campaigns created
Last 14 days
By team
Share of activity
Paid Media 34%
Brand 27%
Performance 21%
Agency Clients 18%
Collections and dashboards
Google Ads health, computed with no model.
Four metrics, 14 days of campaigns created, and a breakdown by team, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Google Ads
All three can connect Google Ads to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Google Ads tools | Allow or restrict single Google Ads tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Google Ads call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Google Ads tools for your AI agents
198 tools are ready to call through Elaichi's MCP endpoint the moment you connect Google Ads, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Google Ads to Claude?
Connect Google Ads in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Google Ads needs an OAuth application registered inside your own Google Ads account, so one person brings that client ID and secret to Elaichi once, after which everyone signs in with their normal Google account. Nobody else on the team ever handles the secret.
Does Google Ads work with ChatGPT and Cursor as well as Claude?
Yes. The Google Ads connection in Elaichi is reached through the same endpoint, https://api.elaichi.ai/mcp, from Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi agent. You connect Google Ads once and every client can use it.
What can an AI agent actually do with my Google Ads data?
With Google Ads connected, an agent can list your customer accounts, campaigns, ad groups, ads, budgets, assets, bidding strategies, users, and audiences, and it can create new campaigns, ad groups, ads, assets, and custom audiences. It can also update a custom audience. Short, concrete asks like "list the campaigns in the brand account" work better than long paragraphs.
Does connecting Google Ads give the AI access to every account I manage?
The agent sees exactly the Google Ads accounts the signed-in person can see, and nothing more. Elaichi can narrow that further by restricting which actions a team's toolbox includes, but it can never widen it beyond what Google Ads already allows that person.
Can I stop an agent from changing things in Google Ads?
Yes. Restrictions in Elaichi work per action, so you can allow listing Google Ads campaigns and budgets while restricting anything that creates or updates them. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
What happens to a Google Ads connection when someone leaves?
Offboarding a person in Elaichi ends their access to Google Ads through every client at once. If they connected a shared Google Ads account, it keeps working for everyone else on the team. Disconnecting Google Ads once in Elaichi removes it from every client at the same time.
Does the Google Ads MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Google Ads is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Google Ads?
Yes. Both let Claude, ChatGPT or Cursor use Google Ads. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Google Ads call.
How is Elaichi different from Composio for Google Ads?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Google Ads: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Google Ads in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot