Mailmodo MCP Server

Name: Mailmodo MCP Server
Author: mailmodo

@mailmodo

About Mailmodo MCP Server

Mailmodo MCP server to interact with Mailmodo APIs listed here. https://www.mailmodo.com/developers/8e957152b6128-getting-started-with-mailmodo-api

#mailmodo #email #marketing #digital #email-marketing #amp-emails

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mailmodo": {
      "command": "npx",
      "args": [
        "-y",
        "@mailmodo/mcp"
      ],
      "env": {
        "MAILMODO_API_KEY": "<GET MAILMODO KEY from https://manage.mailmodo.com/app/settings/apikey and insert here>"
      }
    }
  }
}

Tools

Tool to get all details of a contact

Tool to get the campaign reports for a particular campaign like open, click submission count etc

Get Current Date and time

Send custom events with email, event name and event properties

Add Contact to list

Add Many Contact to a list in single API

Unsubscribe or supress contact in mailmodo

Resubscribe contact in mailmodo

permanently archive contact in mailmodo

Remove a particular contact from the contact list

Trigger and email for email campaign trigger with personalization parameter added to the email template.

The broadcast campaign API allows the user to trigger campaigns to the entire contact list using a single API request.

Overview

What is Mailmodo MCP Server?

Mailmodo MCP Server is a TypeScript-based server that implements the Model Context Protocol (MCP) for integrating Mailmodo email marketing capabilities with Claude Desktop and other MCP-supported clients. It provides tools and resources to manage campaigns, contacts, templates, and contact lists directly from an AI assistant.

How to use Mailmodo MCP Server?

Clone the repository, install dependencies (npm install), build the TypeScript code (npm run build), and run with npm start. Then configure the server in your Claude Desktop settings using one of four modes: local code path, Docker image (avneesh001/mailmodo-mcp), npx (@mailmodo/mcp), or a remote server (https://mcp.app.mailmodo.com/mcp). All modes require a MAILMODO_API_KEY obtained from Mailmodo's API key settings page.

Key features of Mailmodo MCP Server

Fetch all email templates, campaigns, and contact lists
Retrieve detailed user information by email
Generate campaign reports with open, click, and submission counts
Send custom events with email and event properties
Add, bulk-add, and remove contacts from lists
Unsubscribe, resubscribe, or archive contacts
Trigger personalized or broadcast email campaigns

Use cases of Mailmodo MCP Server

Look up contact details or campaign performance via natural language
Automate adding new subscribers to a Mailmodo contact list
Send triggered email campaigns to individuals or entire lists
Manage contact status (unsubscribe, resubscribe, archive) from chat
Pull campaign reports for analysis without leaving the AI interface

FAQ from Mailmodo MCP Server

What tools does Mailmodo MCP Server provide?

It offers tools for user details, campaign reports, current date/time, sending events, adding/removing contacts to lists, unsubscribing/resubscribing/archiving contacts, sending emails to campaigns, and broadcasting campaigns.

Where does the data live?

All campaign, template, and contact data resides in the Mailmodo platform. The MCP server connects via the Mailmodo API using an API key configured through the MAILMODO_API_KEY environment variable.

What are the runtime requirements?

Node.js version 20 or higher and npm are required. The server can also run as a Docker image or via npx.

What resources does Mailmodo MCP Server expose?

It exposes three resources: mailmodo://templates (list all templates), mailmodo://campaigns (list all campaigns), and mailmodo://contact-lists (list all contact lists), all with MIME type application/json.

How is authentication handled?

Authentication is done through a MAILMODO_API_KEY environment variable that must be set to a valid API key from Mailmodo. For the remote server transport, the API key is passed as a header (mmApiKey).