Sprites MCP · Google Ads MCP server · Lovable

Google Ads MCP for Lovable: setup in two minutes

Add https://mcp.sprites.ai/mcp as a custom MCP connector in Lovable, sign in to Sprites, and Lovable can read your Google Ads account and propose changes to it. Setup takes about two minutes and needs no API key. Every write comes back as an approval before it touches the account.

MCP server URLhttps://mcp.sprites.ai/mcp

5 steps · about 2 minutes

LovableSprites connected

Where is Google Ads wasting money this month?

Spritesoptimizerunning
SpritesGoogle AdsNeeds your approval
  • Generic — Broad$1,240 · 0 convPause−$1,240
  • "free crm software"search termNegate−$380
  • Brand — ExactIS lost to budget 41%Raise+$25/day
3 changes proposed · nothing appliedReview

Add Sprites to Lovable

Available on Custom MCP chat connectors are available on all Lovable plans. You need a Sprites account with Google Ads already connected — the connector acts on that connection, so Lovable never handles a Google Ads credential.

  1. Open Connectors

    In Lovable, open Connectors and scroll to the bottom of the list, past the prebuilt catalogue.

    Lovable
    ConnectorsCustom · MCP
  2. Add Sprites as a custom MCP

    The Custom card labelled MCP opens the form for any remote MCP server that is not already in the catalogue. Paste the Sprites endpoint and give it a name.

    Custom · MCP
    NameSpritesMCP server URLhttps://mcp.sprites.ai/mcp
  3. Sign in

    Complete the Sprites consent screen. The connection is yours; an admin can turn custom MCP servers on or off for everyone as a group under Connectors → Admin settings → Chat connectors, but individual ones stay private to whoever connected them.

    Spriteswants access on behalf of Lovable
    • Read your connected ad accounts and site data
    • Draft campaigns, creatives and pages for your approval
    • Apply only the changes you approve
    AllowCancel
  4. Know what a chat connector is for

    A chat connector gives Lovable context while you build. It does not become part of the app you ship — Sprites informs what Lovable writes, and the running app talks to whatever you configure for it separately.

Official Google Ads MCP vs Sprites MCP

Google runs its own MCP server at github.com/googleads/google-ads-mcp. Here is what each one covers, so you can pick the one that fits in Lovable — or connect both.

Google publishes its own Google Ads MCP server as open source. It has three tools — a GAQL query runner, resource metadata and a list of accessible accounts — and it is read-only by design: in Google’s words it "cannot modify bids, pause campaigns, or create new assets." Google does not host it. You run it locally with pipx or deploy it to your own Cloud Run, with your own OAuth credentials and a developer token.

Google’s official Google Ads MCP server compared with the Sprites MCP server
Google officialgithub.com/googleads/google-ads-mcpSprites MCPapproval-gated
Where it runsYour machine, or your own Cloud Run deploymentHosted: paste mcp.sprites.ai/mcp and sign in
CredentialsYour OAuth client and a developer token with at least Explorer accessNone to manage — Google Ads is connected once through a Google Partner integration
ToolsThree: GAQL search, resource metadata, accessible customersBroad doors: analyze, optimize, launch, change
WritesNone — read-only by designBudgets, bids, keywords, ads and campaigns, each an approval card applied only on approve
AnalysisReturns rows for the model to reason overA Google Ads specialist reads search terms, change history and impression share before answering
ChannelsGoogle AdsGoogle Ads plus Meta, LinkedIn, TikTok, Reddit, GA4 and SEO
Best atPrecise reporting queries, for people comfortable with GAQL and a terminalDeciding what should change, and changing it with your approval

If you want exact answers to reporting questions and are happy to run a Python package with your own credentials, Google’s server is excellent and free. Use Sprites when you want the answer to turn into a change — a budget moved, a keyword paused, a campaign launched — without hosting anything, or when Google Ads is one channel of several.

Run the first prompt

Ask Lovable this. It routes to a Sprites door, which reads your Google Ads account and answers — no account to name, no confirmation to give first.

  • With Sprites, how did Google Ads do last 30 days vs the 30 before?
  • Use Sprites to find search terms that spent over $50 with no conversion last month.
  • Ask Sprites to build a Search campaign for our pricing page at $80/day.
  • Have Sprites raise the Brand — Exact budget to $65/day and tell me why first.
  • With Sprites, which campaigns are losing impression share to budget rather than rank?

Open Connectors; Sprites shows as connected, and the chat can answer a question about your account while you build.

What Lovable can do with Google Ads

The same doors, whichever client you are in. What it builds can be shaped by what actually converts: a landing page written against the search terms that are really paying, rather than against a guess.

Ask about last week in the thread you are already in

Spend, conversions, CPA, ROAS and the period comparison, read from the live account rather than a stale export.

Find the waste before it compounds

Search terms with cost and no conversion, broad-match drift, and the negatives that would have stopped it.

Launch without the wizard

Campaign, ad group, responsive search ads and keywords arrive as one editable proposal rather than nine screens.

Change one thing precisely

Raise a budget, pause a campaign, add a negative — one approval card, applied on your click.

Ask why, not just what

Impression share lost to rank and to budget, auction pressure, and which of the two actually moved.

Leave a standing order

A Monday morning brief or a nightly waste check that runs on schedule and messages you only when it matters.

How approvals work here

Lovable renders tool results as text, so a Google Ads change comes back written out rather than as a card. The approval waits for you in Sprites — open it there and the same run continues. Nothing is applied until you approve it.

What it reads

  • Campaigns, ad groups, ads, keywords and their status
  • Spend, impressions, clicks, conversions, CPA, ROAS and impression share
  • Search terms, assets and asset performance labels
  • Change history, so a drop can be traced to an edit

What it can change

  • Create campaigns, ad groups, responsive search ads and keywords
  • Budgets, bids, statuses, negatives and targeting
  • Nothing applies without an approval you have seen and clicked

When it does not work in Lovable

Three things go wrong in this client specifically, and each has a one-line fix.

The Custom MCP card is missing.

An admin has switched custom MCP servers off for the workspace under Connectors → Admin settings → Chat connectors. It is a group toggle rather than a per-server one.

The built app cannot reach Sprites.

It is not meant to. A chat connector is build-time context; a shipped app needs its own integration.

Lovable answers about the app rather than the account.

Name the channel — "read the Google Ads search terms and write the hero around the ones converting" — so the request is unambiguous.

Google Ads and Lovable: questions

Which URL do I paste into Lovable?

https://mcp.sprites.ai/mcp. There is one endpoint and every client uses it — every OAuth grant is bound to exactly that address, so a variant of it will not be honoured.

Can Lovable change my Google Ads account without asking?

Lovable renders tool results as text, so a Google Ads change comes back written out rather than as a card. The approval waits for you in Sprites — open it there and the same run continues. Nothing is applied until you approve it.

Do I need a Google Ads API key or developer token?

No. Google Ads is connected once inside Sprites through Google Ads (official Google Partner OAuth), and the connector acts on that connection. Lovable never sees a credential for it.

Why Lovable for Google Ads specifically?

What it builds can be shaped by what actually converts: a landing page written against the search terms that are really paying, rather than against a guess.

Is there an official Google Ads MCP server?

Yes. Google publishes googleads/google-ads-mcp: open source, read-only by design, and not hosted by Google — you run it locally or on your own Cloud Run with your own API credentials. Sprites is a separate, hosted server that reads and changes Google Ads through a Google Partner integration, with every change held for approval.

Is this a Google Ads MCP server I have to host?

No. Sprites is a hosted remote MCP server: you paste one HTTPS URL into your agent and sign in. There is nothing to install, no developer token to obtain, and no API credentials to store on your machine.

Keep going

The same Lovable connector reaches every other channel — nothing else to add.

All Google Ads guides

Google Ads, from Lovable

Paste one URL, sign in once, and the next Google Ads question you ask Lovable gets answered from the live account.