How to connect Claude to Google Ads with MCP
A step-by-step guide to wiring the Model Context Protocol into Claude Code so you can audit and optimise Google Ads from your terminal.
The Model Context Protocol (MCP) lets AI assistants call external tools. With an ads MCP server, Claude can read your Google Ads data and stage changes without you leaving the terminal.
What you need
- Claude Code installed
- A MyAd account with Google Ads connected
- A MyAd API key
Step 1 — Create an API key
In MyAd, open Settings → API and create a key. Scope it to the accounts you want and choose read-only or read-write. Copy it immediately.
Step 2 — Add the MCP server
Create or edit .mcp.json in your project root:
{
"mcpServers": {
"myad": {
"type": "http",
"url": "https://myad.si/api/v1/mcp",
"headers": { "Authorization": "Bearer YOUR_MYAD_API_KEY" }
}
}
}
For a global setup, add the same block to ~/.claude.json.
Step 3 — Verify
Restart Claude Code and run /mcp. You should see the myad server with a list of tools.
Step 4 — Use it
Try these prompts:
- “List my MyAd accounts and their health scores.”
- “Run an audit on the biggest account and summarise the top five findings.”
- “Find keywords with spend but no conversions in the last 30 days.”
- “Add these as negatives: free, jobs, template.”
Claude calls the relevant tools, reads the results and reports back.
Safety first
Mutating tools are logged and reversible. Start with a read-only key while you build trust, then enable write access for specific accounts. Every action appears in MyAd’s History.
Why this is better than a dashboard
Dashboards are great for looking. Agents are great for doing. MCP turns “log in, click around, export, decide” into a sentence. If you already live in Claude Code, the ads workflow can live there too.
See the integration guide and the MCP setup docs.
Run this on your own account
MyAd audits Google Ads and Meta Ads automatically, ranks findings by projected savings and can apply the fixes with your approval.