Get started free
All integrations

listmonk integration

listmonk is a self-hosted newsletter and mailing-list manager. This integration covers its admin API: create, read, update, delete and query subscribers with SQL-style filters, add or remove them from lists in bulk or by query, blocklist them, send a double opt-in confirmation, read and delete their bounces, export one subscriber's stored data, manage lists, import subscribers from a file and follow the import log, create campaigns with their content, preview, test-send, schedule, start, pause or cancel them and read running and archived analytics, send a one-off transactional message rendered from a template, manage templates and set the default, upload and delete media, read server settings, logs and dashboard counts and charts, run the maintenance clean-ups, and read the public lists a subscription form offers. The host is part of the credential because every listmonk install is its own deployment. Authentication is an API user and its token, sent either as HTTP basic auth or as an Authorization header of the form 'token user:token'.

66 toolsBasic authAPI docs

What you can do with listmonk

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Subscriber, 10 operations

  • POSTcreate_subscriber

    handles creation of new subscriber.

  • DELETEdelete_orphan_subscribers

    garbage collects (deletes) orphaned or blocklisted subscribers.

  • DELETEdelete_subscriber

    handles subscriber deletion based on id.

  • DELETEdelete_subscribers

    handles subscribers deletion.

  • GETget_import_status

    returns import status.

  • GETget_subscriber

    handles the retrieval of a single subscriber by ID.

  • POSTimport_subscribers

    handles the uploading and bulk importing of a ZIP file of one or more CSV files.

  • GETlist_subscribers

    returns all subscribers.

  • DELETEstop_import_subscribers

    sends a stop signal to the importer.

  • PUTupdate_subscriber

    modify subscriber data.

List, 9 operations

  • POSTcreate_list

    handles list creation.

  • DELETEdelete_list

    handles list deletion, either a single one (ID in the URI), or a list.

  • GETget_list

    retrieves lists with additional metadata like subscriber counts. This may be slow.

  • GETlist_lists

    retrieves lists with additional metadata like subscriber counts. This may be slow.

  • GETlist_public_lists

    returns the list of public lists with minimal fields.

  • PUTmanage_subscriber_lists

    handles bulk addition or removal of subscribers.

  • PUTmanage_subscriber_lists_by_query

    bulk adds/removes/unsubscribes subscribers from one or more lists based on an arbitrary SQL expression.

  • PUTmanage_subscribers_of_list

    handles bulk addition or removal of subscribers for a specified list id.

  • PUTupdate_list

    handles list modification.

Bounce, 6 operations

  • DELETEdelete_bounce

    handles bounce deletion, either a single one (ID in the URI), or a list.

  • DELETEdelete_bounces

    handles deletion of bounce records.

  • DELETEdelete_subscriber_bounces

    deletes a subscriber's bounce records.

  • GETget_bounce

    handles retrieval of bounce record by id.

  • GETlist_bounces

    handles retrieval of bounce records.

  • GETlist_subscriber_bounces

    retrieves a subscriber's bounce records.

Campaign, 5 operations

  • POSTcreate_campaign

    handles campaign creation.

  • DELETEdelete_campaign

    deletes specified campaign.

  • GETget_campaign

    handles retrieval of campaigns.

  • GETlist_campaigns

    handles retrieval of campaigns.

  • PUTupdate_campaign

    handle updation of campaign.

Template, 5 operations

  • POSTcreate_template

    handles template creation.

  • DELETEdelete_template

    handles deletion of templates.

  • GETget_template

    handles retrieval of templates.

  • GETlist_templates

    handles retrieval of templates.

  • PUTupdate_template

    handles template modification.

Media, 4 operations

  • DELETEdelete_media

    handles deletion of uploaded media.

  • GETget_media

    handles retrieval of uploaded media.

  • GETlist_media

    handles retrieval of uploaded media.

  • POSTupload_media

    handles media file uploads.

Blocklist, 3 operations

  • PUTblocklist_subscriber

    handles the blocklisting of one or more subscribers.

  • PUTblocklist_subscribers

    handles blocklisting of subscriber list.

  • PUTblocklist_subscribers_by_query

    bulk blocklists subscribers based on an arbitrary SQL expression.

Analytic, 2 operations

  • DELETEdelete_campaign_analytics

    garbage collects (deletes) campaign analytics.

  • GETget_campaign_analytics

    retrieves view counts for a campaign.

Log, 2 operations

  • GETget_import_logs

    returns import logs from an ongoing import.

  • GETlist_logs

    returns the log entries stored in the log buffer.

Setting, 2 operations

  • GETget_settings

    returns settings from DB.

  • PUTupdate_settings

    returns updated settings from the DB.

Test, 2 operations

  • POSTsend_campaign_test

    handles sending of campaign message to arbitrary subscribers for testing.

  • POSTtest_smtp_settings

    test smtp settings.

Archive, 1 operation

  • PUTset_campaign_archive

    handles campaign status modification.

Chart, 1 operation

  • GETget_dashboard_charts

    returns chart data points to render on the dashboard.

Config, 1 operation

  • GETget_server_config

    returns general server config.

Content, 1 operation

  • POSTconvert_campaign_content

    handles campaign content (body) format conversions.

Count, 1 operation

  • GETget_dashboard_counts

    returns stats counts to show on the dashboard.

Default, 1 operation

  • PUTset_default_template

    handles template modification.

Delete, 1 operation

  • POSTdelete_subscribers_by_query

    bulk deletes based on an arbitrary SQL expression.

Export, 1 operation

  • GETexport_subscriber_data

    retrieves a subscriber's profile.

Health, 1 operation

  • GETget_health

    healthcheck endpoint.

Lang, 1 operation

  • GETget_language_pack

    returns the JSON language pack given the language code.

Optin, 1 operation

  • POSTsend_subscriber_optin

    sends an optin confirmation e-mail to a subscriber.

Stat, 1 operation

  • GETget_running_campaign_stats

    returns stats of a given set of campaign IDs.

Statu, 1 operation

  • PUTset_campaign_status

    handles campaign status modification.

Subscription, 1 operation

  • POSTcreate_public_subscription

    handles subscription requests coming from public API calls.

Tx, 1 operation

  • POSTsend_transactional_message

    send message to a subscriber.

Unconfirmed, 1 operation

  • DELETEdelete_unconfirmed_subscriptions

    garbage collects (deletes) orphaned or blocklisted subscribers.

Use listmonk from Claude Code, Cursor or Codex

Connect listmonk in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its listmonk operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect listmonk

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect listmonk once

    Add your listmonk connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

listmonk integration FAQ

What can you do with the listmonk integration?
LiveContext exposes 66 operations on listmonk, covering subscriber, list, bounce and campaign.

Popular integrations

Browse the whole catalog