Connect Google Ads to Cursor
Cursor can read and change your Google Ads account once Adlyko is in your configuration as a remote MCP server. That's one line with a URL, followed by a Google sign-in in your browser. From then on your campaigns sit in the same window as the landing page your ads point to, and that's exactly why this connection belongs in an editor rather than in a separate tab.
- Where you set it up
- Cursor Settings, the section for tools and MCP
- Or by hand
- mcp.json in your home folder or .cursor/mcp.json in your project
- Server type
- Remote, with only a url and no command
- Signing in
- Through the Needs login message, then OAuth in your browser
Add Adlyko in four steps
- 1
Sign up for Adlyko
Sign in with the Google account you use to manage your Google Ads. After that you don't need to configure a key or header in Cursor.
- 2
Open the MCP section in the settings
Go to Cursor Settings and choose the section for tools and MCP. In recent versions it's called Tools & MCP, in earlier versions Tools & Integrations. Click New MCP Server there; Cursor then opens the configuration file.
- 3
Add Adlyko as a server with a URL
A remote server only needs a url. Copy the block below and save the file. There's no command or args, because Adlyko doesn't run on your own machine.
https://mcp.adlyko.com/mcp - 4
Sign in through the Needs login button
As soon as the file is saved, Adlyko appears in the overview with a message that you still need to sign in. Click it, choose the same Google account you signed up with in the browser, and Cursor stores the sign-in itself from then on.
This is what it looks like in mcp.json
This is the full block. If you already have other servers, add only the adlyko part inside mcpServers.
{
"mcpServers": {
"adlyko": {
"url": "https://mcp.adlyko.com/mcp"
}
}
}Where the file lives decides where the connection applies. In your home folder, Adlyko is available in every project. Put it in .cursor/mcp.json in a project folder and it only applies there, which is handy if you have a separate folder per client. No key goes in the file: access runs through your Google sign-in, not through something you could commit by accident.
Your first task
In an editor you have something a chat window doesn't: the page your ads lead to. So ask for something that needs both.
Read the search terms for the last thirty days from my Google Ads and compare them with the copy on the landing page in this project. Which search question does the page not answer?
Based on that, write three ad headlines that match the page, and prepare the matching change in the page itself as a proposal.
What to know about Cursor
- The MCP panel shows which tools each server has and lets you switch them on and off one by one. With a large toolset, that's the button you're looking for when the agent becomes indecisive.
- Cursor handles the sign-in itself and doesn't need an address from you that you'd have to register somewhere. So there's nothing to set up on the Google side.
- Adlyko also writes, not just reads. A change is put to you first and new campaigns come in paused, so an agent that keeps working never puts anything live by accident.
- Prefer a terminal to an editor? Then Manage Google Ads from Claude Code is the same connection with one command. Should the work run on its own at a set time? Then have a look at Run Google Ads from n8n.
If it doesn't work
- Adlyko stays on Needs login
- Click that message to open the browser; Cursor doesn't start the sign-in on its own. If the window closes without a result, close the other Google sessions in that browser or use a private window, so the selection screen appears and you deliberately pick the right account.
- The server works in one project but not in another
- Then Adlyko is in that one project's file. Put it in mcp.json in your home folder if you want it everywhere, or in .cursor/mcp.json in the project folder if you want to keep it separate per project.
- The agent uses the wrong tool or can't find it
- Adlyko provides a lot of tools, and an editor doesn't show an unlimited number to the model at once. In the MCP panel you can switch tools on and off per server. Keep what you actually use in your editor, or name the tool in your instruction.
- Does this work in Cursor on the web too?
- A remote server with a URL isn't tied to your laptop, so yes. In both cases you sign in through your browser, and the stored sign-in belongs to the place where you created it, so you sign in once per environment.
The URL only works with an account
Adlyko ties your Google account to your access, so sign up first. It costs nothing and you connect your first Google Ads account right away. The rates are 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.
- WorkflowRun Google Ads from n8nThe MCP node under your AI Agent, for work that has to run on its own at a set time.
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.