listmonk-mcp-bridge
Related Servers
Alternatives to listmonk-mcp-bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible LLM clients to manage a Listmonk instance end-to-end through its full REST API, covering subscribers, campaigns, lists, templates, media, bounces, imports, settings, transactional messages, and admin functions, with selective tool loading for a leaner context.33 npm1MIT
- AlicenseNot gradedqualityCmaintenanceAn 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.39MIT

Mailjet MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceEnables AI agents to interact with Mailjet's contact, campaign, segmentation, statistics, and workflow APIs for managing email marketing operations through natural language.80 npm11Apache 2.0
Sequenzy MCP Serverofficial
AlicenseBqualityCmaintenanceEnables management of AI-powered email marketing automation, including subscriber segments, campaigns, and templates. It allows users to generate email sequences with AI and track detailed analytics through natural language commands.1001,310 npm2MIT- FlicenseNot gradedqualityCmaintenanceEnables AI agents to programmatically manage email outreach campaigns, leads, domains, senders, and webhook events, as well as send emails, through the Model Context Protocol over HTTP.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage email newsletters and contacts via Resend, including sending broadcasts to segments, managing subscribers in bulk, scheduling campaigns, and tracking delivery status using human-friendly identifiers.17,286 npm5MIT
TDQS
Scored across 37 tools
Many tools have overlapping purposes, especially around subscriber import (e.g., safe_add_subscriber, safe_bulk_add_subscribers, validate_subscriber_import, prepare_subscriber_import, safe_import_subscribers, import_status_summary) and campaigns (e.g., safe_create_campaign_draft, safe_update_campaign_content, safe_send_campaign, safe_schedule_campaign, safe_test_campaign, campaign_performance_summary). The boundaries between these tools are unclear, making it difficult for an agent to distinguish when to use which.
Tool names are all in snake_case and many use a verb_prefix pattern, but the prefixes are inconsistent. For example, some use 'safe_', others 'get_', 'export_', 'validate_', etc. There is no uniform convention for indicating the action or resource, and some names like 'audience_catalog' or 'campaign_catalog' are vague.
With 37 tools, the server feels bloated. The number is high for the likely domain scope (email marketing via Listmonk). Many tools could be merged or removed, such as the several subscriber import-related tools or the multiple campaign export tools.
The tool set covers a wide range of operations: health, diagnostics, subscribers (add, import, assign, opt-in), campaigns (create, update, send, schedule, test, preview, performance), templates, and exports. However, there are notable gaps: no tools for deleting campaigns, subscribers, or lists; no update for individual subscriber profile beyond upsert; no template creation or update. This leaves dead ends in common workflows.