Sprites
Perplexity133d livePerplexity Computer
Add Sprites to Lovable
Available on Custom MCP chat connectors are available on all Lovable plans. You need a Sprites account with Meta Ads already connected — the connector acts on that connection, so Lovable never handles a Meta credential.
Open Connectors
In Lovable, open Connectors and scroll to the bottom of the list, past the prebuilt catalogue.
LovableConnectorsCustom · MCPAdd 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 · MCPNameSpritesMCP server URLhttps://mcp.sprites.ai/mcpSign 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
AllowCancelKnow 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.
Run the first prompt
Ask Lovable this. It routes to a Sprites door, which reads your Meta Ads account and answers — no account to name, no confirmation to give first.
- With Sprites, which Meta creatives are fatiguing and what should replace them?
- Ask Sprites for 5 new hooks for our best-performing Instagram ad.
- Use Sprites to compare Meta ROAS this month against last month by ad set.
- Have Sprites check whether our ad sets are overlapping on audience.
- With Sprites, show me what our top 3 competitors are running on Meta right now.
Open Connectors; Sprites shows as connected, and the chat can answer a question about your account while you build.
What Lovable can do with Meta 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.
See fatigue before the CPA does
Frequency, first-time impression ratio and the day a creative's CTR broke trend, per ad rather than per campaign.
Get new creative, not a brief
Hooks, headlines and image concepts drafted against what is already working, previewed in the real placement.
Untangle the ad sets
Audience overlap, learning-phase resets and the ad sets quietly bidding against each other.
Watch the competition
Live ads from any advertiser in the Meta ad library, read as angles rather than screenshots.
Launch across placements
Campaign, ad sets, audiences and ads in one editable proposal, with the creative attached.
Reallocate on evidence
Move budget to the ad set that earns it, with the before-and-after stated in the card.
How approvals work here
Lovable renders tool results as text, so a Meta change comes back written out rather than as a card. Nothing is applied until you approve it, and the approval waits for you in Sprites — open it there and the same run continues.
What it reads
- Campaigns, ad sets, ads, audiences and their status
- Spend, ROAS, CPA, CTR, frequency and placement breakdowns
- Creative assets and per-creative performance
- Public competitor ads from the Meta ad library
What it can change
- Create campaigns, ad sets, audiences and ads
- Budgets, schedules, statuses and targeting
- New creative, previewed in placement before anything ships
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.
Meta 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 Meta Ads account without asking?
Lovable renders tool results as text, so a Meta change comes back written out rather than as a card. Nothing is applied until you approve it, and the approval waits for you in Sprites — open it there and the same run continues.
Do I need a Meta Ads API key or developer token?
No. Meta Ads is connected once inside Sprites through Meta (Facebook and Instagram) Ads, and the connector acts on that connection. Lovable never sees a credential for it.
Why Lovable for Meta 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.
Do I need a Meta developer app or a system user token?
No. You connect Meta once inside Sprites with OAuth; the MCP connector then acts on that connection. Your agent never sees a token.
Can it publish an ad without me seeing it?
No. Creative comes back as a preview in the real placement, editable, and ships only when you approve it.
Keep going
The same Lovable connector reaches every other channel — nothing else to add.
Meta Ads, from Lovable
Paste one URL, sign in once, and the next Meta question you ask Lovable gets answered from the live account.