Connect OpenAI Codex CLI to Nitrosend with remote MCP. Your email stack lives next to your code, so the same agent that ships the feature can wire the emails, on-brand, without a separate design pass.
Run codex mcp add nitrosend --url https://api.nitrosend.com/mcp in your terminal.
Run codex mcp login nitrosend. Codex opens the Nitrosend sign-in flow in your browser.
Tell Codex what emails your app needs. It reads your code, understands your users, and builds the campaigns.
Pick the surface that fits how you're building with Codex.
Give Codex access to the Nitrosend MCP surface - campaigns, flows, contacts, analytics, Brand Kit, and deliverability.
Call the REST API directly, or use the typed Node SDK, for transactional sends and programmatic control.
Drive Nitrosend from your terminal or CI - sign in once, then run MCP tools as commands.
"Use Nitrosend REST/SDK to set up transactional emails for signup confirmation, password reset, and invoice receipt. Reference my User model for the fields."
"Use Nitrosend to build a 5-email onboarding series based on our app's key features. Space them out over 14 days."
"Use Nitrosend to import our contacts from the Mailchimp export in /data/contacts.csv and recreate our existing segments."
"Use Nitrosend to check our email deliverability. Are SPF, DKIM, and DMARC configured correctly? What's our bounce rate?"
"Use Nitrosend to pull the last 10 campaigns and correlate performance with subject line length and send time."
"Use Nitrosend to replace our old Mailgun transactional code. Wire up the equivalent Nitrosend calls and keep the same template variables."
Transactional and marketing on one platform. Separated sending reputations. No second provider.
Nitrosend's Brand Kit learns your colors, fonts and tone from your own site once. Every email Codex drafts already looks and sounds like your product, no separate design step.
Codex reads your models, routes, user flows. Your emails match what your product actually does.
Use your own sending infrastructure and AI keys, or use Nitrosend managed.
Because Codex is already writing the code that sends your mail, it helps that the MCP tools and your application hit the same email API. The agent can scaffold the integration and then exercise it. For build steps and one-off sends outside an agent session, the command line interface does the same work.
The connection is not exclusive to Codex. The same MCP server is used from Windsurf, from ChatGPT, and from Claude Code. Every supported client is listed on the integrations page.
Hand-templating a transactional email is a 2010s problem when the same agent that wrote the endpoint can also write and send the email. That is the honest case for Codex specifically, and it is why Nitrosend, not a raw SMTP relay, is the best option here: it is built for an agent to run the whole job, composing and branding included.
One MCP connection. Free to start. Send your first campaign in under five minutes.