AdCopilotby Atromx
Connect Google Ads
Product
Connect
Resources
Company
Connect Google Ads — 7-day Pro trial, no cardAlready have an account? Log in

Connect any MCP client to Google Ads

Add one MCP server URL to whichever tool you live in, sign in with Google, and the assistant you already use reads and runs your Google Ads account — build campaigns, move budgets and bids, add negatives, in seconds. Because MCP is a protocol, not a product, that same URL works everywhere. Here is where the setting lives in Copilot, Gemini CLI, Cursor, OpenCode and Claude Code.

Updated 2026-07-29Atromx IntelligenceGoogle Ads · Search, PMax, Display, YouTube, Demand Gen
The short answer

A Google Ads MCP connector is one URL that works in every MCP client. Add https://mcp.adcopilot.cloud/mcp as a remote, streamable-HTTP MCP server in whichever tool you use — Copilot, Gemini CLI, Cursor, OpenCode, Claude Code — then sign in with Google, and it can read and run your Google Ads account under your own Google sign-in, from pulling reports to building campaigns and adjusting budgets and bids, on your instruction.

One URL, every client

The point of a protocol is that the server does not care which client is calling. You paste the same MCP URL wherever you want to work and sign in with Google the first time each client connects. The tools it exposes, the accounts it can reach and the tier it runs on follow your Google sign-in, not the client.

https://mcp.adcopilot.cloud/mcp

Claude and ChatGPT have their own walkthroughs — Claude, ChatGPT. Everything else is below.

GitHub Copilot

Copilot reads MCP servers from an mcp.json, either in your user settings or in .vscode/mcp.json for a single workspace. Either is fine — the URL is public and holds no secret.

{
  "servers": {
    "adcopilot": {
      "type": "http",
      "url": "https://mcp.adcopilot.cloud/mcp"
    }
  }
}

Reload the window, then check the tool picker in Copilot Chat for the connector's tools.

Gemini CLI

Gemini CLI takes its servers from settings.json in its config directory. HTTP servers use the httpUrl key.

{
  "mcpServers": {
    "adcopilot": {
      "httpUrl": "https://mcp.adcopilot.cloud/mcp"
    }
  }
}

Cursor

Cursor keeps MCP servers in ~/.cursor/mcp.json for every project, or .cursor/mcp.json inside one. Either location is fine — the URL holds no secret.

{
  "mcpServers": {
    "adcopilot": {
      "url": "https://mcp.adcopilot.cloud/mcp"
    }
  }
}

OpenCode

OpenCode declares remote servers in its config under mcp, with the type set to remote.

{
  "mcp": {
    "adcopilot": {
      "type": "remote",
      "url": "https://mcp.adcopilot.cloud/mcp",
      "enabled": true
    }
  }
}

Claude Code

One command, no file editing:

claude mcp add --transport http adcopilot https://mcp.adcopilot.cloud/mcp

Add --scope user to make it available in every project rather than the current one.

Which client to use

If you want to…Use
Ask questions in prose and get explanationsClaude or ChatGPT, in the browser or desktop app
Cross-reference ads data with a codebase or analyticsClaude Code, Copilot or Cursor
Script something repeatable in a terminalGemini CLI or Claude Code
Keep everything inside an editor you already live inCopilot, Cursor or OpenCode

There is no wrong answer, and no lock-in: the same address works in all of them at once, so trying a second client costs nothing.

If a client won't connect

  • Check it supports remote HTTP servers. Some clients only launch local stdio processes. Every client on this page supports remote.
  • Check the address ends in /mcp with no trailing slash.
  • Restart or reload after editing a config file. Most clients read MCP config once at startup.
  • Seeing only three tools? That is the read-only tier, not a connection fault. Connectors are on the full tier unless you asked us for read-only.
  • Seeing no accounts? The Google account you signed in with probably does not have access to them.

Frequently asked questions

Does the same connector work in every MCP client?

Yes. MCP is a protocol, so a server written once works in any client that speaks it. The same address goes into Claude, ChatGPT, GitHub Copilot, Gemini CLI, Cursor, OpenCode and Claude Code — only the place you paste it differs.

Do I need a different connector for each person or each client?

One connection per person, and it works in as many clients as you like. Everyone adds the same MCP URL; your Google sign-in is what ties the connection to you, so each teammate signs in with their own Google account and gets their own connection — see the team access model.

What transport does the connector use?

Streamable HTTP. Clients that only support stdio servers — the kind you run as a local process — need a bridge, but every client listed here supports remote HTTP servers directly.

Can I use a coding assistant for advertising work?

Yes, and it is less strange than it sounds: the connector returns structured account data and the tools to change it, and a coding assistant is sharp at querying, cross-referencing and executing precise edits across structured data — the exact shape of pulling a wasted-spend report and then adding the negatives that stop it. It is a poor choice for judgement about copy or offers.

Is the connector URL safe to put in a project config file?

Yes. It is the same public URL for everyone and holds no secret. What authorises access is your Google sign-in (OAuth), handled by your AI client, not anything in the URL — so committing the URL does not hand anyone your Google Ads access. Only your own Google grant does that.

The offer

Try it on your own account for a week

The full set of tools for seven days, so you can see what it actually does — and it still cannot delete anything. No cost, no card: connect your own Google account, and when the week ends it drops to the Free plan automatically rather than locking out.

Connect Google AdsRead the security model
  • 7-day Pro trial
  • Then drops to Free
  • No card
  • Never deletes
Keep reading