Codex CLI + MagicSlides MCPMake a spreadsheet with Codex CLI
Codex CLI can read exported CI results and the test files in your repo, work out which tests fail without code changes, and suggest a likely cause for each. With the MagicSlides MCP server, it saves the report as a spreadsheet the team can triage from.
Set up MagicSlides in Codex CLI (one time)
Two commands: add the server, then log in.
codex mcp add magicslides --url https://www.magicslides.app/api/mcp/mcp
codex mcp login magicslides[mcp_servers.magicslides]
url = "https://www.magicslides.app/api/mcp/mcp"- 1.Run codex mcp add, then codex mcp login and approve in the browser.
- 2.Start codex (or use codex exec "…" for one-off runs).
- 3.Ask for a deck. Codex calls MagicSlides and prints the present link.
Example: what you type in Codex CLI
Read the JUnit reports in ci-results/ for the last 30 days, find tests that failed and passed on the same commit, work out the likely cause from the test code, and save a flaky test report as a MagicSlides sheet.
- Parsed the JUnit XML files in ci-results/ with a short Python script
- Flagged tests that failed and then passed on the same commit
- Read each flaky test file to find a likely cause and fix
- Called create_sheet with 11 rows sorted by failure count
The flaky test report is saved as a MagicSlides sheet with 10 tests. The top two, the discount fixture and the search timing test, cause over half of the 124 flaky failures.
| Test | File | Runs | Failures | Flake rate | First seen failing | Likely cause | Suggested fix | Owner |
| checkout applies discount once | tests/checkout/discount.test.ts | 412 | 31 | 7.5% | 2026-09-28 | Shared cart fixture mutated between tests | Create fixture per test | payments |
| search returns results under 200ms | tests/search/perf.test.ts | 412 | 27 | 6.6% | 2026-09-30 | Timing assertion on shared CI runner | Move to nightly perf job | search |
| webhook retries on 500 | tests/webhooks/retry.test.ts | 412 | 19 | 4.6% | 2026-10-02 | Real timers with 1s backoff | Use fake timers | platform |
| user can reset password | e2e/auth/reset.spec.ts | 205 | 12 | 5.9% | 2026-10-05 | Email stub not awaited | Await mailbox helper | identity |
| export CSV includes all rows | tests/reports/export.test.ts | 412 | 9 | 2.2% | 2026-10-07 | Order of rows not fixed in query | Add ORDER BY id | data |
| cache invalidates on update | tests/cache/invalidate.test.ts | 412 | 8 | 1.9% | 2026-10-09 | Redis container not ready at start | Add readiness wait | platform |
| image upload rejects 20MB file | e2e/media/upload.spec.ts | 205 | 6 | 2.9% | 2026-10-11 | Upload timeout too low on CI | Raise timeout to 30s | media |
This is the real output from that prompt, made with the MagicSlides MCP. Open it to click through or download it.
How it works
- 1.Run codex mcp add magicslides --url https://www.magicslides.app/api/mcp/mcp
- 2.Run codex mcp login magicslides
- 3.Ask Codex to analyse your CI results and save a flaky test report as a MagicSlides sheet
- 4.Schedule it with codex exec in a weekly job if you want a fresh report
Tool used: create_sheet. Prefer a web app? AI spreadsheet generator does the same without an agent.
FAQ
Where does Codex get the test results?
From files in your project, such as exported JUnit reports. Codex CLI reads local files and runs shell commands to parse them.
Can I run this weekly without opening Codex?
Yes. Put the prompt in a codex exec command and run it from a scheduled CI job.
How do teammates open the report?
Share the editor link. It opens in MagicSlides after they sign in.
Does Codex fix the tests too?
It can. Once you pick a row, ask Codex to apply the suggested fix in the repo as a separate step.
More with Codex CLI
Sheets in other agents
Connect MagicSlides to Codex CLI
One MCP server for decks, docs, sheets and reels. Log in with your MagicSlides account, no API key. Making a deck from your own copy uses no AI credits.
