Manage Google Ads from Claude Code

One command in your terminal puts your Google Ads account next to your code. That command holds one server URL, you sign in with your Google account, and from then on Claude Code can read and change your campaigns without you opening the Google Ads interface. It's especially strong when you want the answer to end up somewhere: an export, a script, or a change to the landing page you're already working on.

Where you set it up
In your terminal, with claude mcp add
Transport
HTTP, with OAuth through your browser
Signing in
/mcp in a session, or claude mcp login adlyko
Default scope
The project folder where you run the command

Add Adlyko in four steps

  1. 1

    Sign up for Adlyko

    Sign in with the Google account you use to manage your Google Ads. You don't need to set a key or environment variable in your terminal.

  2. 2

    Add the server

    Run this command in the folder of the project where you want to use Adlyko. Claude Code saves the server and confirms it with a line that starts with Added.

    claude mcp add --transport http adlyko https://mcp.adlyko.com/mcp
  3. 3

    Sign in with Google

    Start Claude Code, type /mcp and choose Authenticate next to adlyko. A browser opens where you pick the same Google account you signed up with. In recent versions you can also do this straight from your shell with claude mcp login adlyko.

  4. 4

    Check that the connection works

    Run claude mcp list. Next to adlyko it should say Connected. If it says authentication is needed, the browser step wasn't finished; if it says Failed to connect, Claude Code puts the server's error message after it.

Choose where the connection applies

This is the difference people overlook most often with Claude Code. Without an extra option, the server only applies in the folder where you added it. Start Claude Code in another folder and Adlyko isn't there, so the connection seems to have disappeared. Want it everywhere? Then add it at user level:

claude mcp add --transport http adlyko --scope user https://mcp.adlyko.com/mcp

If you work with a team in the same repository, the project scope can actually be handy. It writes the server to a file in the project, so a colleague has it as soon as they pull the repository. Everyone then signs in with their own Google account, and everyone only sees the accounts Google gives them rights to.

Your first task

In a chat window you ask a question. In a terminal you usually ask for something that's there afterwards. That's exactly where this connection stands out.

Pull the search terms for the last thirty days from my Google Ads, filter on search terms with cost and zero conversions, and write them to wasted-spend.csv in this folder.
Read the headings of the landing page in this repository and compare them with the search terms that do convert. Suggest three ad texts that match them.

What to know about Claude Code

If it doesn't work

I get a message that adlyko already exists in local config
You already added the server in this folder. Run claude mcp list to see what's there, or claude mcp remove adlyko to remove it and start again. Running the same command twice with the same name in the same scope always gives this error.
The browser doesn't open when signing in
Claude Code then shows the authorization URL. Open it yourself and sign in. If you work over SSH or on a machine without a screen, use claude mcp login adlyko with the no-browser option and paste the full address bar from your browser back at the prompt that appears.
Does this work in a script or in claude -p too?
The sign-in itself doesn't: outside an interactive session Claude Code can't open the login screen. Sign in once with claude mcp login adlyko, and a later run simply uses the stored sign-in.
Claude Code says my account isn't recognized
Then the browser is signed in to a different Google account than the one you signed up to Adlyko with. Run claude mcp logout adlyko, then claude mcp login adlyko, and this time explicitly choose the right account on Google's selection screen.

You need an account first

The command above only works once you've signed up, because the server ties your Google account to your access. Signing up costs nothing and you connect your first Google Ads account right away. The rates are on the pricing page.

Start free →Get the free audit →

Same URL, a different agent

The server URL doesn't change when you switch agents. Only the place where you enter it is different. What connecting involves is explained on the overview page about connecting Adlyko.

Not sure yet whether this is what you're looking for? First read what a Google Ads MCP server is and how Adlyko compares to Google's own server.