Mailcoach now has a hosted MCP server. You can connect AI assistants such as Claude and let them inspect lists, look up subscribers, check campaign stats, and prepare drafts in Mailcoach.
The MCP server is available at:
https://mcp.mailcoach.app
With the Mailcoach CLI, we made it easier for agents and scripts to use Mailcoach from the command line. The MCP server takes that idea one step further: your assistant can use Mailcoach directly, without copying subscriber counts, campaign stats, or draft content between tools.
What you can ask #
Once connected, your assistant can answer questions about your audience and help prepare campaigns.
For example, you can ask:
- “How many subscribers does this list have?”
- “Show me the recent stats for our latest campaign.”
- “Find this subscriber and show me which list they belong to.”
- “Prepare a draft campaign from this outline.”
- “Send a test email for this campaign.”
By default, the MCP server can read the Mailcoach data your account may view. With write access enabled, it can also:
- create and update draft campaigns
- create and update campaign templates
- send campaign test emails
It does not expose a tool that sends a campaign to your full audience.
You stay in control #
Connecting an assistant uses OAuth. When you approve the connection, Mailcoach asks which teams the assistant may access.
Read access is granted by default. Write access is optional, so you can decide whether an assistant is allowed to create or update drafts and templates.
All MCP results are filtered through your existing Mailcoach permissions. If your account cannot view or change something in Mailcoach, your assistant cannot access it through MCP either.
You can revoke connected assistants at any time from Account settings > AI Assistants.
Getting started #
In Claude.ai, add Mailcoach as a custom connector and use https://mcp.mailcoach.app
as the server URL.
If you use Claude Code, you can add Mailcoach with:
claude mcp add --transport http mailcoach https://mcp.mailcoach.app
Other MCP clients can connect to the same server URL. Some desktop clients may need mcp-remote
for remote HTTP MCP servers.
You’ll find the full setup guide in the Mailcoach MCP server docs.
Self-hosted Mailcoach users can also expose their own MCP server. The setup instructions are in the self-hosted MCP server documentation.