Connect Google Ads to Cursor and run campaigns from the editor

One JSON block; three editors read the same schema

You write a single mcpServers entry in ~/.cursor/mcp.json pointing at https://mcp.tecrube.com/mcp. VS Code reads the same JSON from .vscode/mcp.json, Windsurf from ~/.codeium/windsurf/mcp_config.json: same keys, same value, nothing to rewrite when you switch editors.

No npm package to install, no local process to keep alive, no credential in the file; it contains nothing but an address.

The page and the ad get written in the same session

The agent already sees your pricing page, feature components and landing copy. When you ask for responsive search ad headlines, the copy comes from the code going live, not from a summary you pasted an hour ago: real plan names, real prices.

The reverse works too: compare the headlines in your live ads with the hero text of the page they send traffic to, and rewrite whatever drifted. The moment you push the commit that adds a new route is also the right moment to build the campaign that sends traffic there; the sitelink extensions point at routes you wrote four minutes ago.

Brakes designed for an agent that keeps going on its own

Cursor's agent chains tool calls back to back and many people leave auto-run on; that is exactly why the write path is gated on the server. Every action that would change the account returns a preview first: which account, which campaign, current value, proposed value. It is applied only after you explicitly approve.

Any single budget increase above 50% is rejected outright. Every applied change is written to the audit log. The client-side auto-run setting only lets the agent produce proposals faster; it cannot grant spending authority.

Tag Manager and GA4 work without a browser detour

The developer wiring up a conversion can create the tag and trigger with the Google Tag Manager tools, publish the container version, then verify in GA4 that the event actually landed; all in the window where that button's code lives. The Search Console tools show pages with impressions but almost no clicks in the same session.

The answer lands in your repo, not just the chat pane

Because Cursor can write files, the report does not have to stay stuck in the chat panel. Ask for last week's spend, conversions and cost per conversion and have it written to docs/marketing/weekly.md, then commit the report next to the code it describes. Next week you compare against a file, not a screenshot.

Set it up in 60 seconds

• 1. Open ~/.cursor/mcp.json, create it if missing, and paste: { "mcpServers": { "tecrube": { "url": "https://mcp.tecrube.com/mcp" } } }. That is the entire setup.
• 2. Reload the window; the tecrube server appears in Cursor's MCP settings with its tool list. On the first tool call the hosted OAuth screen opens in the browser; sign in with Google and pick the ad account the connector may touch.
• 3. Ask in agent mode. Cursor's agent is what calls MCP tools; a plain editor question triggers nothing. Reads return instantly, write requests wait at the preview stage for your approval.
• 4. Same connector in other editors: VS Code .vscode/mcp.json, Windsurf ~/.codeium/windsurf/mcp_config.json. Your Tecrube account and authorisation are shared across all of them; connect once.

Ask in plain English

• “Read src/app/pricing/page.tsx; write 15 headlines and 4 descriptions with the real plan names and prices, draft a responsive search ad for my brand campaign and show it before applying.”
• “Compare the headlines in my live search ads with the hero text on the home page; rewrite the ones that no longer match.”
• “The /integrations page ships today. Build a paused search campaign with a $30 daily budget; add exact-match keywords and sitelinks pointing at routes in this repo.”
• “Create a GTM tag and trigger for the sign-up button in components/signup-modal.tsx, then publish the container version.”
• “Pull the last 30 days of spend, conversions and cost per conversion; write the summary to docs/marketing/weekly.md.”