Skip to content

Connect Google Ads to Cursor

  • Does the gclid survive?

Check your Google Ads tracking against the code you're editing in Cursor, with live campaign data next to your landing pages. Lemonado connects them in about 2 minutes, no API keys needed.

MCPhttps://mcp.lemonado.io/mcp

Why connect Google Ads to Cursor?

In Cursor, the agent already sees your landing pages, UTM helpers and conversion tags. Add Lemonado and it can compare them with what Google Ads actually records, so broken attribution shows up as a diff, not a mystery in next month's report.

  • Your whole Google Ads account

    Campaigns, ad groups, ads and assets, ready to ask about.

  • Always today's numbers

    Performance Max asset groups, synced from Google Ads automatically, so answers use today's numbers.

  • Connect all your tools

    Questions like "What's our real ROAS?" use Google Ads and Meta Ads, GA4 at once.

How to connect Google Ads to Cursor

Before you start

  • A Google Ads account you can sign in to
  • Cursor installed
  • A Lemonado account (the free trial works)
  1. 1

    Connect Google Ads in Lemonado

    In Lemonado, open Connectors, find Google Ads and sign in. If you use a manager (MCC) account, choose the client accounts you want, not only the manager.

  2. 2

    Turn on external access

    In the company's settings, open External tools, turn the connection on, choose which sources it can reach and copy the server URL.

    text
    https://mcp.lemonado.io/mcp
  3. 3

    Open your MCP config

    Open ~/.cursor/mcp.json for every project, or .cursor/mcp.json for this project only. Create the file if it doesn't exist.

  4. 4

    Add Lemonado

    Merge this into the file and save.

    json
    {
      "mcpServers": {
        "lemonado": {
          "url": "https://mcp.lemonado.io/mcp"
        }
      }
    }
  5. 5

    Sign in

    Cursor asks you to sign in to Lemonado. Approve access, then ask the agent about your data.

  6. 6

    Ask Cursor about Google Ads

    Try "Look at our checkout redirect and tell me if the gclid survives it. Then check whether Google Ads conversions dropped after the last deploy." Or ask: "Do our UTMs match?" or "What did each campaign spend?"

Good to know

  • Editing the file directly avoids relying on menu labels that change between Cursor versions.

What can Cursor do with Google Ads?

Cursor's agent reads your Google Ads data while it edits: it fills components with real data, checks tracking code and writes the analysis next to your code.

Cursor logoCursor

Look at our checkout redirect and tell me if the gclid survives it. Then check whether Google Ads conversions dropped after the last deploy.

The redirect in checkout/route.ts drops query params, so the gclid is lost. Google Ads conversions fell 31% the day after that file changed on Sept 12.

Source: Google Ads + your code

Reading this as an AI agent?

Everything an agent needs to set this up, in plain text. Paste this page's link into Cursor and ask it to connect you, or copy the block.

For agents · markdown
# Connect Google Ads to Cursor (Lemonado MCP)

- Server URL: https://mcp.lemonado.io/mcp
- Transport: Streamable HTTP
- Auth: OAuth; the user signs in to Lemonado in the browser. No API keys.
- In Lemonado: connect the Google Ads account. If you use a manager (MCC) account, choose the client accounts you want, not only the manager.
- In Cursor: ~/.cursor/mcp.json

```json
{
  "mcpServers": {
    "lemonado": {
      "url": "https://mcp.lemonado.io/mcp"
    }
  }
}
```

First question to try: "Look at our checkout redirect and tell me if the gclid survives it. Then check whether Google Ads conversions dropped after the last deploy."

More: https://lemonado.io/integrations/google-ads · https://lemonado.io/llms.txt
FAQ

Frequently Asked Questions

Yes. Add Lemonado to ~/.cursor/mcp.json once and Cursor's agent can query Google Ads while it works on your code. Google's official server also runs in Cursor, but it needs Python, a Google Cloud project and a developer token.

You can. Google publishes an open-source Google Ads MCP server (googleads/google-ads-mcp on GitHub). It's free and read-only, but it runs locally or on your own Cloud Run and needs a Google Cloud project with OAuth credentials. In Cursor that means setting up the Cloud project, credentials and Python yourself. Lemonado is one URL with a normal Google sign-in, and also covers your other channels.

Open Cursor's settings and find lemonado in the MCP list. A red dot or a sign-in prompt means the login expired. Restart Cursor after editing mcp.json. In Lemonado, check that Google Ads is connected and External tools is on for the company. If you sign in with a manager (MCC) account, ask about a client account by name: the data sits in the client accounts, not the manager.

Yes, if both are connected in Lemonado. One connection reaches every source you allow, so you can ask things like "Put Google Ads spend next to Stripe revenue by week for the last quarter."

MCP is included in Lemonado's paid plans and in the free trial, so you can try it before you pay.

See plans and pricing

Still have a question?

Shoot us an email at hello@lemonado.io.

Try for free

Stop fighting with data. Start feeding your AI.

Connect your data to AI and free your team from reporting and busywork.

Try Lemonado free