Let Codex work across code and email. One MCP block, then browser authorization.
Give Codex live tools for contacts, templates, lifecycle flows, and delivery evidence while it reads the product code that produces the events.
✓Configure the remote endpoint in TOML. OAuth keeps credentials out of the repository.
Start with a read-only task
Operator prompt
Inspect the onboarding flow, explain where contacts stop, and show the evidence before proposing a change.
Connect
Remote MCP
Prompt
Inspect the live system
Boundary
Show before changing
[ 01 / 03 ]Repository to runtime
Let Codex verify both sides of the integration.
Match events to flows
Compare product event names in the repository with triggers and runs in the live email system.
Implement and prepare together
Update application code, then prepare the corresponding template or paused flow in the same task.
Keep deployment separate from activation
Codex can prepare the product and email changes, while consequential email actions retain explicit confirmation.
[ 02 / 03 ]Connect
Start Codex with a task you can verify.
Add one MCP server block to Codex configuration, authorize the selected project in the browser, and verify the connection with a read-only task.
Authorize in the browser, then begin with a read-only comparison task.
[mcp_servers.sendandretain]
type = "http"
url = "https://sendandretain.com/api/mcp"[ 03 / 03 ]Related
Build around Codex
Questions people ask us
Give Codex the runtime context behind the code.
Add one MCP block, compare product events with live flows, and prepare a traceable change.