Your campaigns, from the Claude Code session you already have open.
Mailcheer's MCP server connects your workspace to the session you already have open: you ask in plain language, the agent prepares, and it can do nothing you have not allowed.
Read mailcheer.com/claude-code/install and connect Mailcheer for me.What you can ask
Six examples to copy, from the first draft to domain health.
Campaigns
Draft the September newsletter, then check that nothing would stop it from going out.
Read the subject of my latest draft and suggest three shorter ones.
Subscribers
How many active subscribers this month, and where do they come from?
Tag everyone who subscribed this month “september”.
Domain & deliverability
Tell me which of my sending domains are verified, and which address I can send from.
Show me this week's bounces and tell me if I should worry.
Connected in 3 steps
Create a key in your Mailcheer workspace: Settings → API → New key. Tick what it is allowed to do.
Copy the prompt at the top of this page and paste it into Claude Code, with your key. The agent reads the guide and connects itself.
Ask it about your workspace: it answers with its name and your verified domains. You are connected.
What the agent can do
- Read your campaigns, your subscribers and your statistics.
- Create a campaign draft: subject, content, sender.
- Send a single email, if the key carries the “emails:send” right.
- Send a campaign, if the key carries the “campaigns:write” right.
- Watch your deliverability: bounces, complaints, suppression list.
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.
Connection details
| Surface | Hosted MCP server (Streamable HTTP), connected with one command |
|---|---|
| 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 |
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
An address your Claude Code session queries to discover your workspace's tools: read subscribers, create a draft, send. We host it — there is nothing to install or run.
Yes, once. You create it under Settings → API and paste it into the connection command. It is shown only once: we keep a fingerprint, so a stolen database yields no usable key.
Only if you ticked “campaigns:write” on its key. Without that right the sending tool refuses it — and that is the only safeguard that truly holds: you do not rely on its caution, you remove the button. The tool's own description also tells it to ask you first.
One key per workspace. The agent only ever sees the one its key belongs to, and there is no way to switch from the session.
You create another one and revoke the old one. Nobody can give the first one back — not even us.
Your emailing, in the terminal you already have open.
Read mailcheer.com/claude-code/install and connect Mailcheer for me.