@kieksme/listmonk-mcp
Related Servers
Alternatives to @kieksme/listmonk-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI assistants to manage a self-hosted Listmonk instance, covering subscribers, lists, campaigns, templates, bounces, system diagnostics, and transactional email sending. Ships with an optional read-only mode that registers only the read tools.32MIT
- AlicenseBqualityCmaintenanceEnables managing lists, subscribers, campaigns, templates, bounces and transactional email on a self-hosted Listmonk instance through Claude tools, with an optional read-only mode that limits access to read operations.321MIT
- FlicenseDqualityAmaintenanceEnables AI agents to manage Listmonk email campaigns, subscribers, lists, and analytics through typed MCP tools with production safety features.37224 PyPI2-
- AlicenseAqualityBmaintenanceMCP server for self-hosted Listmonk newsletters: manage subscribers, lists, campaigns, templates (including from local files), media and transactional email. File access is sandboxed to a configured directory.36295 npm1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server implementation that enables AI assistants to interact with Listmonk instances, providing programmatic access to newsletter and mailing list management functionality including subscriber, list, and campaign operations.43MIT
- AlicenseAqualityBmaintenanceMCP server exposing autobrr's full API as tools, enabling LLMs to read and manage filters, indexers, feeds, clients, actions, releases, and system config. It wraps approximately 104 endpoints into 13 resource-scoped tools for comprehensive autobrr instance management.13MIT
TDQS
Scored across 72 tools
Most tools are clearly separated by resource and action, and descriptions explicitly clarify tricky boundaries such as single vs bulk vs query-based operations and saved vs draft previews. A few closely related tools remain, especially campaign preview variants and subscriber-specific vs global bounce deletion, which could cause occasional misselection in such a large set.
Tool names consistently use the listmonk_ prefix, snake_case, and a verb_resource pattern such as listmonk_create_subscriber, listmonk_update_campaign, and listmonk_delete_template. Variations like get/list and manage are semantically motivated and do not break the predictable convention.
The server exposes 72 tools, far above a practical 3-15 range, and many are narrow variants for previews, bulk/query operations, maintenance deletion, and diagnostics. While Listmonk is a broad product, much of this surface could be consolidated to reduce agent overload.
Coverage is extensive across subscribers, campaigns, templates, lists, media, imports, bounces, settings, public subscription endpoints, transactional sending, logs, maintenance, health, and dashboard data. CRUD and lifecycle operations are present throughout, with only negligible possible gaps such as media metadata updates.