Any MCP client
Connect any MCP client to Google Ads
One endpoint over HTTP, added by URL or by one command, under the same Google sign-in every other on-ramp uses.
- One HTTP endpoint
- Your own Google sign-in
- It cannot delete
Setup
The URL, and nothing else
If your client can add a server by URL, it can add this one. The config shape is below.
Connect your Google Ads account
Sign up, then sign in with Google itself. You grant access to the accounts you can already open in the Google Ads interface, and nothing widens that.
Add the server to your client
Give your client the URL, or write it into the configuration file the client reads. The transport is HTTP and the sign-in happens in a browser window the first time.
New to the word? Read what an MCP server is, and how its tool list tells you what it can do.
JSON configuration { "mcpServers": { "adcopilot": { "url": "https://mcp.adcopilot.cloud/mcp" } } }Where that file lives is your client's own business — check its documentation for the path.
Ask your first question
Start a conversation and ask about the account. Answers are read live, every call is written down, and it cannot delete.
Command line and Cursor
Four clients, one command or one link
The command-line clients add the server with one command, and Cursor with one link. Claude Code has a plugin that adds it for you.
Claude Code
Install the AdCopilot plugin, or add the connector to Claude Code with one command.
Claude Code plugin /plugin marketplace add AtromxIntelligence/adcopilot-claude-plugin /plugin install adcopilot@adcopilot-claude-pluginTyped in Claude Code. The plugin adds the connector for you; then run /mcp, choose adcopilot and sign in.
Claude Code, by hand claude mcp add --scope user --transport http adcopilot https://mcp.adcopilot.cloud/mcp--scope user makes it show in every folder; without it, only in the folder you ran the command from.
Codex
Add the connector to Codex with one command.
Codex codex mcp add adcopilot --url https://mcp.adcopilot.cloud/mcpGemini CLI
Add the connector to Gemini CLI from the command line.
Gemini CLI gemini mcp add --scope user --transport http adcopilot https://mcp.adcopilot.cloud/mcpCursor
Add the connector to Cursor with Add to Cursor, or in its mcp.json, then sign in with Google and approve.
Add to Cursor opens Cursor with the connector filled in, named adcopilot. Or add it by hand:
Cursor's mcp.json { "mcpServers": { "adcopilot": { "url": "https://mcp.adcopilot.cloud/mcp" } } }In ~/.cursor/mcp.json for every project, or .cursor/mcp.json in one.
The on-ramps
Eight ways in, one URL
Whichever client you add it to, the endpoint is the same and what it can reach is the same.
Claude
ChatGPTworks today as an app you add yourself in developer mode; a directory listing is planned
Microsoft Copilot
Claude Code
CodexGemini CLI
Cursor
- Any MCP client
https://mcp.adcopilot.cloud/mcpWhat arrives
The same tool list
Your client is handed one list, the same whichever products you have connected; connecting one is what lets its tools run.
- One list, whatever the client
- The connector hands every client the same set, so a question answered in one of them is answered the same way in the next.126 tools on the full tier, whichever products are connected, as of v2.45.2
- Read-only is a tier, not a prompt
- Ask for the read-only tier and every write capability is gone from the list your client receives, on the server rather than in an instruction it could be talked out of.
- It can be pinned to named accounts
- An allow-list of Google Ads customer IDs, checked on our server before the call leaves it. A call to an account outside the list is refused and the refusal names the account.
Questions
Five things people ask
Which transport, whether a local install is needed, how the sign-in works, which clients work, and what it cannot do.
HTTP. Nothing runs on your machine — the endpoint above is the whole of it, and a client that speaks the Model Context Protocol over HTTP can use it.
No. The server is hosted, and your client talks to it over the network. That is also why the sign-in is a browser window rather than a key you paste into a file.
Your client opens a browser window the first time it calls the server. You sign in with Google itself, Google returns a token for the access you granted, and we never receive a password.
Yes — all three add a server by URL or by command, and the endpoint above is the whole of it. Claude Code takes the plugin or the one-line command on this page, Gemini CLI its command, Cursor its install link or the configuration block. The sign-in is the same browser window, and the tool list is the same one.
It cannot delete a campaign, ad group, ad, keyword or asset: those removal tools are never registered for a hosted connector, and a change carrying the status REMOVED is refused on our server before Google is called. The refusal is written down too. The one removal it serves takes a negative keyword back out.
Ask
Client not behaving?
Tell us which client and what it printed, and we will tell you what it wants.