Listmonk MCP Server

What is Listmonk MCP Server?

Listmonk MCP Server is a Model Context Protocol (MCP) server that bridges MCP requests into Listmonk API calls. It allows users of Cline or other MCP-compatible clients to manage Listmonk mailing lists, subscribers, campaigns, templates, bounces, and transactional messages directly through the MCP interface.

How to use Listmonk MCP Server?

Configure the server in your MCP client (e.g., cline_mcp_settings.json) by specifying the command to run the server and environment variables for your Listmonk API endpoint, username, and token. The server uses Python and requires a running Listmonk instance, Python 3.x, and dependencies installed via pip install -r requirements.txt. After setup, invoke MCP tools (e.g., list_subscribers, create_subscriber, get_campaign) from the client.

Key features of Listmonk MCP Server

• Manage subscribers: create, update, delete, blocklist, and manage lists.
• Manage mailing lists: create, update, delete, and list.
• Manage campaigns: create, update, delete, change status, and list.
• Manage templates: create, update, preview, render preview, set default, delete.
• Handle bounces: list, delete individual or multiple bounces.
• Send transactional messages using templates.

Use cases of Listmonk MCP Server

• Integrate Listmonk email marketing into Cline workflows.
• Automate subscriber imports, list management, or campaign launches.
• Check campaign stats and manage bounces programmatically.
• Send transactional emails from an MCP-compatible client.

FAQ from Listmonk MCP Server

What do I need to run Listmonk MCP Server?

A running Listmonk instance, Python 3.x, and API credentials (endpoint, username, token) set as environment variables.

How do I configure the server for my MCP client?

Add an entry in your client’s settings (e.g., cline_mcp_settings.json) with the command python /path/to/main.py and supply LISTMONK_API_ENDPOINT, LISTMONK_API_USER, and LISTMONK_API_TOKEN in the env object.

What Listmonk API operations are supported?

Subscribers (CRUD, blocklist, list management), mailing lists (CRUD), campaigns (CRUD, status change), templates (CRUD, preview, render), bounces (list, delete), and transactional message sending.

How does the server handle authentication?

It reads LISTMONK_API_USER and LISTMONK_API_TOKEN from the environment or a .env file and uses them for authenticated API requests.

What are the main dependencies?

Python packages: requests for API calls, python-dotenv for loading environment variables.