Skip to main content
Glama
mnbro

listmonk-mcp-bridge

by mnbro

Related Servers

Alternatives to listmonk-mcp-bridge

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      86 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An 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.
      43
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to manage mailing lists and contacts, read campaign reports with per-link clicks, and trigger automations. Supports lookups and updates by email address, tag and status management, and destructive operations with client confirmation.
      13
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with Mailjet's contact, campaign, segmentation, statistics, and workflow APIs for managing email marketing operations through natural language.
      133 npm
      13
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to connect and warm up sending mailboxes, build and launch outbound campaigns, manage leads and replies, and handle suppressions, analytics, and webhooks through policy-gated MCP tools.
      3
      Apache 2.0

    TDQS

    D1.5/5.0

    Scored across 37 tools

    Disambiguation2/5

    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.

    Naming Consistency3/5

    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.

    Tool Count2/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive