# Cursor + Google Ads: MCP Setup That Works

Add a Google Ads MCP connector to Cursor — the mcp.json shape, where it lives, how tool approvals behave, and how to run ads work beside your code.

Tutorials · Published 2026-08-10, updated 2026-10-18.

> In Cursor, open Settings → MCP and add the server to mcp.json: {"mcpServers":{"adcopilot":{"url":"https://mcp.adcopilot.cloud/mcp"}}}, then sign in with Google the first time it connects. The URL is the same for everyone and holds no secret. The tools appear in Agent mode and reads run freely. Each write is proposed first; for a hard stop, set Cursor's run mode to Allowlist and keep AdCopilot's write tools off the allowlist, because in Auto-review, Cursor's default, a write can run without anyone being asked, and Cursor's cloud agents never ask. The payoff is ads work running beside your actual codebase.

Cursor takes the Google Ads connector as a four-line entry in `mcp.json`,
reached through Settings → MCP. The setup is two minutes; the reason to
do it in Cursor rather than a chat app is what sits next to the tools —
your codebase, in the same Agent session as your ad account. Per-client
config for every other client lives on
[the MCP clients pillar](https://adcopilot.cloud/mcp-clients); this page is Cursor's specifics.

## Add the server

Open Cursor Settings, find the MCP section, and add a new server — Cursor
edits `mcp.json` for you, or you can write it directly:

```text
{
  "mcpServers": {
    "adcopilot": {
      "url": "https://mcp.adcopilot.cloud/mcp"
    }
  }
}
```

Cursor-specific details that matter:

- **The field is `url`** for a remote server — Cursor detects the
  transport from the endpoint, so streamable HTTP needs no extra flags.
- **Two possible homes:** `~/.cursor/mcp.json` (global, every project)
  or `.cursor/mcp.json` (this project only). Use the global one. The
  project file lives in the repo and repos get shared; the URL holds no
  secret — access is your Google sign-in, not the URL — but keeping the
  server out of the repo means each teammate adds their own and signs in as
  themselves. [The security model](https://adcopilot.cloud/security) explains how access follows
  your Google grant.

Back in the MCP settings page, the server should show as connected with
a tool count in the thirties — reads like the GAQL query, writes like
campaign creation and adding negative keywords. Toggle it on if it is
not already.

## First prompts — in Agent mode

MCP tools run in Cursor's Agent mode, not plain autocomplete or a bare
chat. Open an Agent chat and start with reads:

```text
List the Google Ads accounts you can see.
```

```text
In account <account>: last 14 days of spend, conversions and cost per
conversion by campaign. Then the top 10 search terms with cost and no
conversions. Read-only — change nothing.
```

Reads change nothing, so allowing them is safe. A write — adding a negative,
creating a paused campaign — stops for you only in Cursor's **Allowlist** run
mode (Settings → Agents → Approvals & Execution) with AdCopilot's write tools
off the allowlist: then Cursor shows the tool call and asks before running
it. In **Auto-review**, Cursor's default, a classifier can let it run
unasked, and Cursor's cloud agents never ask. Keep that setting: running
unasked belongs to read-only servers, and the reasoning — which calls to
graduate, which to gate forever — is the
[approval workflow](https://adcopilot.cloud/tutorials/approval-workflows-for-ai-ads-changes).

## The actual point: ads and code in one session

Everything above works in any client. What Cursor adds is that the agent
holding your ad account also holds your repository, and real tasks live
across both:

```text
Read the hero copy and pricing section of app/landing/page.tsx. Now pull
the responsive search ads in campaign <campaign> from account <account>.
Where do the ads promise something the page no longer says? Propose ad
copy updates — show me before creating anything.
```

```text
We renamed the /pricing route in this repo. Which enabled ads or
sitelinks in account <account> still point at the old URL? List them,
then create replacement sitelinks on the new route for the ones I
confirm — I'll retire the old links in the Google Ads UI.
```

Message-match audits, URL drift after refactors, drafting a campaign for
the feature you just shipped from the code that implements it — these
are one-session jobs in Cursor and multi-tool afternoons anywhere else.
Audit output can land in the repo too: ask for findings written to a
markdown file and commit it, the same
[file-based pattern](https://adcopilot.cloud/tutorials/claude-code-google-ads-workflow) that
makes terminal clients good at recurring checks.

## Quirks

- **Agent mode only** — if the tools seem missing, check which mode the
  chat is in before debugging config.
- **JSON errors fail silently** — a stray comma and Cursor just ignores
  the file. The MCP settings page showing the server is your parse
  check.
- **Restart-ish** — config changes usually surface on toggling the
  server or reopening settings; a full restart is the reliable fallback.
- **Same address everywhere** — the URL works unchanged in
  [Gemini CLI](https://adcopilot.cloud/tutorials/gemini-cli-google-ads-setup), Claude and
  Copilot. One connector, many clients; if it connects nowhere, that is
  [a troubleshooting matter](https://adcopilot.cloud/tutorials/troubleshooting-your-ads-connector),
  not a Cursor one.

Five-minute version: paste the JSON into the global `mcp.json`, open an
Agent chat, run the two read prompts, and try the message-match audit on
a page you actually ship. No connector yet?
[Start free](https://app.adcopilot.cloud/signup) — sign in with your own
Google account, and Cursor is one paste from your ad account. Five days on the full Pro plan for your first workspace, no card to start (one is needed after 1,000 operations).

## Questions

### Why don't the ads tools show up in my Cursor chat?

Three usual causes: the chat is not in Agent mode — MCP tools only run there; the server toggle in Settings → MCP is off; or the JSON has a syntax error, in which case Cursor ignores the file quietly. Check the MCP settings page first — a healthy server shows its status and a tool count — then fix mode or JSON accordingly.

### Should the connector go in project mcp.json so my team gets it?

No — each teammate should connect with their own Google sign-in rather than inherit a server config from the repo. The URL itself holds no secret (access follows the Google account, not the URL), so committing it is not a credential leak, but a shared config muddies attribution and revocation. Keep it in the global ~/.cursor/mcp.json, and let each person add their own and sign in as themselves; that keeps access individually revocable and changes correctly attributed.

### Is it safe to let Cursor run MCP tools without asking?

Running without asking is fine for a server that can only read; this one can write. Set Cursor's run mode to Allowlist and keep AdCopilot's write tools off the allowlist, whatever you allow elsewhere: in Auto-review, Cursor's default, a classifier can let a write run unasked, and Cursor's cloud agents never ask. The confirmation you would be skipping is the only human step between a misunderstood instruction and a changed campaign. Reads never need the ceremony; writes always deserve it.

---

This is the markdown copy of https://adcopilot.cloud/tutorials/cursor-google-ads-setup. The index of the site's pages is https://adcopilot.cloud/llms.txt.
