SpritesAdd Sprites to Codex
Available on Anywhere Codex CLI runs — a ChatGPT plan that includes Codex, or an API key. You need a Sprites account with AI visibility (AEO) already connected — the connector acts on that connection, so Codex never handles a AEO credential.
Add the server
One command writes the entry into ~/.codex/config.toml for you.
Terminalcodex mcp add sprites --url https://mcp.sprites.ai/mcpOr write the config by hand
The same entry in ~/.codex/config.toml, or in .codex/config.toml inside a trusted project when you want the connector scoped to one repo.
~/.codex/config.toml[mcp_servers.sprites] url = "https://mcp.sprites.ai/mcp" auth = "oauth"Sign in
Codex opens a browser for the Sprites consent screen and stores the token locally. Sprites supports dynamic client registration and client ID metadata documents, so there is nothing to pre-register.
Terminalcodex mcp login spritesApprove changes by name
Codex renders results as text, so a pending change comes back written out rather than as a card you can click. Nothing is applied until you approve it, and the approval waits for you in Sprites — open it there and the same run continues.
Pending changeChangeDaily budget $40 → $65Gategate_7f2c…
Run the first prompt
Ask Codex 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.
Run `codex mcp list` and confirm sprites shows as connected.
What Codex can do with AI visibility (AEO)
The same doors, whichever client you are in. Marketing work that belongs in a commit: Codex can read the landing page it is about to ship and brief Sprites on the campaign pointing at it, in one session.
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
Codex 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 Codex
Three things go wrong in this client specifically, and each has a one-line fix.
Codex says the tool is not found.
The config was edited while a session was open. Restart Codex — it reads config.toml at startup.
Login loops without ever completing.
The OAuth callback defaults to http://127.0.0.1/callback. If something else on the machine holds that port, set mcp_oauth_callback_url in config.toml and log in again.
Codex says a change was applied and nothing happened in the account.
It was proposed, not applied — that is the design. The approval is waiting in Sprites; open it there and the run continues from where it stopped.
AI visibility (AEO) and Codex: questions
Which URL do I paste into Codex?
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 Codex change my AI visibility (AEO) account without asking?
Codex 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. Codex never sees a credential for it.
Why Codex for AI visibility (AEO) specifically?
Marketing work that belongs in a commit: Codex can read the landing page it is about to ship and brief Sprites on the campaign pointing at it, in one session.
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 Codex connector reaches every other channel — nothing else to add.
AI visibility (AEO), from Codex
Paste one URL, sign in once, and the next AEO question you ask Codex gets answered from the live account.