Run Google Ads from n8n
In n8n you connect Adlyko with the MCP Client node, which you hang under an AI Agent. You put one endpoint URL in the node, authenticate with your Google account and choose which tools the agent may use. From then on a workflow can read and change your Google Ads at the moment you decide, and that's the difference with a chat window: nobody has to be at their screen when it happens.
- Which node
- The MCP Client node, on the tool input of an AI Agent
- Transport
- The HTTP variant, not the older transport with server-sent events
- Authentication
- OAuth2, stored as a credential in n8n
- What else you need
- A trigger and a language model under the same agent
Add Adlyko in five steps
- 1
Sign up for Adlyko
Sign in with the Google account you use to manage your Google Ads. That account decides which Google Ads accounts your workflow can see.
- 2
Build a workflow with an AI Agent
The MCP node isn't a step on its own but a toolbox under an agent. So you need at least three things: a trigger, an AI Agent node and a language model under it.
- 3
Hang the MCP Client node under the agent
Add the MCP Client node to your AI Agent's tool input. Set Server Transport to the HTTP variant and put this URL in the MCP endpoint field.
https://mcp.adlyko.com/mcp - 4
Create the OAuth credential
Choose OAuth2 as the authentication and go through the sign-in with the same Google account you signed up with. n8n stores that sign-in as a credential, so you can reuse it in several workflows.
- 5
Limit the toolset
Set Tools to Include to Selected and pick only what this workflow needs. An agent offered dozens of tools at once chooses noticeably worse than an agent with five tools for one task.
A workflow that pays for itself
The setup that makes sense most often is short: a trigger that fires at a set time, an agent with a limited set of Adlyko tools, and a last step that puts the answer somewhere you already look. The instruction to the agent is then not a question but a task.
Pull last week's campaign performance. Name every campaign where the cost per conversion is more than a quarter higher than the week before, with the amount. If there are none, reply with: nothing unusual.
Compare the products in stock from the previous step with the active shopping groups in Google Ads, and report which sold-out products are still getting ad budget.
That second one is where n8n really adds something. The first one you can also switch on as a routine in Adlyko itself, which saves you maintaining a workflow.
What to know about n8n
- The node only works as a tool under an agent. There's no screen where you type a question yourself, so you steer through the agent's system instruction.
- The credential is tied to one Google account. If you manage clients from different companies, create a separate credential per account instead of switching within an existing one.
- A workflow that changes something in your account runs without anyone watching. So build in an approval step, or keep this agent's tools to the ones that only read. New campaigns come in paused regardless.
- Just want to ask questions yourself without a workflow around it? Then Connect Google Ads to Claude is quicker to set up. For work you combine with code, Manage Google Ads from Claude Code is the shortest route.
If it doesn't work
- The node doesn't fetch any tools
- Almost always the sign-in wasn't finished. n8n only requests the tool list once the credential works, so an empty dropdown usually means the OAuth step was interrupted. Open the credential again, sign in and save it; then the list fills up.
- Which transport should I choose?
- The HTTP variant. Adlyko runs on a regular HTTPS address that uses the modern MCP transport. The older transport with server-sent events is in n8n for existing connections, but it's not what you build a new connection on.
- My agent picks the wrong tool
- Limit the list with Tools to Include and put in your agent's system instruction what the workflow should and shouldn't do. One workflow per task works better than one agent that can do everything, because an agent chooses from what you offer it.
- Why would I build this in n8n and not in Adlyko itself?
- For reports and recurring checks on your account, Adlyko has routines, and you set those up in a few clicks without a workflow. n8n gets interesting as soon as something else comes into play: your CRM, your stock, a spreadsheet or a message in a channel where your team already is.
Sign up first, then build
The endpoint only gives access after you've signed up to Adlyko with your Google account. It costs nothing and you connect your first Google Ads account right away. What the paid layer costs is on the pricing page.
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.
- ChatConnect Google Ads to ClaudeThe chat on claude.ai or in Claude Desktop, with Adlyko as a custom connector.
- ChatConnect Google Ads to ChatGPTA custom connector in the web version, switched on per conversation.
- TerminalManage Google Ads from Claude CodeOne command in your terminal, and your account sits next to your code and your files.
- ChatConnect Google Ads to PerplexityA custom remote connector, so your account data sits next to your research.
- EditorConnect Google Ads to CursorOne line in mcp.json, so your landing page and your campaigns share one window.
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.