Listmonk MCP Server

Created By
ngomis-coma year ago
Listmonk-MCP server is used as MCP server to use your Listmonk server.
Overview

What is Listmonk MCP Server?

Listmonk MCP Server is a Model Context Protocol (MCP) server that facilitates interaction with a Listmonk instance, allowing users to manage mailing lists, subscribers, and campaigns through an MCP interface.

How to use Listmonk MCP Server?

To use the Listmonk MCP Server, set up a running Listmonk instance, clone the repository, configure environment variables, and run the server to handle MCP requests.

Key features of Listmonk MCP Server?

  • Integrates Listmonk with MCP-compatible clients like Cline.
  • Automates email marketing tasks such as managing subscribers and campaigns.
  • Provides centralized management of Listmonk resources through MCP tools.

Use cases of Listmonk MCP Server?

  1. Managing mailing lists and subscribers efficiently.
  2. Automating email marketing campaigns.
  3. Integrating Listmonk with other tools and services.

FAQ from Listmonk MCP Server?

  • What is required to run the Listmonk MCP Server?

    A running Listmonk instance and Python 3.x are required.

  • Can I automate tasks with Listmonk MCP Server?

    Yes! You can script and automate common Listmonk operations.

  • Is there documentation available for Listmonk MCP Server?

    Yes, detailed documentation is provided in the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ngomis-com
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago