Give OpenAI Codex a real
data layer
Connect Codex to Improvado and your coding assistant gets clean spend, attribution, and CAC data - plus the shared memory your whole team already uses.
Which channels are over CAC?
df = mcp.query("spend, cac by channel", window="last_30d")
df.plot.bar(x="channel", y="spend")
| job | schedule | last run | status |
|---|---|---|---|
| attribution_export.py | Daily 06:00 | 06:02 UTC | success |
| cac_alert.py | Every 4h | 2h ago | success |
| weekly_board_pack.py | Mon 07:00 | 3 days ago | success |
| anomaly_scan.py | Hourly | 18 min ago | retried x1 |
| creative_fatigue_scan.py | Daily 05:30 | 5h ago | success |
| budget_pacing_check.py | Every 6h | 1h ago | success |








From question to scheduled report in three steps
Connect once, ask in plain English, and put the answer on autopilot - no setup project and no query language to learn.
Connect
Connect Improvado to Codex once - set up at onboarding, nothing to install.
Set up once at onboarding - nothing for your team to install or maintain.
Ask anything
Ask about spend, CAC, LTV, or attribution across every connected source and get the answer in seconds - in plain numbers, not a query language.
412 ms median answer · every number source-cited · saved to shared memory
Schedule it
Turn any answer into a report that runs on a schedule and lands where your team needs it - nobody has to remember to pull it.
Runs on a schedule and saves the results.
See the technical setupThe exact commands, queries & scheduling - for your engineers and AI agents
# 1 - Show setup command
{ "mcpServers": {
"improvado": { "url": "https://mcp.improvado.io/v1" }
} }
✓ oauth: authenticated as growth@acme.com
✓ scopes: read:spend · read:crm · write:memory
# 2 - See the notebook cell
In [1]: mcp.query("blended CAC by channel, 30d")
Out[1]: google_ads $XXX -7% vs target
meta_ads $XXX +3% vs target
tiktok_ads $XXX +23.7% flagged
# 3 - See the scheduled job
cron: "0 6 * * *" cac_alert.py
today success · 412 ms · 3 flags → knowledge graph
yesterday success · 398 ms · 0 flags
Mon success · 405 ms · 1 flagPick a workflow, see the live board
Live boards from your connected data - pick a workflow to see what your team gets.
last 30 days
last 30 days
last 24 hours
last 7 days
See the queries behind these boardsThe exact query each workflow runs - for your engineers and AI agents
Clean marketing data, ready the moment you ask
Codex is only as good as the data it can reach. Improvado hands it the same clean, governed data your whole team already trusts.
All your channels in one ask
Every connected source in seconds - one clean set of numbers, nothing to wire up.
Shared memory with your team
The same shared memory Claude and your team use - context carries across every tool.
Enterprise security
SOC 2 Type II, GDPR-ready, role-based access and audit logs - no credentials anywhere.
Works wherever your team works
Use Codex however your team already does - the connection follows wherever it runs.
One clean format
Every channel arrives in one format - what works for Google Ads works for Meta and TikTok too.
Always up to date
Metrics are live - what Codex reads is exactly what your dashboards show.
See the technical detailsHow Codex reads each capability - for your engineers and AI agents
spend↦google_ads.costspend↦meta.spendMinutes to your first answer, not a data project
Connect once and Codex queries your live marketing data the same day - no data project, no integration backlog, no waiting on your data team.
Ask on day one. The data-engineering project that used to sit between you and an answer is already done.
Every ad platform, your CRM, and your warehouse arrive as one clean set of numbers - not 500 exports to reconcile.
Governed access and one clean, consistent data source mean Codex's answer matches what your BI team would hand you.
See the full technical comparisonHow this compares to wiring up each platform yourself
| Dimension | Raw platform APIs | With Improvado MCP |
|---|---|---|
| Auth | -One credential per platform | +One OAuth connection |
| Schema | -Drifts per source, per version | +One normalized schema |
| Memory | -None - re-explain context every session | +Shared knowledge graph |
| Credentials | -API keys pasted into prompts | +Zero credentials leave the endpoint |
| Rate limits | -Per-API, hit blind | +Governed layer, one budget |
| Time to first query | -Weeks of glue code | +Minutes, one config block |
| Dependency | -N direct integrations you maintain and control | +One governed endpoint - a single vendor dependency, by design |
One governed layer between Codex and your entire stack
Switch AI tools whenever you want. Your data, your access rules, and everything your team has taught the system stay exactly where they are - nothing to reconnect, nothing relearned.
Switch agents. Keep your data. Keep your memory
For engineers & AI agentsThe MCP contract, endpoints, and how memory persists across agents
# 1 - One connection, declared once
{
"mcpServers": {
"improvado": {
"url": "https://mcp.improvado.io/v1",
"auth": "oauth"
}
}
}
# 2 - Scopes - role-based, read-only by default
# read:spend
# read:crm
# read:attribution
# write:memory
# 3 - Shared memory - survives an agent switch
persisted in the governed knowledge graph · versioned · every agent (Claude, Codex, custom) reads the same nodesAgent access your security team will actually approve
SOC 2 Type II · HIPAA · GDPR/CCPA · 6/6 controls green, audited quarterly · every query logged, zero raw credentials.
For engineers & AI agentsThe live compliance audit - every control, cycle date, and scope
Improvado powers our data views every single day. It's a pulse check on business performance that enables our clients to make smarter, strategic decisions on budgeting, sales forecasting, and assess marketing's impact on their businesses.
Common questions
Q01Does Codex support MCP?
Q02Can Codex and Claude share context?
Q03Can Codex schedule recurring jobs against the data?
Q04Is my data safe?
Q05What is MCP?
Q06How long does setup take?
Give Codex a real measurement foundation
Bring your own stack - we'll show your pipeline, attribution, and Codex querying it live, in twenty minutes.