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
Draft the autumn offer, then rework it with me before anything goes out.
Before I send this draft, tell me how many people would receive it.
Subscribers
Pull the list of subscribers who unsubscribed this month.
Prepare a welcome note for this month's new subscribers, sent to them alone.
Domain & deliverability
Check that my sending domain is verified before the first send.
Tell me if the last campaign's bounce rate went over 2%.
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.
- Compare your bounces and complaints from one campaign to the next.
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.
- Send a campaign to someone who unsubscribed, or write to an address that 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
On Mailcheer's side, not at all: same MCP server, same key. Only the connection command differs. Use the page for the tool you already work in.
Yes, both. The guide gives the command, and the configuration-file form if your version does not know the subcommand.
Yes: a key created under Settings → API, pasted into the authorisation header. It is shown only once.
Only with “campaigns:write” on its key. A key without it is refused, whatever it is asked.
Every call is logged with its key, time and result. Settings → API shows the number of calls over the last seven days and the most recent emails sent.
Emailing joins your workflow, not the other way round.
Read mailcheer.com/codex/install and connect Mailcheer for me.