listmonk-mcp-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LISTMONK_MCP_URL | Yes | The base URL of the Listmonk instance, e.g. https://listmonk.example.com | |
| LISTMONK_MCP_PASSWORD | Yes | The API token or password for Listmonk authentication | |
| LISTMONK_MCP_USERNAME | Yes | The API username for Listmonk authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| inspect_listmonk_audience | |
| create_campaign_safely | |
| send_campaign_safely | |
| import_subscribers_safely | |
| review_campaign_performance | |
| debug_listmonk_connection |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| list_mailing_lists | |
| health_resource | |
| capabilities_resource | |
| campaigns_summary_resource | |
| templates_summary_resource |
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.