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 SEO and Search Console already connected — the connector acts on that connection, so Codex never handles a SEO 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 SEO and Search Console account and answers — no account to name, no confirmation to give first.
- With Sprites, write a post on "programmatic SEO for SaaS" and put it in WordPress as a draft.
- Ask Sprites which queries we rank 8-20 for and could reach the top 5.
- Use Sprites to optimize our /pricing page for "ai ads platform pricing".
- Have Sprites do keyword research for the integrations section and cluster it by intent.
- With Sprites, find pages that lost position in the last 28 days and say why.
Run `codex mcp list` and confirm sprites shows as connected.
What Codex can do with SEO and Search Console
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.
It writes onto the site, not into the chat
WordPress, Webflow, Shopify, Framer, Wix, Ghost or a custom CMS: the post lands as a draft with metadata and internal links already set.
Keyword research with real numbers
Volume, difficulty and intent clustering from live data, not a model's recollection of a keyword tool.
Edit a page without breaking it
Page edits arrive as a diff. You see exactly which block changes before anything touches the live site.
Read what Search Console knows
Queries you nearly rank for, pages that slipped, and the impressions you are leaving on the table.
Internal links that already exist
New posts link into the site's real structure, because Sprites has read it.
Metadata that is not an afterthought
Titles, descriptions, focus keyphrases and schema written with the page rather than bolted on.
How approvals work here
Codex renders tool results as text, so a SEO 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
- Search Console queries, impressions, clicks and average position
- Your live site: structure, internal links, existing pages and voice
- Keyword volume, difficulty and SERP composition
- What currently ranks for the target query
What it can change
- Blog posts, created as drafts in your CMS
- Landing and service pages, created or edited as a reviewable diff
- Titles, meta descriptions, focus keyphrases, headings and schema
- Publishing is always a separate, explicit 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.
SEO and Search Console 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 SEO and Search Console account without asking?
Codex renders tool results as text, so a SEO 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 SEO and Search Console API key or developer token?
No. SEO and Search Console is connected once inside Sprites through Google Search Console and your CMS, and the connector acts on that connection. Codex never sees a credential for it.
Why Codex for SEO and Search Console 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.
Which content management systems does it publish to?
WordPress, Webflow, Shopify's blog, Framer, Wix, Ghost and custom CMSes through a webhook. The CMS is connected once in Sprites; your agent never handles the credential.
Will it publish without asking?
No. Posts arrive as drafts and page edits arrive as diffs. Publishing is a separate approval, and a page edit shows you every block it would change.
Keep going
The same Codex connector reaches every other channel — nothing else to add.
SEO and Search Console, from Codex
Paste one URL, sign in once, and the next SEO question you ask Codex gets answered from the live account.