Codex
The data chores, done and reported. You approve the send.
Codex works on your project through the MCP server while it handles the rest of the task: it counts, audits and checks the data, writes the import against the API and reports back with the real figures. What it prepares stays ready for you; sending waits for your approval.
Codex, working on a real project
Connect Codex to your project
The fast way. Paste this prompt into Codex and it does the three steps for you.
Or do it by hand:
- 1
Add the server
In the Codex CLI, run codex mcp add instasent --url followed by Instasent's server address. In the IDE extension, it is the gear menu → MCP servers → Add server; in the app, Settings → MCP servers.
- 2
Sign in
Run codex mcp login instasent. Codex opens Instasent in your browser: sign in, pick the project and the permissions it gets. The connection is listed under Connected apps, and you can revoke it any time.
- 3
Check it
Ask it to count your contacts. If the figure matches your project, you are connected.
What to ask Codex
- Audit my audience: duplicated phones, empty attributes and contacts without consent.
- Write the script that imports last night's orders as events, run it and tell me how many made it.
- Check that the new signup field arrives as an attribute and build a segment with it.
- Leave me a report of the week's campaigns as a Markdown file in the repo.
What Codex will not do on its own
- It reads everything.
- Audience, campaigns, flows and results of the project you connect.
- It creates and leaves it ready.
- Contacts, segments and campaign drafts, prepared for you to review.
- It never sends.
- Sending waits for your approval, every time. No agent sends on its own.