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 Zoho CRM already connected — the connector acts on that connection, so Codex never handles a Zoho CRM 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…
Official Zoho CRM MCP vs Sprites MCP
Zoho runs its own MCP server at zoho.com/mcp. Here is what each one covers, so you can pick the one that fits in Codex — or connect both.
Zoho runs its own MCP platform, in early access, with four servers for Zoho CRM: Data Insights for read-only queries, Data Operations for creating, updating and deleting records, Modules for fields and layouts, and Workflow & Automation for rules and blueprints. Agents sign in with Zoho OAuth and inherit your permissions. It reaches CRM and other Zoho apps such as Mail, Desk and Projects, and knows nothing about your ad accounts. See Zoho’s own documentation.
| Zoho officialsince July 2025 | Sprites MCPapproval-gated | |
|---|---|---|
| Endpoint | Servers you set up in Zoho MCP (early access) | mcp.sprites.ai/mcp |
| Reaches | Zoho CRM and other Zoho apps | Zoho CRM beside Google Ads, Meta, LinkedIn, TikTok, Reddit, GA4 and SEO |
| Writes | Create, update and delete records; change modules and automation | Leads and contacts, one deal at a time, and notes — each approved on a card |
| Deletes | Available on the Data Operations server | Impossible — the connection has no delete permission |
| Attribution | CRM data only | Closed-won deals matched to the ad spend that produced them |
| Schema changes | Modules and automation rules are in scope | Not offered; Sprites works inside your existing fields |
If you want an agent to administer Zoho itself — reshape modules, write automation, bulk-delete — Zoho’s own servers are built for that. Use Sprites when the CRM question is really a marketing question: which campaigns produced revenue, which leads came from where, and what to change in the ad accounts as a result, with every CRM write held for your approval and no way to delete anything.
Why run Zoho CRM ads through Sprites
Codex is the interface; the connector decides what it can see and what it is allowed to do. Six things change when that connector is Sprites.
The CRM next to the ad accounts
A Zoho-only connector answers with Zoho. Sprites reads Zoho beside Google Ads, Meta and LinkedIn, so cost per closed-won deal is one question, and the budget move it implies is the next one.
Every channel on one connectorScopes chosen so it cannot delete
Sprites asks Zoho for read access plus exactly three kinds of write — create or update leads and contacts, update deals, add notes. There is no delete scope to misuse, however a request is phrased.
Every write approved, then verified
Lead imports, deal updates and notes each arrive as a card with the before and after. After you approve, Sprites reads the record back to confirm the change landed as shown.
Run the first prompt
Ask Codex this. It routes to a Sprites door, which reads your Zoho CRM account and answers — no account to name, no confirmation to give first.
- With Sprites, which campaigns produced closed-won deals in Zoho this quarter?
- Ask Sprites how many Zoho leads came in last month by lead source, next to our ad spend.
- Use Sprites to add the 40 webinar sign-ups in this CSV to Zoho as leads with Lead_Source set to Webinar.
- Have Sprites move the Acme renewal deal to Negotiation and set the next step to "send pricing".
- Every Monday, have Sprites summarize open Zoho deals by stage and owner.
Run `codex mcp list` and confirm sprites shows as connected.
Running Zoho CRM from Codex
The jobs people hand over first, start to finish: what you type, what Sprites does with it, and what comes back to approve.
Cost per closed-won deal
You, in CodexWith Sprites, what did each closed-won deal cost us this quarter, by campaign?
- Sprites does
- Groups closed-won deals by lead source and campaign in Zoho, then reads spend for the same period from the ad accounts.
- You get back
- One table of cost per deal by campaign, and the budget changes it suggests as approval cards.
Event list to CRM
You, in CodexAsk Sprites to add these event sign-ups to Zoho as leads.
- Sprites does
- Reads the list, checks your Lead_Source picklist, and matches each row on email against existing leads and contacts.
- You get back
- One approval showing new versus updated records; the batch is written only when you approve.
Monday pipeline
You, in CodexEvery Monday, have Sprites summarize open Zoho deals by stage and owner.
- Sprites does
- Runs Zoho aggregate queries for open deals by stage and owner on a schedule.
- You get back
- A short pipeline read in your thread each week, with stalled deals named.
What Codex can do with Zoho CRM
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.
Ad spend and closed-won in one answer
Zoho CRM sits beside Google Ads, Meta and LinkedIn in the same conversation, so "which campaigns produced revenue" is read from the ad accounts and the CRM together rather than from two exports and a spreadsheet.
Totals Zoho computes, not the model
Counts and sums come from Zoho’s own aggregate queries, grouped by stage, owner or lead source. The agent reads your field names and picklist values first, so a renamed stage or a custom field does not break the report.
Leads in from a campaign list
Hand over a form export or an event list and Sprites creates or updates up to 50 leads or contacts per call, matched on email, so a known person is updated rather than duplicated.
Deal updates you approve on a card
Stage, amount, closing date, owner or next step — only the fields you name change, the card shows before and after, and the deal is read back afterwards to confirm the write landed.
Notes where the context belongs
A call summary or the campaign a lead came from, written as a note on the lead, contact, account or deal it belongs to — approved first, then read back.
Nothing can be deleted
The connection is granted no delete permission. Ask to remove records and Sprites finds them and hands you their Zoho links to delete yourself.
How approvals work here
Codex renders tool results as text, so a Zoho CRM 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
- Leads, contacts, accounts and deals, including custom modules
- Campaigns, lead sources and deal stages, with your own field names and picklist values
- Users, for resolving owners to names
- Aggregate counts and sums by stage, owner, lead source or campaign
What it can change
- Leads and contacts, created or updated — up to 50 per call, matched on email
- One deal at a time: stage, amount, closing date, owner or next step
- Notes on a lead, contact, account or deal
- Every write is an approval card first, and is read back after
- Nothing is deleted: the connection has no delete permission
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.
And on the Zoho CRM side
Sprites says a field or stage does not exist.
Zoho orgs rename stages and add custom fields. Sprites reads your field names and picklist values before writing; if a value was just added in Zoho, ask again and it will be picked up.
Deals do not show which campaign they came from.
Attribution reads the Lead_Source and campaign fields on your Zoho records. If leads arrive without them, the report can only group by what is there; set the source when leads are created and the next report can use it.
A record I just created is not found.
Zoho search lags recent changes. Sprites falls back to a direct query, so a brand-new record is usually found on the second ask.
Zoho says the connection needs to be reauthorized.
Reconnect Zoho CRM on the Sprites integrations page, then ask again. Zoho revokes older connections once a user has too many, so a connection made long ago can lapse.
Zoho CRM 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 Zoho CRM account without asking?
Codex renders tool results as text, so a Zoho CRM 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 Zoho CRM API key or developer token?
No. Zoho CRM is connected once inside Sprites through Zoho CRM (Zoho OAuth, any Zoho data center), and the connector acts on that connection. Codex never sees a credential for it.
Why Codex for Zoho CRM 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.
Is there an official Zoho MCP server?
Yes, in early access. Zoho announced Zoho MCP in July 2025, and it offers four servers for Zoho CRM: Data Insights (read-only), Data Operations (create, update and delete records), Modules (fields and layouts) and Workflow & Automation. Agents sign in with Zoho OAuth and inherit your permissions. Sprites is a separate MCP server that reads Zoho CRM beside your ad accounts and holds every CRM write for approval.
Which Sprites plan includes Zoho CRM?
The pricing page lists CRM integration, covering Zoho CRM, HubSpot, Salesforce and Pipedrive, as a Scale plan feature. The MCP server itself comes with every paid plan.
Keep going
The same Codex connector reaches every other channel — nothing else to add.
Zoho CRM, from Codex
Paste one URL, sign in once, and the next Zoho CRM question you ask Codex gets answered from the live account.