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 your channels already connected — the connector acts on that connection, so Lovable never handles a platform 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.
What Lovable can reach
All ten channels run through the one connector. Rows with a guide go deeper on that pairing; the rest are covered on the channel's own page.
| Channel | What Lovable does with it | Guide |
|---|---|---|
| Google Ads | Converting search terms become the copy on the page being generated, in the same session. | Set up → |
| Meta | The creative angle that works informs the page it points at, so message and destination match. | Set up → |
| Cost per lead by job function, ABM account lists, sponsored content that converts. | Channel → | |
| TikTok | Hook-level hold rates, the next creative batch, and rotation before the CPA moves. | Channel → |
| Performance per subreddit, community-native copy, and the tourist traffic to cut. | Channel → | |
| GA4 | Drop-off and landing-page data shape the layout instead of being reviewed after it ships. | Set up → |
| SEO | Structure and metadata written against Search Console evidence rather than a template default. | Set up → |
| AEO | Who gets cited by ChatGPT and Perplexity for your prompts, and the pages that change it. | Channel → |
| Shopify | Real catalogue and revenue behind whatever storefront view Lovable is building. | Set up → |
| GBP | Performance per location, the listings missing fields, and posts that keep the map pack. | Channel → |
5 of the ten channels have no Lovable-specific guide yet — they are covered in the matrix above and on their own channel pages. A guide gets its own page when the pairing shows real demand or behaves differently enough on Lovable to be worth one.
Marketing workflows worth doing in Lovable
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.
Build a landing page from paid-search evidence
Read the converting search terms first, then write the hero and the proof around the language people actually used.
Generate an ad-account audit interface
A small internal view of waste and opportunity, built against the real account shape.
Create a lead magnet that reflects demand
Pick the topic from what Search Console says people are already asking for, then build the thing.
Iterate checkout UX on real numbers
GA4 and Shopify together, so a checkout change is argued from drop-off data rather than taste.
Permissions, approvals and authentication
You sign in with OAuth and the connector acts on your workspace. No API keys in a config file, no shared service account, and revoking the grant kills the very next call.
| Action | When it happens | What that covers |
|---|---|---|
| Read an account | On request | Spend, performance, search terms, rankings, catalogue |
| Draft a change | On request | Campaigns, creative, budgets, pages and posts |
| Apply a change | Only on your approval | Lovable returns the change as text; the approval waits for you in Sprites |
| Spend money | Only on your approval | New campaigns start paused unless you say otherwise |
| Revoke access | Instantly | The next call after a revoke fails, not the one after that |
Lovable MCP questions
Does the app Lovable builds get access to Sprites?
No, and that distinction matters. A chat connector gives Lovable context while building; the app you ship needs its own integration. Sprites informs what gets written, it does not become part of the deployed product.
Which plans support custom MCP?
Custom MCP servers are available on all Lovable plans as chat connectors.
Can I also drive Lovable from Claude or Cursor?
That is the other direction, and Lovable publishes its own MCP server for it. This page covers bringing marketing data into Lovable; using Lovable from another host is a separate setup on that host.
Can it change my ad accounts on its own?
No. Reads happen on request; every write comes back as a change you approve first, and new campaigns start paused. Nothing is applied because a model decided it should be.
The Custom MCP card is not there.
An admin has turned custom MCP servers off for the workspace under Connectors → Admin settings → Chat connectors. It is a single group toggle rather than a per-server one.
Point Lovable at your ad accounts
One URL, one sign-in, and the next question you ask Lovable about your marketing gets answered from the live account.