Mailcoach MCP server

Connect your AI assistant to Mailcoach so it can help with audiences, campaigns, templates, and transactional mail data.

On this page:

Mailcoach has an MCP server that lets AI assistants work with the Mailcoach data you give them access to.

You can use it to inspect your lists and campaigns, look up subscribers, review campaign statistics, work with templates, and prepare draft campaigns without switching back and forth between tools.

The hosted Mailcoach MCP server is available at:

https://mcp.mailcoach.app

Connecting Claude.ai

In Claude.ai, add Mailcoach as a custom connector and use https://mcp.mailcoach.app as the MCP server URL.

Claude will send you to Mailcoach to approve the connection. During approval, choose which teams the assistant may access. You can also choose a default team, which means the assistant will not need to pass a team_id with every request.

Connecting Claude Code

You can add the hosted Mailcoach MCP server to Claude Code with this command:

claude mcp add --transport http mailcoach https://mcp.mailcoach.app

The first time Claude Code uses the server, it will ask you to complete the Mailcoach OAuth flow in your browser.

Connecting desktop clients

Some MCP clients, such as Claude Desktop, Cursor, and VS Code extensions, use a JSON configuration file. If your client does not connect to remote HTTP MCP servers directly yet, you can use mcp-remote.

{
  "mcpServers": {
    "mailcoach": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.mailcoach.app"]
    }
  }
}

After saving the configuration, restart your MCP client and complete the Mailcoach OAuth flow when prompted.

Permissions

When you connect an assistant, Mailcoach asks which teams it may access.

Read access is granted by default. With read access, the assistant can view Mailcoach data that your account is allowed to view.

Write access is optional. If you enable it, the assistant can create and update draft campaigns, create and update campaign templates, and send campaign test emails. The MCP server does not expose a tool that sends a campaign to your full audience.

When you grant access to multiple teams without choosing a default team, the assistant must include a team_id when using Mailcoach tools. Your assistant can first ask Mailcoach for context to see which team it is working with.

What assistants can do

The Mailcoach MCP server exposes tools to:

  • get the current Mailcoach context
  • list email lists
  • list and look up subscribers
  • list and inspect campaigns
  • get campaign statistics
  • list and inspect campaign templates
  • list recent transactional mail log items
  • create and update draft campaigns
  • create and update campaign templates
  • send campaign test emails

All tool results are filtered through your Mailcoach permissions. If your account cannot view or change something in Mailcoach, the assistant cannot access it through MCP either.

Managing connected assistants

You can see and revoke connected assistants in Mailcoach under Account settings > AI Assistants.

Revoking an assistant also revokes the OAuth tokens that were issued for that connection.

Self-hosted

Self-hosted Mailcoach installations can expose their own MCP server. Read the self-hosted MCP server documentation for installation and configuration details.

CLI