Connect any MCP client to Google Ads

One address, every client

The point of a protocol is that the server does not care who is calling. You sign in with Google once, get one private address, and paste it wherever you want to work. The tools it exposes, the accounts it can reach and the tier it runs on are all properties of the address, not of the client.

https://mcp.adcopilot.cloud/c/<your key>/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. Prefer user settings here, so the address does not end up in a repository.

{
  "servers": {
    "adcopilot": {
      "type": "http",
      "url": "https://mcp.adcopilot.cloud/c/<your key>/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/c/<your key>/mcp"
    }
  }
}

Cursor

Cursor keeps MCP servers in ~/.cursor/mcp.json for every project, or .cursor/mcp.json inside one. Same caution about committing the file.

{
  "mcpServers": {
    "adcopilot": {
      "url": "https://mcp.adcopilot.cloud/c/<your key>/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/c/<your key>/mcp",
      "enabled": true
    }
  }
}

Claude Code

One command, no file editing:

claude mcp add --transport http adcopilot https://mcp.adcopilot.cloud/c/<your key>/mcp

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

Which client to use

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, and that the key is complete.
• 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 and it is the pilot default, not a connection fault.
• Seeing no accounts? The Google login behind the address probably does not have access to them.

Frequently asked questions