Codex · MCP install
Add the Latten MCP server, then hand Codex one task. You approve one connect link; Codex does the rest — scans your TypeScript app, opens a reviewable PR, and comes back with a receipt: what your AI costs, where your private data flows, and confirmation that only types and counts — never PII values — crossed the wire.
1. Add Latten to Codex.
Put this in ~/.codex/config.toml. No token is needed up front: Codex calls provision once if this repo does not already have one, and hands you a connect link to approve — that click is your whole job.
[mcp_servers.latten]
command = "npx"
args = ["-y", "@latten/installer"]
env = { LATTEN_URL = "https://latten.io" }
2. Give Codex the task.
Use the Latten MCP. If there is no LATTEN_TOKEN, call provision once — it returns a connect link; show it to me, I approve in the browser, then poll provision with the device_code for the token. Then read guide, scan this repo, instrument high-confidence TypeScript crossings with @latten/sdk, open a reviewable PR, verify real crossings, and return the receipt.
Free
The first receipt.
One free-account approval, first crossing, and a trust receipt — never a card. Your headline numbers stay free forever.
First week
Everything open.
Starts at your first crossing: the full graph, every finding, real traffic — all open for a week.
Solo
The fix loop.
The full graph, every finding ranked by $, traces, fix prompts, and verified savings.