SpritesAdd Sprites to Cursor
Available on Any Cursor plan that allows MCP servers, on desktop and on Cursor web agents. You need a Sprites account with AI visibility (AEO) already connected — the connector acts on that connection, so Cursor never handles a AEO credential.
Write the config
Put the entry in ~/.cursor/mcp.json to have Sprites available in every project, or in .cursor/mcp.json inside one repo to scope it there.
~/.cursor/mcp.json{ "mcpServers": { "sprites": { "url": "https://mcp.sprites.ai/mcp" } } }Or add it from the UI
Cursor lists MCP servers under Customize in the sidebar; adding one there writes the same file.
CursorCustomizeMCPNew MCP serverSign in
Cursor finds the Sprites authorization server from the endpoint's protected-resource metadata, registers itself, and opens a browser for the consent screen. Desktop completes on http://localhost:8787/callback and web agents on cursor.com; both are pre-registered, so there is nothing to allowlist.
Spriteswants access on behalf of Cursor- Read your connected ad accounts and site data
- Draft campaigns, creatives and pages for your approval
- Apply only the changes you approve
AllowCancelKeep it in the repo, not in your dotfiles
A project-scoped .cursor/mcp.json is worth committing: every teammate who opens the repo gets the same connector and signs in as themselves. The file holds a URL and nothing else — the token is per person and never touches the config.
Run the first prompt
Ask Cursor this. It routes to a Sprites door, which reads your AI visibility (AEO) account and answers — no account to name, no confirmation to give first.
- With Sprites, who gets cited when someone asks ChatGPT for the best AI ads platform?
- Ask Sprites to check our AI visibility against our three named competitors.
- Use Sprites to write a comparison page for "us vs [competitor]" and draft it on the site.
- Have Sprites generate an llms.txt from what we actually publish.
- With Sprites, set up a weekly check on our top 20 buying prompts.
Open Cursor Settings → MCP and confirm sprites is listed as connected with its tool count.
What Cursor can do with AI visibility (AEO)
The same doors, whichever client you are in. The campaign and the page it points at live in the same window: change the pricing copy, then have Sprites update the ads that quote it, without a second tool.
Find out whether you exist
The prompts your buyers type, run against the answer engines, with who gets named and who does not.
See who is taking the citation
The competitor being cited, and the page the engine is reading to do it.
Write the page that wins it back
Answer pages, FAQ pages and comparison pages, structured the way answer engines actually lift from.
Ship an llms.txt that is not a stub
A real index of what you publish, generated from the site rather than hand-listed and forgotten.
Track it over time
Visibility per prompt per engine, so a change is attributable to the page that caused it.
Get told when it slips
A scheduled check that messages you when a citation you had is gone.
How approvals work here
Cursor renders tool results as text, so a AEO 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
- Answer-engine responses for the prompts you care about
- Which brands and pages get cited, and how often
- Your own site structure and existing answer coverage
- Competitor pages the engines are reading
What it can change
- Answer pages, FAQ pages, comparison and "vs" pages
- llms.txt and entity pages
- All drafted onto your site and published only on approval
When it does not work in Cursor
Three things go wrong in this client specifically, and each has a one-line fix.
The Connect button does nothing and no request is made.
A known Cursor issue on some builds. Update Cursor, then remove and re-add the server; if it persists, restart Cursor with the config already in place so the connection is made at startup.
Cursor authenticates but every call comes back unauthorized.
The token was issued for a different address. Delete the server entry, restart Cursor, and re-add it with the exact endpoint above — every grant is bound to that one URL, so a variant of it will not be honoured.
The agent invents ad-platform tools instead of calling Sprites.
Name it: "use Sprites to…". Cursor ranks its own tools first, and a generic phrasing loses to the built-in search.
AI visibility (AEO) and Cursor: questions
Which URL do I paste into Cursor?
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 Cursor change my AI visibility (AEO) account without asking?
Cursor renders tool results as text, so a AEO 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 AI visibility (AEO) API key or developer token?
No. AI visibility (AEO) is connected once inside Sprites through Your site, plus AI answer-engine tracking, and the connector acts on that connection. Cursor never sees a credential for it.
Why Cursor for AI visibility (AEO) specifically?
The campaign and the page it points at live in the same window: change the pricing copy, then have Sprites update the ads that quote it, without a second tool.
What is AEO?
Answer engine optimization: getting cited in the answers ChatGPT, Perplexity, Claude, Gemini and Google AI Overviews give, rather than ranking in a list of ten blue links. The unit of success is a citation, not a position.
How does it know whether we are cited?
It runs your prompts against the engines and reads the answers, recording which brands and sources are named. It is a measurement, not an estimate.
Keep going
The same Cursor connector reaches every other channel — nothing else to add.
AI visibility (AEO), from Cursor
Paste one URL, sign in once, and the next AEO question you ask Cursor gets answered from the live account.