Integration

AcyMailing integration

AcyMailing is a newsletter and email marketing plugin for WordPress and Joomla. Manage its users (subscribers), lists and subscriptions, send an existing email to one address, create, update, send and delete campaigns, manage email templates, and build follow-up email sequences. Several tools send real emails. Campaign reads, campaign statistics and template updates are not exposed (their answers or parameters are not documented consistently). Authentication: switch the REST API on in AcyMailing's configuration (tab Security), then connect with the site's address and the API key shown there (older versions use the AcyMailing license key), sent in the Api-Key header.

Connect AcyMailing How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in AcyMailing.Built from the 26 AcyMailing tools below, on the connection you add once.

What you can do with AcyMailing

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.

Follow up, 4 operations

create_or_update_follow_upCreate or update follow upPOSTCreates a follow-up (name, display_name and trigger required), an email sequence started by a subscription, birthday, user creation or purchase, or updates the one given by followUpId. Created inactive unless active is 1.
delete_follow_upDelete follow upDELETEDeletes a follow-up.
get_follow_upGet follow upGETReturns one follow-up with its trigger, conditions and emails (mail id, delay and delay unit).
list_follow_upsList follow upsGETLists the follow-ups (automated email sequences), 100 per page by default: name, trigger, conditions, active flag, attached list and last trigger time.

Template, 4 operations

create_templateCreate templatePOSTCreates an email template (editable afterwards only in the standard editor) with its HTML body, default subject, sender, reply-to, headers and preheader. Returns the new templateId.
delete_templateDelete templateDELETEDeletes an email template.
get_templateGet templateGETReturns one email template: name, subject, HTML body, sender and reply-to, stylesheet, headers, preheader, editor type and creation date.
list_templatesList templatesGETLists the email templates, 20 per page by default, optionally searched by name or subject and limited to standard or drag and drop templates.

Campaign, 3 operations

create_or_update_campaignCreate or update campaignPOSTCreates a campaign, or updates the one given by campaignId (it becomes an unsent draft again): subject, body, sender, target lists and sending type. Returns the campaignId; send_campaign sends it.
delete_campaignDelete campaignDELETEDeletes a campaign.
send_campaignSend campaignPOSTQueues a campaign for immediate sending to the subscribers of its lists, whatever its sending type: real emails go out to real people.

Mailing list, 3 operations

create_listCreate listPOSTCreates an AcyMailing list with its name, color, active and visible flags and optional welcome and unsubscribe emails. Returns the new listId.
delete_listDelete listDELETEDeletes an AcyMailing list.
list_listsList listsGETLists the AcyMailing lists, 100 per page by default, optionally filtered by id, name or active status: name, color, visibility, welcome and unsubscribe email ids and creation date.

Subscriber, 3 operations

create_or_update_userCreate or update userPOSTCreates an AcyMailing user, or updates the one with this email. Sends email: a new user gets the confirmation email unless sendConf is false, and automations or follow-ups start unless triggers is false.
delete_userDelete userDELETEDeletes an AcyMailing user, given its email address or its id.
list_usersList usersGETLists AcyMailing users (subscribers), 100 per page by default, filtered by id, CMS user id, email, active or confirmed status. Personal data: name, email, confirmation IP and email activity dates.

Subscription, 3 operations

get_user_subscriptionsGet user subscriptionsGETReturns the lists a user is or was subscribed to, each with its name, subscription status (1 subscribed, 0 unsubscribed) and its subscription and unsubscribe dates.
subscribe_usersSubscribe usersPOSTSubscribes existing users (by email) to lists. Sends email: the lists' welcome emails go out unless sendWelcomeEmail is false. Addresses matching no user are skipped and named in errors; it answers 404 when none matches.
unsubscribe_usersUnsubscribe usersPOSTUnsubscribes existing users (by email) from lists. Sends email: the lists' unsubscribe emails go out unless sendUnsubscribeEmail is false. Addresses matching no user are skipped and named in errors; 404 when none matches.

Email, 2 operations

list_emailsList emailsGETLists the emails created in AcyMailing (campaigns, notifications, welcome and unsubscribe emails, automations, follow-ups, templates), filterable by name and type. Each id is an emailId for send_email_to_user.
send_email_to_userSend email to userPOSTSends an existing AcyMailing email (by emailId) to one address, with optional shortcode values: a real email goes out. With autoAddUser=true an unknown address also becomes an AcyMailing user.

Follow up email, 2 operations

attach_email_to_follow_upAttach email to follow upPOSTAdds an email to a follow-up, sent after the given delay once the follow-up starts for a user, or updates one of its emails (mail.id). Returns the mailId.
delete_follow_up_emailDelete follow up emailDELETERemoves an email from a follow-up.

List subscriber, 2 operations

list_list_subscribersList list subscribersGETLists the users subscribed to the given lists, 100 per page by default. Personal data: email, name, confirmation flag and subscription date.
list_list_unsubscribed_usersList list unsubscribed usersGETLists the users who unsubscribed from the given lists, 100 per page by default. Personal data: email, name, confirmation flag and subscription date.

Use AcyMailing from Claude Code, Cursor or Codex

Connect AcyMailing in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its AcyMailing 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 AcyMailing

Create your workspace
Sign up free. Nothing to install.
Connect AcyMailing once
Add your AcyMailing connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
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.