How to Manage Google Ads from Cursor: The Full Workflow (2026)

What you can manage from Cursor, at a glance

Everything below runs from the Agent panel once the account is connected. The right-hand column is the honest answer to the question people actually ask: yes, Cursor can change a Google Ads account — but only through a write tool you approve.

Rows 1 to 4 are the management loop; rows 5 to 8 feed it. The pattern that makes this work in an editor rather than a chat window is that every row ends with a file — a negative list, a bid plan, a digest — that the next run can read.

Step 1: connect the account (about 2 minutes)

Cursor reads MCP servers from .cursor/mcp.json in the project or ~/.cursor/mcp.json in your home directory. A remote server needs only a url. The managed Ryze AI connector is the fastest route because it authenticates with a Google sign-in and holds no secrets in the file, so the config can be committed for the team.

Self-hosting is possible with Google's official Google Ads MCP server as a stdio entry; it needs a developer token and a Cloud project. The five routes are ranked in how to connect Cursor to Google Ads.

Step 2: the weekly operating loop

Google Ads does not need daily hands; it needs the same five checks every week, in the same order, with the results written down. This is the schedule we run. Each row is one slash command and about ten minutes, most of it reading the output.

Two things make the loop stick. The outputs are files, so Thursday's change run reads Tuesday's negative list rather than re-deriving it. And the changes/ folder is an audit trail: what was applied, when, why, and what the metric did afterwards — which is what you need on the Monday two weeks later when someone asks why CPA moved.

Step 3: diagnose — the three prompts that find the money

Run diagnostics before touching anything. The average account has three to five diagnosable problems at any time, and the Agent finds them faster than a human because it does not skip rows. These three are the Tuesday and Wednesday jobs; the full skill files have the complete instructions.

Wasted spend (Tuesday)

CPA spike (Wednesday, when it moves)

Quality Score (Wednesday, monthly)

Read every diagnosis bottom-up: the ranked list is the headline, the evidence lines tell you whether the Agent reasoned from your numbers. If a cause is marked Critical with thin evidence, ask for the exact rows that support it before you act on it.

Step 4: optimize — ship changes with two approvals

Thursday is the only day the account changes. Three prompts, each of which ends with the Agent showing a list and waiting. Cursor asks before every MCP tool call; the connector's write tools are approval-gated on the server side as well. Both layers stay on.

Apply the negative list

Reallocate budget

Adjust bid targets

Step 5: report — files the team actually reads

Reporting is where Cursor beats a chat assistant outright. The digest is a Markdown file in the repo, the executive summary is a page, and both can be committed, diffed and linked from Slack. The Monday and Friday jobs:

Weekly digest (Monday)

Executive summary (Friday, monthly)

Anomaly scan (Friday)

One habit worth building: ask the Agent to append a one-line result to changes/ two weeks after every Thursday change (“negatives applied 2026-09-04: wasted spend down $1,240/month, CPA -6%”). That closes the loop and turns the folder into the account's memory.

Step 6: automate — what Cursor can schedule and what it cannot

The desktop app runs when you are in it. Three ways to make the loop run without you, in increasing order of hands-off.

Guardrails that keep this safe

Every one of these came from a mistake we made or watched someone make. Put them in the rule file so every skill inherits them.

• Pause, never delete. Removals in Google Ads cannot be undone. The connector's delete tool only runs on an item-by-item approved list; the rule should say the Agent never asks for it.
• Show the list, then wait. Every write prompt ends with “wait for my approval”. Cursor's tool approval is the second gate; keep both.
• Cap single changes at 20%. Budgets and bid targets move in steps. A 35% budget shift is three Thursdays, not one.
• Name the conversion action. Conversions vs all conversions is the most common reason numbers do not match the UI. Put it in the rule.
• Keep secrets out of mcp.json. The managed connector has none; any server that needs a developer token or API key gets it from an environment variable.
• Log everything to changes/. Date, what, why, and the two-week result. This is the file that saves you in the next budget review.

Cursor vs Claude vs Grok for running Google Ads

All three connect to the same MCP server, so the data is identical. The difference is what happens to the output and where the work runs.

The practical answer for most teams is to pick the tool they already have open. If that is Cursor, this guide is the workflow; the same loop exists for Claude and for Grok. Running Meta as well? The Meta version of this workflow is how to manage Meta Ads from Cursor.

For the product side, the Ryze help center covers what the Ryze agent manages in Google Ads and approvals.