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 LinkedIn Ads already connected — the connector acts on that connection, so Codex never handles a LinkedIn 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 LinkedIn Ads account and answers — no account to name, no confirmation to give first.
- With Sprites, what is our LinkedIn CPL by job function this quarter?
- Use Sprites to build an ABM campaign for Series B fintechs in the US, 200-1000 employees.
- Ask Sprites which LinkedIn audiences are saturated and should be rotated.
- Have Sprites draft 3 new sponsored-content intros for our best-performing lead-gen form.
- With Sprites, compare LinkedIn spend and leads this month against last month.
Run `codex mcp list` and confirm sprites shows as connected.
What Codex can do with LinkedIn Ads
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.
Cost per lead that names the segment
CPL by job function, seniority, company size and account, not one number for the whole account.
Build the ABM list in the chat
ICP criteria in, a matched company audience out, with the reach per tier stated before you spend.
Multi-thread the buying committee
Separate audiences for the champion, the economic buyer and the blocker, each with its own message.
Refresh sponsored content
New intros and creative drafted against what already converts, previewed in the feed.
Catch the quiet CPL drift
Frequency, audience saturation and the week the form fill rate started sliding.
Report without exporting
A period comparison your agent can read aloud, sourced from Campaign Manager rather than a slide.
How approvals work here
Codex renders tool results as text, so a LinkedIn 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, campaign groups, creatives and audiences
- Spend, impressions, clicks, leads, CPL and form completion rate
- Demographic breakdowns: function, seniority, company, industry
- Matched-audience size and account coverage
What it can change
- Create campaigns, audiences, matched account lists and creatives
- Budgets, schedules, bids, targeting and status
- All of it gated behind an approval card
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.
LinkedIn Ads 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 LinkedIn Ads account without asking?
Codex renders tool results as text, so a LinkedIn 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 LinkedIn Ads API key or developer token?
No. LinkedIn Ads is connected once inside Sprites through LinkedIn Campaign Manager, and the connector acts on that connection. Codex never sees a credential for it.
Why Codex for LinkedIn Ads 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.
Does it work with LinkedIn lead-gen forms?
Yes. Form completion rate and cost per lead are read per campaign and per segment, and new lead-gen campaigns are built with the form attached.
Can it upload a target account list?
It builds one. Give it the ICP criteria and it matches companies into a LinkedIn matched audience, showing the reach per tier before anything runs.
Keep going
The same Codex connector reaches every other channel — nothing else to add.
LinkedIn Ads, from Codex
Paste one URL, sign in once, and the next LinkedIn question you ask Codex gets answered from the live account.