listmonk-mcp
Related Servers
Alternatives to listmonk-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables 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
- AlicenseBqualityBmaintenanceEnables 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.72121 npm1MIT
- FlicenseDqualityBmaintenanceEnables AI agents to manage Listmonk email campaigns, subscribers, lists, and analytics through typed MCP tools with production safety features.37322 PyPI2-
- AlicenseBqualityBmaintenanceEnables Claude and other MCP clients to manage an addy.io account through the full addy.io API, covering alias creation and bulk actions, recipients, usernames, custom domains, labels, rules, the blocklist and failed deliveries. Runs locally with your own API key, with an optional read-only mode that hides every tool that can change the account.6266 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude to manage a self-hosted PocketBase instance: querying and editing records, inspecting and changing collection schemas, handling files, users and backups, and auditing API rules for exposure risks. Writes are gated by a read-only mode plus a two-step confirmation that returns a preview diff and single-use token, so nothing changes until the identical call is approved.18 npmMIT
- AlicenseBqualityCmaintenanceEnables Claude and other MCP clients to work with SendPulse WhatsApp chatbots, reading bots, contacts, chats, tags and variables, and sending messages, approved templates, flows and campaigns. Supports multiple SendPulse accounts and an optional read-only mode that exposes only the 10 read tools.26MIT
TDQS
Scored across 32 tools
Tools are organized around distinct resources and actions, so most selections are clear. A few areas could be confused, such as subscriber_update versus subscribers_lists_change and the several email-sending tools, but their descriptions make the intended use distinguishable.
Names are consistently snake_case and mostly follow a resource_action pattern, with plural collection names like subscribers_search and singular record names like subscriber_get. Minor deviations exist, including the listmonk_ prefix for system tools and mixed collection verbs such as list versus search.
32 tools is heavy for an MCP surface, even though Listmonk is a broad domain with multiple CRUD-managed resources. Most tools map to real operations, but the count is borderline and could overwhelm agents selecting among many similar resource actions.
Core lifecycle coverage is strong across lists, subscribers, campaigns, templates, bounces, and system diagnostics. Minor gaps remain, such as no settings update, subscriber import/export, campaign preview beyond campaign_get, and media management.