Your revenue data, inside Codex
Kometrics in Codex, in two terminal lines.
Add Kometrics to Codex
https://app.kometrics.com/mcpcodex mcp add kometrics --url https://app.kometrics.com/mcp codex mcp login kometrics
The second line opens the browser for the approval screen, where you pick the workspace.
Codex manages MCP servers from the command line. Two lines put Kometrics in: one to add the endpoint, one to sign in, and the second opens a browser for the same approval screen every other client uses.
The workspace is chosen on that screen and remembered for Codex, so nothing has to be passed on the command line and no credential ends up in a dotfile. If you need a client that cannot open a browser at all, a workspace API key sent as a bearer token works instead.
Read only, and scoped to one workspace in code rather than by instruction, so nothing typed into a session can widen what it is allowed to see.
What it is good for
- Reading the revenue side of a change you are about to make
- Scripting a report against real figures, in the same session
- Keeping metrics one question away while you work
Ask it this
Break last month into new business, expansion, contraction and churn.
Which customers renew in the next 30 days?
Show MRR by month for the last year.
The nine tools it gets
Every client reaches the same read-only tools, run by the same code as the reports.
Metric series for MRR, ARR, churn, LTV, ARPA and the rest, at any granularity
The movement list behind a month: new business, expansion, contraction, churn, reactivation
Customer search and the full detail of any one of them
Cohort retention by signup month
A forecast baseline from the trailing months
Past due and dunning, with the MRR each customer carries
Risk radar, and the renewals the next weeks bring
Connect your billing, then connect Codex
Stripe, Paddle, Creem and Asaas, backfilled into one ledger. Free while you are under $1,000 MRR.