Listmonk

You can connect AI-powered tools to Listmonk using the Listmonk MCP Server, which exposes Listmonk operations through a standardized interface. This enables you to manage subscribers, mailing lists, campaigns, templates, and analytics from AI assistants in a safe, typed way.

How to use

Install and run the MCP server, then connect your MCP client using the provided HTTP endpoint or the local stdio runtime. With the HTTP method, you communicate with the remote MCP server via the configured URL and credentials. With the local stdio method, you run the server locally and interact through the command-line entry that starts the MCP service. You can perform common tasks such as adding or updating subscribers, creating or managing lists, launching campaigns, and accessing analytics through the MCP client, without manually composing REST calls.

How to install

Prerequisites: you need Python and the uvx tooling available for your environment, as well as access to a Listmonk instance for MCP integration.

# Prerequisites check (example)
python3 --version
uv --version
pip --version

# Quick install (Python MCP server)
pip install listmonk-mcp
# Or install with uvx
uvx install listmonk-mcp

# Run the MCP server (module entry)
uv run python -m listmonk_mcp.server
# Or use the provided CLI entry point
listmonk-mcp

Configuration and operation notes

Set up Listmonk API access and MCP connection details to enable proper authentication and routing between the MCP server and your Listmonk instance.

Environment variables required to connect to Listmonk from the MCP server:

export LISTMONK_MCP_URL=http://localhost:9000
export LISTMONK_MCP_USERNAME=your-api-username
export LISTMONK_MCP_PASSWORD=your-generated-api-token

Notes:

• The password variable should contain the API token, not a user login password.
• The server uses the token authentication format: Authorization: token username:api_token
• Verify variables by echoing them and test access with a health check endpoint as you configure.

## Troubleshooting and tips

If you encounter connection issues, verify that Listmonk is running and that the MCP URL matches where the MCP server expects to reach Listmonk. Common problems include invalid credentials or incorrect API tokens.

Test connectivity from the MCP host to Listmonk using the configured credentials and the health check endpoint to ensure the token-based authentication works as expected.