Write, test, schedule — without leaving Codex.
Mailcheer's MCP server gives Codex — CLI and app alike — your workspace's tools: emailing fits into your workflow, not the other way round.
Read mailcheer.com/codex/install and connect Mailcheer for me.Connected in 3 steps
Create a key in your Mailcheer workspace: Settings → API → New key.
Copy the prompt at the top of this page into Codex, CLI or app. It reads the guide and adds the server itself.
Ask about your workspace to check: it is a read, nothing is changed.
What you can ask
Six examples to copy, from the first draft to domain health.
Campaigns
Duplicate the April campaign and adapt it to the autumn offer.
Send me a test of this draft and list what feels off.
Subscribers
Pull the list of subscribers inactive for six months.
Prepare a gentle re-engagement note for sign-ups who never opened.
Domain & deliverability
Check that my sending domain is aligned: SPF, DKIM, DMARC.
Flag it if the bounce rate goes over 2% this week.
Connection details
| Surface | Hosted MCP server, connected inside Codex (CLI and app) |
|---|---|
| Connection | API key in a Bearer header, created under Settings → API |
| Scope | One Mailcheer workspace per key, with the rights you tick |
| Revocation | One click under Settings → API, effective on the next call |
What the agent can do
- Read campaigns, subscribers, statistics and the suppression list.
- Create drafts and pick up an existing campaign.
- Send a single email to your own address, to see how it renders.
- Send a campaign, if the key carries the “campaigns:write” right.
- Track your bounces and complaints, and tell you when they drift.
What it cannot do
- Send anything with a key you did not grant sending rights to.
- Send from an address whose domain is not verified in your workspace.
- Write to someone who unsubscribed, or whose address hard-bounced.
- Remove an address from the suppression list — no tool allows it.
- See any workspace other than the one its key belongs to.
Useful access, clear limits
One key, one workspace
Every key belongs to a single Mailcheer workspace. Your other brands or clients stay invisible to the agent, with nothing to configure.
You tick what the key may do
Seven rights, chosen at creation: send emails, read subscribers, change them, read campaigns, send them, read webhooks, manage them. A key without sending rights can never send, whatever the agent is told.
Revoke in one click
One click under Settings → API cuts the key. The next call is refused, and your other keys keep working.
Frequently asked questions
Emailing joins your workflow, not the other way round.
Read mailcheer.com/codex/install and connect Mailcheer for me.