Changelog
Every MailerLite MCP server release: tools added, removed or renamed, tool description and schema changes, and fixes.
Each entry covers one release of the MailerLite MCP server at https://mcp.mailerlite.com/mcp. The server version is ours; the MCP protocol revision is the version of the Model Context Protocol the server speaks. Link to a release by its anchor, for example /mcp/changelog#v4-13-1.
⚠ Breaking marks a change that narrows what a tool accepts — a new required field, a removed enum value, a tighter limit — or removes a tool, or a field clients may rely on in a tool's output. Tool description changes are never marked breaking, but they are always listed: assistants read descriptions to decide how and when to call a tool.
v4.23.0
Nov 11, 2026 · MCP protocol 2026-07-28 (also supports 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release adds tools to build and edit simple-editor emails block by block, and to read brand styles and the media library.
Tools
- Added:
delete_email_block- Remove a block from a simple-editor email, together with any blocks nested inside it. - Added:
get_brand_styles- List every palette a simple-editor email can be styled with: your account’s brand styles (`brand`, null until set), the editor’s `default`, and the built-in `presets`, each a font and colours with … - Added:
get_email- Read a simple-editor email: its content blocks in order (each with an id, type and editor_content) and the design settings applied across the whole email, plus the etag to pass on your next write. - Added:
get_email_block- Read one block of a simple-editor email, with `placement` naming the blocks either side of it. - Added:
get_email_html- Render a simple-editor email to HTML to preview it. - Added:
insert_email_block- Add a content block to the top level of a simple-editor email, at the end unless you pass a placement. - Added:
list_email_versions- List the saved versions of a simple-editor email, newest first. - Added:
list_files- List the images, PDFs and EPUBs in the account’s media library, newest first. - Added:
move_email_block- Move a block among its siblings in a simple-editor email: to the start or end, or before or after a sibling block. - Added:
restore_email_version- Put a simple-editor email back to a saved version, replacing its current content and settings. - Added:
save_email_as_template- Copy a simple-editor campaign email’s content and styles into a new saved template with the given name. - Added:
save_email_version- Save a simple-editor email's current content and settings as a version that can be restored later. - Added:
update_design_settings- Change the styles applied across a simple-editor email: brand palette, layout, typography, button and footer. - Added:
update_email_block- Replace the content of one block in a simple-editor email. editor_content is replaced whole, not merged: read the block with get_email or get_email_block, change what you want, and send the whole r… - Added:
validate_design_settings- Optional dry run: check a change to a simple-editor email's design settings without saving it, sending exactly what you would send to update_design_settings. - Added:
validate_email_block- Optional dry run: check a block against MailerLite's rules without saving anything, sending exactly what you would send to insert_email_block.
Description changes
batch_requests
Execute multiple MailerLite API requests in a single call.
Requests may create, overwrite, or delete account data depending on their HTTP methods.
Maximum 50 requests per batch.
Paths must start with "api/".
Webhooks are not supported in batch requests.
+ Do not edit simple-editor email blocks or settings through batch: use the email tools (insert_email_block, update_email_block, update_design_settings), which handle the etag.cancel_campaign
- Cancel a scheduled campaign
+ Cancel a scheduled campaign.
+ Only a scheduled campaign can be cancelled.
+ It goes back to draft, so its content, including a simple-editor email, can be edited again.create_campaign
Create a new email campaign.
The "from" email must be a verified sender on the account; check Settings > Domains in the MailerLite dashboard if you need to add or verify a sender.
+ To build the email block by block, pass editor: "simple" instead of content: the result has an `email_id` to pass to get_email, get_brand_styles/update_design_settings and insert_email_block.get_automation_email
Read one email step of an automation: subject, preheader, sender, reply-to, internal name, language, open tracking, UTM tags, plain text and HTML.
Works for emails designed in the visual editor and for HTML set via update_automation_email_content.
The HTML is the stored source: merge tags such as {$name} and {$unsubscribe} and conditional blocks are kept as written, so change it with update_automation_email_content edits copied from this HTML, without re-adding them. has_html is false when the email has no body yet: set one with update_automation_email_content.
The plain text can hold click-tracking markers such as {$url}{link-id:123}.
Keep each marker right after its link when you pass the plain text back to update_automation_email.
+ If the email was built in the simple editor, get_email and get_email_html can read it with this email_id, but the editing tools (insert_email_block and others) only change a draft campaign email.update_campaign
Update campaign details.
`name` is optional — if omitted, the campaign's existing name is preserved automatically, so subject/content-only edits don't require knowing or inventing a name.
Only campaigns with status "draft" can be updated.
Omitting `groups` and `segments` leaves existing recipients unchanged.
+ `content` cannot be set on a simple-editor email: edit it with the email tools (insert_email_block, update_email_block) instead.validate_email_content
Validate email content (subject and body) against MailerLite best practices.
Provide the subject and plain_text you have drafted, and this tool will check for issues like subject length, spam trigger words, missing call-to-action, and body length limits.
+ This is an offline copywriting check: it does not call MailerLite or check a simple-editor email (use validate_email_block for that).validate_subject_lines
Validate a list of email subject line candidates against MailerLite best practices.
Provide subject lines you have drafted, and this tool will check each one for length, spam trigger words, and other issues.
+ This is an offline check that does not call MailerLite.Input schema changes
create_campaign·editor- optional property addedcreate_campaign·template_id- optional property added
Output schema changes
create_campaign·email_id- optional property addedcreate_campaign·next_step- optional property added
Annotations
cancel_campaign· destructiveHint false → true
Bug fixes
update_campaignnow returns an error when you setcontenton a simple-editor email. Before, the server ignored the content without an error. Use the email block tools instead.cancel_campaignis now marked as a destructive tool. A cancelled campaign goes back to draft, and you can edit it again.- Email IDs with many digits now work correctly.
- A lost connection now gives a network error on every tool. Each call also stops after 45 seconds.
- The server now refuses request bodies larger than 256KB.
v4.22.0
Nov 11, 2026 · MCP protocol 2026-07-28 (also supports 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release adds date filters to list_campaigns, and update_segment now changes filter rules and returns a url.
Description changes
list_campaigns
- List campaigns with optional status and type filters.
+ List campaigns with optional status, type and date filters.
+ Sent campaigns include per-email stats (opens, clicks, unsubscribes).
+ Pass date_from and date_to to get the campaigns sent in a period, e.g.
+ "compared to last month" is one call for this month and one for last month, each with status sent and the first and last day of that month.
+ Always pass status with a date range: without it, MailerLite returns ready campaigns filtered by creation date.
Results are cursor-paginated — pass the cursor from the previous response to fetch the next page.update_segment
- Update a segment name
+ Rename a segment, change its filter rules, or both.
+ Pass at least one of name and filter.
+ A filter REPLACES all of the segment's existing rules, so send the complete new rule set, not only the rule that changes; read the current rules with get_segment first.
+ The filter format and the valid operator/field pairings are the same as for create_segment.Input schema changes
list_campaigns·date_from- optional property addedlist_campaigns·date_to- optional property addedupdate_segment·name- no longer requiredupdate_segment·filter- optional property added
v4.21.0
Nov 11, 2026 · MCP protocol 2026-07-28 (also supports 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release lets update_automation_email_content change part of an email, and get_automation_email now works without step_index.
Description changes
get_automation_email
Read one email step of an automation: subject, preheader, sender, reply-to, internal name, language, open tracking, UTM tags, plain text and HTML.
Works for emails designed in the visual editor and for HTML set via update_automation_email_content.
- The HTML is the stored source: merge tags such as {$name} and {$unsubscribe} and conditional blocks are kept as written, so edit it in place and pass it back to update_automation_email_content without re-adding them. has_html is false when the email has no body yet: set one with update_automation_email_content.
+ The HTML is the stored source: merge tags such as {$name} and {$unsubscribe} and conditional blocks are kept as written, so change it with update_automation_email_content edits copied from this HTML, without re-adding them. has_html is false when the email has no body yet: set one with update_automation_email_content.
The plain text can hold click-tracking markers such as {$url}{link-id:123}.
Keep each marker right after its link when you pass the plain text back to update_automation_email.update_automation_email_content
- Replace the HTML body of an automation email.
- This overwrites the existing email design — any content previously created in the dashboard editor is lost.
- Call get_automation_email first to read the current content, so you change it rather than replace it blind.
+ Change the HTML body of an automation email.
+ To change part of an existing body, pass edits: each one replaces an exact snippet of the stored HTML, so you do not resend the whole email.
+ Pass html only to set a new body or rewrite most of it.
+ Writing the HTML overwrites the existing email design — any content previously created in the dashboard editor is lost.
+ Call get_automation_email first to read the current content.
Use update_automation_email to change the subject or plain text instead.
The automation must be disabled: on an active one, ask the user first, then call update_automation with enabled: false, make the edit, and call update_automation with enabled: true to turn it back on.Input schema changes
get_automation_email·step_index- no longer requiredupdate_automation_email_content·html- no longer requiredupdate_automation_email_content·edits- optional property added
Annotations
update_automation_email_content· idempotentHint true → false
Bug fixes
get_automation_emailnow uses the first email when you do not sendstep_index. Before, the call failed with a validation error.update_automation_email_contentnow acceptseditsto change part of an email body. You do not need to send the whole HTML again.
v4.20.0
Nov 10, 2026 · MCP protocol 2026-07-28 (also supports 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release lets you filter subscribers by join date and edit more automation steps and email settings.
Tools
- Added:
select_automation_ab_test_winner- Pick the winning path of an A/B split step. - Added:
update_automation_step- Change an existing condition, action or A/B split step in place.
Description changes
add_automation_step
Add a new step to an EXISTING automation.
By default the step is appended at the end of the main path; pass after_step_id to insert it right after a specific step instead (get step ids from dry_run_automation).
When the main path ends in a condition there is no single end, so MailerLite asks for after_step_id and branch.
If after_step_id points at a condition step, you MUST pass branch: "yes" or "no" to say which path the new step belongs to.
If it points at an A/B test step, pass branch: "a_path"/"b_path"/"c_path" to place it inside one of the test's paths, or omit branch to place it after the test (once all paths converge).
Step types:
- email: email_subject.
Like create_automation, the HTML content cannot be authored here — design it in the drag & drop editor, or set the HTML afterwards with update_automation_email_content; update_automation_email sets the subject, plain text, sender, reply-to and preheader.
- delay: delay_value and delay_unit.
- condition: matching_type and 1 to 5 conditions.
Sends each subscriber down the yes or the no branch.
The steps that were below the insertion point move into the new condition's yes branch (or no, with move_to_branch).
- abtest: split_percentages, e.g. [50, 50] or [40, 30, 30], summing to 100.
Splits subscribers at random into 2 or 3 paths.
Only email and delay steps can go inside a path, and the plan must include A/B split steps.
- action: the complete action config. update_custom_field, mark_as_unsubscribed, remove_from_group / copy_to_group (group_ids), move_to_group (from_group_ids, then to_group_ids), go_to_step (must be the last step in its branch), send_internal_email_notification (1 to 5 recipients, who must be verified before the automation can be enabled).
Actions cannot go inside an A/B split path.
Conditions, A/B splits and actions change who gets which emails and change subscriber data once the automation runs.
The automation must be disabled to add steps.
MailerLite checks the placement and the referenced groups, fields and steps, and the response carries its warnings, such as a delay that ends a branch.
For an email step, from, from_name and reply_to set the sender, sender name and reply-to.
- They default to the account sender. from and reply_to must be verified on the MailerLite account.
+ They default to the account sender. from and reply_to must be verified on the MailerLite account. name, language_id, track_opens and google_analytics set the internal name, language, open tracking and UTM tags; they default to the subject and the account settings.
+ To change a condition, action or A/B split later, use update_automation_step rather than deleting and re-adding it.create_automation
Create a new automation workflow in MailerLite, including its trigger and an ordered list of email and delay steps.
IMPORTANT: This creates real resources.
- Email steps are created without HTML content — use update_automation_email_content to author the HTML body via the API, or design each email in the MailerLite visual editor.
+ An email step with email_content gets that text as its body, one paragraph per blank-line-separated block; email steps without it are created empty — use update_automation_email_content to author the HTML body via the API, or design each email in the MailerLite visual editor.
The new automation is left inactive.
- For conditions, A/B splits, actions or email copy, use build_automation instead.
+ For conditions, A/B splits, actions or emails with headings and buttons, use build_automation instead.
Args:
- name (string): Automation name.
- trigger_type (enum): What starts the automation (e.g. subscriber_joins_group, form_completed, abandoned_cart, subscriber_joins_segment, clicks_link, field_updated, anniversary).
- trigger_config (object): Trigger-specific fields — group_ids for subscriber_joins_group, segment_id for subscriber_joins_segment, form_id (+ form_type) for form_completed, shop_id for abandoned_cart, link for clicks_link, field_id (+ field_operator, value) for field_updated, field_id (+ group_ids, send_hour, send_minute) for anniversary.
Look IDs up first with list_resources / list_fields.
- steps (array): Ordered steps; each is { type: "email" | "delay" }.
- Email steps take email_subject; delay steps take delay_value and delay_unit.
+ Email steps take email_subject and optionally email_content (plain text, paragraphs separated by a blank line; for headings, buttons or HTML use build_automation or update_automation_email_content), email_name, track_opens and google_analytics; delay steps take delay_value and delay_unit.
+ - language_id (optional): language of every email's unsubscribe and footer text, from list_campaign_languages.
+ Defaults to the account language.
- from, from_name, reply_to (optional): sender, sender name and reply-to for every email step. from defaults to the account's verified sender, from_name to the account name, and reply_to to from. from and reply_to must be verified on the MailerLite account.
Change them per email later with update_automation_email.
MailerLite checks the trigger, the sender and the steps before creating anything.
If it refuses (for example abandoned_cart without a connected store, a group that does not exist, or a sender that is not verified), nothing is created and the result lists the problems.
Returns: a structured result with automation_id, dashboard_url, steps_created, email_steps_count, and next_steps guidance.
Examples:
- Welcome series: trigger_type="subscriber_joins_group", trigger_config={ group_ids: ["123"] }, steps=[{ type: "email", email_subject: "Welcome" }, { type: "delay", delay_value: 2, delay_unit: "days" }, { type: "email", email_subject: "Getting started" }].
- Birthday automation: trigger_type="anniversary", trigger_config={ field_id: "45", group_ids: ["123"], send_hour: "09", send_minute: "00" }.
- Validate the plan with build_custom_automation and confirm IDs with list_resources first.get_automation_email
- Read one email step of an automation: subject, preheader, sender, reply-to, plain text and HTML.
+ Read one email step of an automation: subject, preheader, sender, reply-to, internal name, language, open tracking, UTM tags, plain text and HTML.
Works for emails designed in the visual editor and for HTML set via update_automation_email_content.
The HTML is the stored source: merge tags such as {$name} and {$unsubscribe} and conditional blocks are kept as written, so edit it in place and pass it back to update_automation_email_content without re-adding them. has_html is false when the email has no body yet: set one with update_automation_email_content.
The plain text can hold click-tracking markers such as {$url}{link-id:123}.
Keep each marker right after its link when you pass the plain text back to update_automation_email.get_subscriber_count
Get the count of subscribers in the account.
By default returns the total across all statuses; pass status to get the count for just that status (e.g. unsubscribed).
+ Pass subscribed_from and subscribed_to to count subscribers who joined in a period, e.g.
+ "how many subscribers joined last month" is the first and last day of that month.
+ Leave status out for those questions unless the user asks only about subscribers who are still active.list_subscribers
- List subscribers in the account.
+ List subscribers in the account, newest first.
Results are cursor-paginated (default 25 per page) — pass the cursor from the previous response to fetch the next page.
- This tool cannot filter by name — MailerLite's API only supports filtering by status.
+ Filters by status and by the date subscribed (subscribed_from/subscribed_to).
+ This tool cannot filter by name.
Do not use this to search for or look up one specific subscriber; use get_subscriber with an ID/email instead, or ask the user for one.
+ To count subscribers, use get_subscriber_count instead of paging through this list.update_automation_email
- Update the subject line, plain text content, sender, sender name, reply-to and preheader of an email step in an automation.
+ Update the subject line, plain text content, sender, sender name, reply-to, preheader, internal name, language, open tracking and UTM tags of an email step in an automation.
Fields you leave out keep their current value, and the email design is kept. from and reply_to must be verified on the MailerLite account.
The preheader can only be set on emails built with the drag & drop, rich text or inline editor.
Use update_automation_email_content to replace the HTML body.
The automation must be disabled: on an active one, ask the user first, then call update_automation with enabled: false, make the edit, and call update_automation with enabled: true to turn it back on.Input schema changes
add_automation_step·name- optional property addedadd_automation_step·language_id- optional property addedadd_automation_step·track_opens- optional property addedadd_automation_step·google_analytics- optional property addedcreate_automation·steps[].email_name- optional property addedcreate_automation·steps[].track_opens- optional property addedcreate_automation·steps[].google_analytics- optional property addedcreate_automation·language_id- optional property addedget_subscriber_count·subscribed_from- optional property addedget_subscriber_count·subscribed_to- optional property addedlist_subscribers·subscribed_from- optional property addedlist_subscribers·subscribed_to- optional property addedupdate_automation_email·name- optional property addedupdate_automation_email·language_id- optional property addedupdate_automation_email·track_opens- optional property addedupdate_automation_email·google_analytics- optional property added
Output schema changes
add_automation_step·ab_test_winner- optional property addedadd_automation_step·automation_enabled- optional property addedcopy_automation_step·ab_test_winner- optional property addedcopy_automation_step·automation_enabled- optional property addeddelete_automation_step·ab_test_winner- optional property addeddelete_automation_step·automation_enabled- optional property addedget_automation_email·name- optional property addedget_automation_email·language_id- optional property addedget_automation_email·track_opens- optional property addedget_automation_email·google_analytics- optional property addedreorder_automation_step·ab_test_winner- optional property addedreorder_automation_step·automation_enabled- optional property addedupdate_automation_email·name- optional property addedupdate_automation_email·language_id- optional property addedupdate_automation_email·track_opens- optional property addedupdate_automation_email·google_analytics- optional property added
Bug fixes
create_automationnow usesemail_contentas the email body. Before, the tool accepted this field but did not use it.
v4.19.2
Nov 10, 2026 · MCP protocol 2026-07-28 (also supports 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
Maintenance release.
No tool or schema changes.
v4.19.1
Nov 10, 2026 · MCP protocol 2026-07-28 (also supports 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release gives clearer error messages when MailerLite rejects a sender, a reply-to address or custom HTML, and create_campaign makes fewer requests.
Description changes
add_automation_step
Add a new step to an EXISTING automation.
By default the step is appended at the end of the main path; pass after_step_id to insert it right after a specific step instead (get step ids from dry_run_automation).
When the main path ends in a condition there is no single end, so MailerLite asks for after_step_id and branch.
If after_step_id points at a condition step, you MUST pass branch: "yes" or "no" to say which path the new step belongs to.
If it points at an A/B test step, pass branch: "a_path"/"b_path"/"c_path" to place it inside one of the test's paths, or omit branch to place it after the test (once all paths converge).
Step types:
- email: email_subject.
- Like create_automation, the HTML content cannot be authored here — design it in the dashboard, or set it afterwards with update_automation_email / update_automation_email_content.
+ Like create_automation, the HTML content cannot be authored here — design it in the drag & drop editor, or set the HTML afterwards with update_automation_email_content; update_automation_email sets the subject, plain text, sender, reply-to and preheader.
- delay: delay_value and delay_unit.
- condition: matching_type and 1 to 5 conditions.
Sends each subscriber down the yes or the no branch.
The steps that were below the insertion point move into the new condition's yes branch (or no, with move_to_branch).
- abtest: split_percentages, e.g. [50, 50] or [40, 30, 30], summing to 100.
Splits subscribers at random into 2 or 3 paths.
Only email and delay steps can go inside a path, and the plan must include A/B split steps.
- action: the complete action config. update_custom_field, mark_as_unsubscribed, remove_from_group / copy_to_group (group_ids), move_to_group (from_group_ids, then to_group_ids), go_to_step (must be the last step in its branch), send_internal_email_notification (1 to 5 recipients, who must be verified before the automation can be enabled).
Actions cannot go inside an A/B split path.
Conditions, A/B splits and actions change who gets which emails and change subscriber data once the automation runs.
The automation must be disabled to add steps.
MailerLite checks the placement and the referenced groups, fields and steps, and the response carries its warnings, such as a delay that ends a branch.
For an email step, from, from_name and reply_to set the sender, sender name and reply-to.
They default to the account sender. from and reply_to must be verified on the MailerLite account.create_campaign
Create a new email campaign.
- The "from" email must be a verified sender on the account — this is verified automatically before the campaign is created; check Settings > Domains in the MailerLite dashboard if you need to add or verify a sender.
+ The "from" email must be a verified sender on the account; check Settings > Domains in the MailerLite dashboard if you need to add or verify a sender.Bug fixes
- Tool errors now explain why MailerLite rejected a sender or reply-to address. This works for
create_campaign,update_campaignandschedule_campaign, and the message points to the domain settings. - When an account cannot use the custom HTML editor,
create_campaign,update_campaignandupdate_automation_email_contentnow say so in the error. The message tells the client to design the email in the drag & drop editor. - One error now shows every hint that applies. Before, a client that sent a bad sender, reply-to and HTML together saw only one hint.
create_campaignandschedule_campaignno longer make an extra account request before they run. The API still rejects an unverified sender.
v4.19.0
Nov 9, 2026 · MCP protocol 2026-07-28 (also supports 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
Maintenance release.
No tool or schema changes.
v4.18.0
Nov 9, 2026 · MCP protocol 2026-07-28 (also supports 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
The e-commerce import tools now accept the documented request shape and read the API response correctly.
No tool or schema changes.
Bug fixes
- The orders import now accepts
{ orders: [...] }with options next to the list. A bare list also works. - The e-commerce import tools for categories, customers, products and orders now return the accepted items from the API response.
- The categories, customers and products imports return an error when the body is an object instead of a list.
v4.17.0
Nov 9, 2026 · MCP protocol 2026-07-28 (also supports 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07) · ⚠ Breaking
This release adds tools to search and read the MailerLite developer documentation, and it makes ID checks stricter in read and write tools.
Tools
- Added:
read_developer_docs_page- Read a page of the MailerLite developer documentation as Markdown. - Added:
search_developer_docs- Search the MailerLite developer documentation at developers.mailerlite.com.
Input schema changes
assign_subscriber_to_group·subscriber_id· ⚠ Breaking - minLength none → 1cancel_campaign·campaign_id· ⚠ Breaking - pattern none → "^\\d+$"delete_campaign·campaign_id· ⚠ Breaking - pattern none → "^\\d+$"delete_form·form_id· ⚠ Breaking - pattern none → "^\\d+$"delete_segment·segment_id· ⚠ Breaking - pattern none → "^\\d+$"delete_subscriber·subscriber_id· ⚠ Breaking - minLength none → 1get_campaign·campaign_id· ⚠ Breaking - pattern none → "^\\d+$"get_campaign_link_recipients·campaign_id· ⚠ Breaking - pattern none → "^\\d+$"get_campaign_links·campaign_id· ⚠ Breaking - pattern none → "^\\d+$"get_campaign_subscribers·campaign_id· ⚠ Breaking - pattern none → "^\\d+$"get_form·form_id· ⚠ Breaking - pattern none → "^\\d+$"get_form_subscribers·form_id· ⚠ Breaking - pattern none → "^\\d+$"get_segment·segment_id· ⚠ Breaking - pattern none → "^\\d+$"get_segment_subscribers·segment_id· ⚠ Breaking - pattern none → "^\\d+$"get_subscriber·subscriber_id· ⚠ Breaking - minLength none → 1get_subscriber_activity·subscriber_id· ⚠ Breaking - minLength none → 1schedule_campaign·campaign_id· ⚠ Breaking - pattern none → "^\\d+$"unassign_subscriber_from_group·subscriber_id· ⚠ Breaking - minLength none → 1update_campaign·campaign_id· ⚠ Breaking - pattern none → "^\\d+$"update_form·form_id· ⚠ Breaking - pattern none → "^\\d+$"update_segment·segment_id· ⚠ Breaking - pattern none → "^\\d+$"update_subscriber·subscriber_id· ⚠ Breaking - minLength none → 1
Output schema changes
add_subscriber·source· ⚠ Breaking - now accepts nullget_subscriber·source· ⚠ Breaking - now accepts nullupdate_subscriber·source· ⚠ Breaking - now accepts null
Bug fixes
- Tools for forms, segments, campaigns and subscribers now reject IDs that are not valid. Form, campaign and segment IDs must be numeric strings. Subscriber IDs and emails must not be empty,
.or... - The error for a wrong form, campaign or segment ID names the tool to use to find the right ID:
list_forms,list_campaignsorlist_segments. get_form,get_segment,get_campaign,get_campaign_linksandget_subscriberno longer fail with an "Output validation error" for these IDs. The tools now report that the item was not found.fetchandget_dashboard_linknow report "not found" for an ID that does not match a single item. Before,fetchcould return a list.add_subscriber,get_subscriberandupdate_subscribernow accept asourcevalue of null.
v4.16.0
Nov 5, 2026 · MCP protocol 2026-07-28 (also supports 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07) · ⚠ Breaking
This release makes tool arguments easier to use and gives clearer errors when an AI assistant sends a wrong argument.
Description changes
fetch
- Fetch the full record for a single MailerLite resource using an identifier returned by the search tool.
+ Takes a MailerLite resource id returned by the search tool and returns that resource's full record.
+ It does not fetch URLs or call HTTP endpoints (no url, path, method, or body arguments).
Always call search first to obtain this id — never guess or fabricate one.
Args:
- id (string, required): A prefixed identifier from search results formatted "<kind>:<id>" where kind is campaign, group, form, automation, or segment (e.g.
"campaign:123").
Alternatively, a bare id (no prefix) if "type" is also given.
- type (string, optional): One of campaign, group, form, automation, segment.
Required only when "id" is a bare id without a "<kind>:" prefix.
Returns: { "id": string, "title": string, "text": string, "url": string, "metadata": object }.
"text" is the full resource serialized as JSON; "metadata" carries kind-specific summary fields (e.g. status/type for campaigns, active_count for groups).
Examples:
- After search returns "automation:012" -> fetch with id="automation:012".
- If you already have a bare numeric id and know its kind -> fetch with id="123", type="group".
- An id without a "<kind>:" prefix and no "type" argument, an unsupported kind, or an id that matches nothing returns an actionable error telling you to call search first.Input schema changes
get_automation_activity·status- no longer requiredget_automation_activity·status· ⚠ Breaking - now limited to "completed", "active", "canceled", "failed", "complete", "cancelled", "cancel", "fail"list_resources·resource_type· ⚠ Breaking - now limited to "group", "form", "shop", "segment", "groups", "forms", "shops", "segments"select_resource·resource_type· ⚠ Breaking - now limited to "group", "form", "shop", "segment", "groups", "forms", "shops", "segments"
Output schema changes
get_automation_activity·status- required property added
Bug fixes
get_automation_activitynow usescompletedas the defaultstatus. The result always includes thestatusthat the tool used.get_automation_activityreturns an error that lists the allowed values whenstatusis not valid. The tool makes no request in this case.list_resourcesandselect_resourcenow accepttype,resourceTypeandresourceas names forresource_type. Ifresource_typeis present, the tool uses it.list_resourcesandselect_resourcenow return an error that names the correct tool whenresource_typeis a value such asautomationsorcampaigns.fetchreturns a clear error whenidis missing or has only spaces. The error tells the client to callsearchfirst.
v4.15.1
Nov 3, 2026 · MCP protocol 2026-07-28 (also supports 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
Maintenance release.
No tool or schema changes.
v4.15.0
Nov 3, 2026 · MCP protocol 2026-07-28 (also supports 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07) · ⚠ Breaking
Automation tools now do more checks and give clearer results, and lists keep their pagination data.
Tools
- Added:
build_automation- Build a whole automation in one call from a plan: its triggers, its steps (emails, delays, conditions, A/B splits, actions) and its email copy. - Added:
get_automation_build_guide- Get the plan format build_automation takes: the plan structure, every trigger with the data keys it accepts, the step types and the rules a plan must follow.
Description changes
add_automation_step
Add a new step to an EXISTING automation.
- By default the step is appended at the end of the flow; pass after_step_id to insert it right after a specific step instead (get step ids from dry_run_automation).
- Automations with condition or A/B split steps have no single end, so they need after_step_id.
+ By default the step is appended at the end of the main path; pass after_step_id to insert it right after a specific step instead (get step ids from dry_run_automation).
+ When the main path ends in a condition there is no single end, so MailerLite asks for after_step_id and branch.
If after_step_id points at a condition step, you MUST pass branch: "yes" or "no" to say which path the new step belongs to.
If it points at an A/B test step, pass branch: "a_path"/"b_path"/"c_path" to place it inside one of the test's paths, or omit branch to place it after the test (once all paths converge).
Step types:
- email: email_subject.
Like create_automation, the HTML content cannot be authored here — design it in the dashboard, or set it afterwards with update_automation_email / update_automation_email_content.
- delay: delay_value and delay_unit.
- condition: matching_type and 1 to 5 conditions.
Sends each subscriber down the yes or the no branch.
The steps that were below the insertion point move into the new condition's yes branch (or no, with move_to_branch).
- - abtest: split_percentages, e.g. [50, 50] or [40, 30, 30].
+ - abtest: split_percentages, e.g. [50, 50] or [40, 30, 30], summing to 100.
Splits subscribers at random into 2 or 3 paths.
Only email and delay steps can go inside a path, and the plan must include A/B split steps.
- action: the complete action config. update_custom_field, mark_as_unsubscribed, remove_from_group / copy_to_group (group_ids), move_to_group (from_group_ids, then to_group_ids), go_to_step (must be the last step in its branch), send_internal_email_notification (1 to 5 recipients, who must be verified before the automation can be enabled).
Actions cannot go inside an A/B split path.
Conditions, A/B splits and actions change who gets which emails and change subscriber data once the automation runs.
The automation must be disabled to add steps.
+ MailerLite checks the placement and the referenced groups, fields and steps, and the response carries its warnings, such as a delay that ends a branch.
For an email step, from, from_name and reply_to set the sender, sender name and reply-to.
They default to the account sender. from and reply_to must be verified on the MailerLite account.create_automation
Create a new automation workflow in MailerLite, including its trigger and an ordered list of email and delay steps.
IMPORTANT: This creates real resources.
Email steps are created without HTML content — use update_automation_email_content to author the HTML body via the API, or design each email in the MailerLite visual editor.
The new automation is left inactive.
+ For conditions, A/B splits, actions or email copy, use build_automation instead.
Args:
- name (string): Automation name.
- trigger_type (enum): What starts the automation (e.g. subscriber_joins_group, form_completed, abandoned_cart, subscriber_joins_segment, clicks_link, field_updated, anniversary).
- trigger_config (object): Trigger-specific fields — group_ids for subscriber_joins_group, segment_id for subscriber_joins_segment, form_id (+ form_type) for form_completed, shop_id for abandoned_cart, link for clicks_link, field_id (+ field_operator, value) for field_updated, field_id (+ group_ids, send_hour, send_minute) for anniversary.
Look IDs up first with list_resources / list_fields.
- steps (array): Ordered steps; each is { type: "email" | "delay" }.
Email steps take email_subject; delay steps take delay_value and delay_unit.
- - from, from_name, reply_to (optional): sender, sender name and reply-to for every email step.
- Default to the account sender. from and reply_to must be verified on the MailerLite account.
+ - from, from_name, reply_to (optional): sender, sender name and reply-to for every email step. from defaults to the account's verified sender, from_name to the account name, and reply_to to from. from and reply_to must be verified on the MailerLite account.
Change them per email later with update_automation_email.
- abandoned_cart requires a connected store — without one the call is refused up front and nothing is created.
+ MailerLite checks the trigger, the sender and the steps before creating anything.
+ If it refuses (for example abandoned_cart without a connected store, a group that does not exist, or a sender that is not verified), nothing is created and the result lists the problems.
Returns: a structured result with automation_id, dashboard_url, steps_created, email_steps_count, and next_steps guidance.
Examples:
- Welcome series: trigger_type="subscriber_joins_group", trigger_config={ group_ids: ["123"] }, steps=[{ type: "email", email_subject: "Welcome" }, { type: "delay", delay_value: 2, delay_unit: "days" }, { type: "email", email_subject: "Getting started" }].
- Birthday automation: trigger_type="anniversary", trigger_config={ field_id: "45", group_ids: ["123"], send_hour: "09", send_minute: "00" }.
- Validate the plan with build_custom_automation and confirm IDs with list_resources first.delete_automation_step
Delete a step from an automation's workflow.
- For condition or A/B test steps, branch_to_keep says what happens to the branches below it: "yes"/"no"/"a_path"/"b_path"/"c_path" keeps that one branch and reattaches it in the step's place, or "all" removes every branch.
+ Deleting a condition or A/B test step needs branch_to_keep, which says what happens to the branches below it: "yes"/"no" (condition) or "a_path"/"b_path"/"c_path" (A/B test, only paths the split has) keeps that one branch and reattaches it in the step's place, and "all" deletes the step with every branch.
+ Without it MailerLite refuses the delete.
+ Keeping an empty branch is refused too: pass "all" instead.
+ Leave branch_to_keep out for other step types.
A step that another step depends on — the target of a "go to step" action, of a condition, or of a delay's "continue from chosen step" — cannot be deleted until that reference is removed.
The automation must be disabled.list_email_templates
- List email templates (visual designs) with optional search filter.
+ List email templates (visual designs) that have content, with an optional name search.
+ Looks through the first 100 email templates in the account, then returns up to `limit` matches.reorder_automation_step
Move a step to a new position in an automation's workflow.
Pass new_parent_step_id to place it after another step, or omit it to make it the first step.
IMPORTANT: moving a single step with dragged_step_id leaves its own children behind, closing the gap at the old position — the same as dragging one box in the dashboard.
To move a whole sequence of steps together (e.g.
- "move the last email, wait and follow-up to right after the first email"), pass step_ids instead: the ordered list of step ids to move as a group.
- They end up chained together in that order at the new position, regardless of where each one currently sits.
+ "move the last email, wait and follow-up to right after the first email"), pass step_ids instead: up to 50 step ids that form a consecutive chain in flow order, each one directly after the one before it.
+ They move together and keep their order.
+ A condition can only be the last id, since the steps after it sit in its branches.
+ Steps inside an A/B test path move with the test, so after an A/B test list only the step its paths merge into.
+ It is all or nothing: if any part is refused, nothing moves.
The automation must be disabled.replace_automation_trigger
Change an automation trigger's TYPE (e.g. from subscriber_joins_group to subscriber_joins_segment).
This clears the trigger's configuration — follow up with update_automation_trigger to set the new type's data.
The automation must be disabled to edit its trigger.
- abandoned_cart requires a connected store — switching to it without one is refused up front instead of leaving an unconfigurable trigger behind.
+ abandoned_cart requires a connected store: without one MailerLite refuses the switch and nothing changes.send_test_automation
Send real test emails from an automation to a verified address on the account.
- Sends every designed email that is eligible for sending at once, skipping the rest; delays and conditions are not simulated.
+ Sends every designed email that is eligible for sending at once, and reports which ones were sent and which were skipped and why; delays and conditions are not simulated.
Not idempotent: each call sends the emails again.update_automation
Update an existing automation: rename it, turn it on or off, or change whether subscribers can go through it more than once.
Pass only what should change.
Use update_automation_trigger / replace_automation_trigger to change what starts it, and add_automation_step to add steps.
- name: rename it.
Works while the automation is active.
- enabled: true activates the automation so it starts sending to subscribers who match its trigger; false stops it.
If MailerLite refuses to activate it (incomplete or broken flow, unverified notification recipients, plan limits) the reason is returned — run dry_run_automation first.
- reentry: { repeatable: false } allows one run per subscriber. { repeatable: true, repeatable_settings: { mode: "immediately" } } lets them re-enter right away; { mode: "wait", value: 2, unit: "week" } makes them wait that long after their last entry.
Omit repeatable_settings to keep the current ones.
Anniversary, exact date and abandoned cart/checkout triggers always wait 1 day; purchase frequency always re-enters.
The response shows what was saved.
- Changing reentry needs the automation disabled.
- On an active automation, pass enabled: true to pause it, apply the change and turn it back on, or enabled: false to leave it off.
- Changes run in this order: disable, name and reentry, enable.
- If one is refused, the response lists what was already applied.
+ Everything is saved in one call.
+ Changing reentry on an active automation needs enabled: true (MailerLite pauses it, applies the change and turns it back on) or enabled: false (leave it off); without enabled the change is refused.
+ If MailerLite saves the other changes but cannot turn the automation on, it stays off and the response says why.update_automation_trigger
Update the configuration of an automation's existing trigger — for example the group_ids for subscriber_joins_group, or the segment_id for subscriber_joins_segment.
Send the COMPLETE config in `data`: fields you leave out are cleared, not kept.
This cannot change the trigger's TYPE — use replace_automation_trigger for that.
The automation must be disabled to edit its trigger.
Args:
- automation_id (string): The automation to update.
- - trigger_id (string, optional): Omit it when the automation has exactly one trigger (the common case) — it resolves automatically.
+ - trigger_id (string, optional): Omit it when the automation has exactly one trigger (the common case).
+ With several triggers MailerLite asks for it.
- data (object): Complete trigger configuration for the trigger's type, e.g. { group_ids: [...], exclude_group_ids: [] } for subscriber_joins_group, or { segment_id: "..." } for subscriber_joins_segment.Input schema changes
list_email_templates·limit· ⚠ Breaking - type number → integerlist_email_templates·limit· ⚠ Breaking - minimum none → 1list_email_templates·limit· ⚠ Breaking - maximum none → 100reorder_automation_step·step_ids· ⚠ Breaking - maxItems none → 50
Output schema changes
create_automation·steps_needing_sender_config· ⚠ Breaking - property removedcreate_automation·step_error· ⚠ Breaking - property removedcreate_automation·problems- optional property addedget_automation_email·is_designed- optional property addedget_webhook·meta.last_page- optional property addedget_webhook·meta.from- optional property addedget_webhook·meta.to- optional property addedget_webhook·meta.path- optional property addedget_webhook·meta- additional properties allowedget_webhook·links- optional property addedsend_test_automation·queued- optional property addedsend_test_automation·skipped- optional property addedupdate_automation_email·plain_text_error· ⚠ Breaking - property removed
Bug fixes
create_automationnow creates nothing when it refuses a request. The result lists theproblems. It refuses a trigger without its key field and a sender that is not verified.update_automation_triggernow returns the trigger type and the broken state of the trigger.reorder_automation_stepnow accepts up to 50step_ids. The ids must form a consecutive chain. Either all steps move or none move.delete_automation_stepnow needsbranch_to_keepfor a condition or an A/B test step. It refuses the request without it.add_automation_stepnow returns warnings in its response. For example, it warns about a delay that ends a branch.update_automationnow saves all changes in one call. If the automation cannot turn on, it stays off and the response gives the reason.send_test_automationnow reports which emails it sent and which it skipped. It returns a clear error when it can send no email.dry_run_automationnow warns about steps that no other step leads to.get_automation_emailnow returnsis_designed.list_email_templatesnow looks through the first 100 templates that have content. It then returns up tolimitmatches.limitmust be a whole number from 1 to 100.- Paginated lists, such as
get_webhook, now keeplinksand themetafields. fetchandget_dashboard_linknow find a group or a form by its ID. They show real errors and do not report them as "not found". The group link now shows the real group name.- When the service is not available, the error tells the caller to repeat the request later.
v4.14.6
Nov 3, 2026 · MCP protocol 2026-07-28 (also supports 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07) · ⚠ Breaking
The release makes automation tools clearer and safer to use, and it adds stricter checks on inputs.
Description changes
dry_run_automation
- Simulate automation flow without sending real emails.
+ Get an automation's steps in the order they run, as a dry run.
+ Returns step IDs, condition and A/B split branches, delays, email subjects, whether each email is designed, and warnings.
+ Use it to read the flow before editing steps or going live.
+ Sends nothing.get_automation_activity
Get activity log for an automation.
- Filter by status (completed, active, canceled, failed), date range, and subscriber email.
+ Filter by status (completed, active, canceled, failed), date range, and exact subscriber email.get_automation_email
Read one email step of an automation: subject, preheader, sender, reply-to, plain text and HTML.
Works for emails designed in the visual editor and for HTML set via update_automation_email_content.
- The HTML is the stored source: merge tags such as {$name} and {$unsubscribe} and conditional blocks are kept as written, so edit it in place and pass it back to update_automation_email_content without re-adding them.
+ The HTML is the stored source: merge tags such as {$name} and {$unsubscribe} and conditional blocks are kept as written, so edit it in place and pass it back to update_automation_email_content without re-adding them. has_html is false when the email has no body yet: set one with update_automation_email_content.
+ The plain text can hold click-tracking markers such as {$url}{link-id:123}.
+ Keep each marker right after its link when you pass the plain text back to update_automation_email.update_automation_delay
Update the duration of a delay step in an automation.
+ The automation must be disabled: on an active one, ask the user first, then call update_automation with enabled: false, make the edit, and call update_automation with enabled: true to turn it back on.update_automation_email
Update the subject line, plain text content, sender, sender name, reply-to and preheader of an email step in an automation.
Fields you leave out keep their current value, and the email design is kept. from and reply_to must be verified on the MailerLite account.
The preheader can only be set on emails built with the drag & drop, rich text or inline editor.
Use update_automation_email_content to replace the HTML body.
+ The automation must be disabled: on an active one, ask the user first, then call update_automation with enabled: false, make the edit, and call update_automation with enabled: true to turn it back on.update_automation_email_content
Replace the HTML body of an automation email.
This overwrites the existing email design — any content previously created in the dashboard editor is lost.
Call get_automation_email first to read the current content, so you change it rather than replace it blind.
Use update_automation_email to change the subject or plain text instead.
+ The automation must be disabled: on an active one, ask the user first, then call update_automation with enabled: false, make the edit, and call update_automation with enabled: true to turn it back on.Input schema changes
dry_run_automation·test_email- no longer requiredget_automation_activity·search· ⚠ Breaking - pattern none → "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"get_automation_activity·search· ⚠ Breaking - format none → "email"
Output schema changes
get_automation_email·has_html- optional property addedget_automation_email·next_step- optional property addedupdate_automation_delay·automation_enabled- optional property addedupdate_automation_email·automation_enabled- optional property addedupdate_automation_email_content·automation_enabled- optional property added
Bug fixes
create_automationnow returnssuccess: falsewhen a step is not fully set up. The next steps then tell you how to fix the step.get_automation_emailnow shows when an email has no body. It also explains the click-tracking markers in the plain text, so you can keep them when you edit.update_automation_delay,update_automation_emailandupdate_automation_email_contentnow return an error when the automation is active. The result showsautomation_enabled. Disable the automation first, make the edit, then enable it again.get_automation_activitynow returns an error whensearchis not a full email address. A blanksearchmeans no filter.dry_run_automationno longer needstest_email. A failed run now shows as an error.
v4.14.5
Oct 29, 2026 · MCP protocol 2026-07-28 (also supports 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release fixes OAuth sign-in errors and keeps active MCP clients signed in for longer.
No tool or schema changes.
Bug fixes
- The
/authorizeendpoint no longer returns a server error when an MCP client is expired or unknown. It now shows a message that tells the user to add the connector again.
Auth & transport
- When the client and redirect address are valid, OAuth errors now go back to the client as standard OAuth error responses.
- Clients that are in use now stay registered. Only clients that are not used expire.
- A client that has already expired must be removed and added again one time.
v4.14.4
Oct 28, 2026 · MCP protocol 2026-07-28 (also supports 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07) · ⚠ Breaking
This release adds e-commerce reports and product variants, and it shows a clear message when MailerLite is no longer connected.
Tools
- Added:
get_ecommerce_report- Get e-commerce revenue reports: the orders and revenue attributed to campaigns and automations, and what a shop or subscriber has earned. - Added:
manage_ecommerce_product_variants- Sync, update or delete a product's variants, such as its sizes or colours.
Description changes
get_auth_status
- Get current authentication status for this MailerLite connection.
+ Check with MailerLite whether this connection still works, and return its account details.manage_ecommerce_customers
- Create, update or delete customers within a shop.
+ Create, update, delete or bulk-import customers within a shop.
Requires `shop_id`.
+ Imports run in the background and do not trigger automations.manage_ecommerce_orders
Create, update, delete or bulk-import orders within a shop.
Requires `shop_id`.
+ Completing an order triggers purchase-based automations unless `without_automations` is set.manage_ecommerce_products
- Create, update, delete or bulk-import products within a shop.
+ Create, update, delete or bulk-import products within a shop, enable or disable a product with `change_status`, or set its categories with `assign_categories`.
Requires `shop_id`.
+ To manage variants one at a time, use manage_ecommerce_product_variants.read_ecommerce_data
- List or fetch MailerLite e-commerce data: shops, products, customers, orders, categories, carts, cart items, and the products in a category.
+ List or fetch MailerLite e-commerce data: shops, products, product variants, customers, orders, categories, carts, cart items, and the products in a category.
Read-only — it cannot create, change or delete anything; use the manage_ecommerce_* tools for that.
- `shop_id` is required for every resource except `shops`; `cart_items` also requires `cart_id`; `category_products` also requires `category_id` and supports only the `list` action.
- Use `action: "get"` with `id` to fetch one record, and the `list` cursor for further pages.
+ `shop_id` is required for every resource except `shops`; `product_variants` also requires `product_id`, `cart_items` `cart_id`, and `category_products` `category_id`, and those two variant and category lists support only the `list` action.
+ Use `action: "get"` with `id` to fetch one record, and `page` for further pages.
+ Orders carry `email_id`, the campaign or automation email the revenue is attributed to; it can stay null for a while after an order is created, because attribution runs in the background within the account's attribution window.
+ For revenue totals, use get_ecommerce_report.Input schema changes
manage_ecommerce_cart_items·data- variants 1 → 2manage_ecommerce_carts·data- variants 1 → 2manage_ecommerce_categories·data- variants 1 → 2manage_ecommerce_customers·action- added "import"manage_ecommerce_customers·data- variants 1 → 2manage_ecommerce_orders·data- variants 1 → 2manage_ecommerce_products·action- added "change_status", "assign_categories"manage_ecommerce_products·data- variants 1 → 2manage_ecommerce_shops·data- variants 1 → 2read_ecommerce_data·resource- added "product_variants"read_ecommerce_data·cursor· ⚠ Breaking - property removedread_ecommerce_data·product_id- optional property addedread_ecommerce_data·page- optional property addedread_ecommerce_data·filter- optional property addedread_ecommerce_data·sort- optional property added
Bug fixes
- When MailerLite is no longer connected, tools now return the message "MailerLite is no longer connected. Connect it again in your agent." Before, they returned a short "Unauthenticated." error.
get_auth_statusnow checks that the connection still works. It reports "not connected" when MailerLite is no longer connected.build_custom_automationnow returns the same "no longer connected" message when the connection is lost.read_ecommerce_datanow usespageto get more results. Thecursorfield did nothing, and the tool no longer accepts it.read_ecommerce_datanow acceptsfilterandsort.- Imports in
manage_ecommerce_customersnow send data in the format that the API expects.
Auth & transport
- When MailerLite is no longer connected, the server answers with HTTP 401. The client can then refresh its token.
- After a disconnect, the token refresh fails with
invalid_grant. The agent then shows the connection as closed, and you can connect again. - A temporary API error does not close the connection.
v4.14.2
Oct 26, 2026 · MCP protocol 2026-07-28 (also supports 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07) · ⚠ Breaking
This release adds more automation control: new step types, sender settings, re-entry settings and reading of email content and stats.
Tools
- Added:
get_automation_email- Read one email step of an automation: subject, preheader, sender, reply-to, plain text and HTML. - Added:
get_automation_stats- Get performance stats for an automation: sent, opens, clicks and unsubscribes, overall and for each email.
Description changes
add_automation_step
- Add a new email or delay step to an EXISTING automation.
+ Add a new step to an EXISTING automation.
By default the step is appended at the end of the flow; pass after_step_id to insert it right after a specific step instead (get step ids from dry_run_automation).
- IMPORTANT: like create_automation, an email step's HTML content cannot be authored via the API — design it in the dashboard, or set the subject/content afterwards with update_automation_email / update_automation_email_content.
+ Automations with condition or A/B split steps have no single end, so they need after_step_id.
+ If after_step_id points at a condition step, you MUST pass branch: "yes" or "no" to say which path the new step belongs to.
+ If it points at an A/B test step, pass branch: "a_path"/"b_path"/"c_path" to place it inside one of the test's paths, or omit branch to place it after the test (once all paths converge).
+ Step types:
+ - email: email_subject.
+ Like create_automation, the HTML content cannot be authored here — design it in the dashboard, or set it afterwards with update_automation_email / update_automation_email_content.
+ - delay: delay_value and delay_unit.
+ - condition: matching_type and 1 to 5 conditions.
+ Sends each subscriber down the yes or the no branch.
+ The steps that were below the insertion point move into the new condition's yes branch (or no, with move_to_branch).
+ - abtest: split_percentages, e.g. [50, 50] or [40, 30, 30].
+ Splits subscribers at random into 2 or 3 paths.
+ Only email and delay steps can go inside a path, and the plan must include A/B split steps.
+ - action: the complete action config. update_custom_field, mark_as_unsubscribed, remove_from_group / copy_to_group (group_ids), move_to_group (from_group_ids, then to_group_ids), go_to_step (must be the last step in its branch), send_internal_email_notification (1 to 5 recipients, who must be verified before the automation can be enabled).
+ Actions cannot go inside an A/B split path.
+ Conditions, A/B splits and actions change who gets which emails and change subscriber data once the automation runs.
The automation must be disabled to add steps.
+ For an email step, from, from_name and reply_to set the sender, sender name and reply-to.
+ They default to the account sender. from and reply_to must be verified on the MailerLite account.create_automation
Create a new automation workflow in MailerLite, including its trigger and an ordered list of email and delay steps.
IMPORTANT: This creates real resources.
Email steps are created without HTML content — use update_automation_email_content to author the HTML body via the API, or design each email in the MailerLite visual editor.
The new automation is left inactive.
Args:
- name (string): Automation name.
- - trigger_type (enum): What starts the automation (e.g. subscriber_joins_group, form_completed, abandoned_cart, subscriber_joins_segment).
- - trigger_config (object): Trigger-specific IDs — group_ids for subscriber_joins_group, segment_id for subscriber_joins_segment, form_id (+ form_type) for form_completed, shop_id for abandoned_cart.
- Look IDs up first with list_resources.
+ - trigger_type (enum): What starts the automation (e.g. subscriber_joins_group, form_completed, abandoned_cart, subscriber_joins_segment, clicks_link, field_updated, anniversary).
+ - trigger_config (object): Trigger-specific fields — group_ids for subscriber_joins_group, segment_id for subscriber_joins_segment, form_id (+ form_type) for form_completed, shop_id for abandoned_cart, link for clicks_link, field_id (+ field_operator, value) for field_updated, field_id (+ group_ids, send_hour, send_minute) for anniversary.
+ Look IDs up first with list_resources / list_fields.
- steps (array): Ordered steps; each is { type: "email" | "delay" }.
Email steps take email_subject; delay steps take delay_value and delay_unit.
+ - from, from_name, reply_to (optional): sender, sender name and reply-to for every email step.
+ Default to the account sender. from and reply_to must be verified on the MailerLite account.
+ Change them per email later with update_automation_email.
+ abandoned_cart requires a connected store — without one the call is refused up front and nothing is created.
Returns: a structured result with automation_id, dashboard_url, steps_created, email_steps_count, and next_steps guidance.
Examples:
- Welcome series: trigger_type="subscriber_joins_group", trigger_config={ group_ids: ["123"] }, steps=[{ type: "email", email_subject: "Welcome" }, { type: "delay", delay_value: 2, delay_unit: "days" }, { type: "email", email_subject: "Getting started" }].
+ - Birthday automation: trigger_type="anniversary", trigger_config={ field_id: "45", group_ids: ["123"], send_hour: "09", send_minute: "00" }.
- Validate the plan with build_custom_automation and confirm IDs with list_resources first.delete_automation_step
Delete a step from an automation's workflow.
- For condition or A/B test steps, branch_to_delete says what happens to the branches below it: "all" removes every branch, or "yes"/"no"/"a_path"/"b_path"/"c_path" keeps that one branch and reattaches it in the step's place.
+ For condition or A/B test steps, branch_to_keep says what happens to the branches below it: "yes"/"no"/"a_path"/"b_path"/"c_path" keeps that one branch and reattaches it in the step's place, or "all" removes every branch.
A step that another step depends on — the target of a "go to step" action, of a condition, or of a delay's "continue from chosen step" — cannot be deleted until that reference is removed.
The automation must be disabled.list_automations
List automations in the account.
Each automation's `status` (active, inactive, broken, or draft) is derived from its enabled/complete/broken flags, since the API has no native status field.
+ Each automation also carries a short `stats` summary (sent, unsubscribes and unsubscribe rate).
+ It has no opens or clicks: use get_automation_stats for those, which counts each subscriber once like the dashboard.
Results are page-paginated — increment the page number to fetch more results.reorder_automation_step
- Move a step — and everything below it — to a new position in an automation's workflow.
+ Move a step to a new position in an automation's workflow.
Pass new_parent_step_id to place it after another step, or omit it to make it the first step.
+ IMPORTANT: moving a single step with dragged_step_id leaves its own children behind, closing the gap at the old position — the same as dragging one box in the dashboard.
+ To move a whole sequence of steps together (e.g.
+ "move the last email, wait and follow-up to right after the first email"), pass step_ids instead: the ordered list of step ids to move as a group.
+ They end up chained together in that order at the new position, regardless of where each one currently sits.
The automation must be disabled.replace_automation_trigger
Change an automation trigger's TYPE (e.g. from subscriber_joins_group to subscriber_joins_segment).
This clears the trigger's configuration — follow up with update_automation_trigger to set the new type's data.
The automation must be disabled to edit its trigger.
+ abandoned_cart requires a connected store — switching to it without one is refused up front instead of leaving an unconfigurable trigger behind.update_automation
- Rename an existing automation.
- Only changes the name shown in the automations list — the trigger and steps are untouched.
- Works whether the automation is active or disabled.
- Use update_automation_trigger to change what starts it, or add_automation_step to add steps.
+ Update an existing automation: rename it, turn it on or off, or change whether subscribers can go through it more than once.
+ Pass only what should change.
+ Use update_automation_trigger / replace_automation_trigger to change what starts it, and add_automation_step to add steps.
+ - name: rename it.
+ Works while the automation is active.
+ - enabled: true activates the automation so it starts sending to subscribers who match its trigger; false stops it.
+ If MailerLite refuses to activate it (incomplete or broken flow, unverified notification recipients, plan limits) the reason is returned — run dry_run_automation first.
+ - reentry: { repeatable: false } allows one run per subscriber. { repeatable: true, repeatable_settings: { mode: "immediately" } } lets them re-enter right away; { mode: "wait", value: 2, unit: "week" } makes them wait that long after their last entry.
+ Omit repeatable_settings to keep the current ones.
+ Anniversary, exact date and abandoned cart/checkout triggers always wait 1 day; purchase frequency always re-enters.
+ The response shows what was saved.
+ Changing reentry needs the automation disabled.
+ On an active automation, pass enabled: true to pause it, apply the change and turn it back on, or enabled: false to leave it off.
+ Changes run in this order: disable, name and reentry, enable.
+ If one is refused, the response lists what was already applied.update_automation_email
- Update the subject line and plain text content of an email step in an automation.
+ Update the subject line, plain text content, sender, sender name, reply-to and preheader of an email step in an automation.
+ Fields you leave out keep their current value, and the email design is kept. from and reply_to must be verified on the MailerLite account.
+ The preheader can only be set on emails built with the drag & drop, rich text or inline editor.
+ Use update_automation_email_content to replace the HTML body.update_automation_email_content
Replace the HTML body of an automation email.
This overwrites the existing email design — any content previously created in the dashboard editor is lost.
+ Call get_automation_email first to read the current content, so you change it rather than replace it blind.
Use update_automation_email to change the subject or plain text instead.Input schema changes
add_automation_step·type- added "condition", "abtest", "action"add_automation_step·branch- optional property addedadd_automation_step·move_to_branch- optional property addedadd_automation_step·matching_type- optional property addedadd_automation_step·conditions- optional property addedadd_automation_step·split_percentages- optional property addedadd_automation_step·action- optional property addedadd_automation_step·from- optional property addedadd_automation_step·from_name- optional property addedadd_automation_step·reply_to- optional property addedcreate_automation·trigger_type· ⚠ Breaking - removed "subscriber_updated", "subscriber_added_via_api", "date_anniversary", "link_click", "campaign_opened", "campaign_finished"create_automation·trigger_type- added "field_updated", "anniversary", "clicks_link"create_automation·trigger_config.value- type number → string | numbercreate_automation·trigger_config.exclude_group_ids- optional property addedcreate_automation·trigger_config.link- optional property addedcreate_automation·trigger_config.field_id- optional property addedcreate_automation·trigger_config.field_operator- optional property addedcreate_automation·trigger_config.send_hour- optional property addedcreate_automation·trigger_config.send_minute- optional property addedcreate_automation·trigger_config.start_before_time- optional property addedcreate_automation·trigger_config.start_before_time_unit- optional property addedcreate_automation·trigger_config.start_after_time- optional property addedcreate_automation·trigger_config.start_after_time_unit- optional property addedcreate_automation·trigger_config.use_timezone- optional property addedcreate_automation·trigger_config.timezone_id- optional property addedcreate_automation·from- optional property addedcreate_automation·from_name- optional property addedcreate_automation·reply_to- optional property addeddelete_automation_step·branch_to_keep- optional property addedreorder_automation_step·dragged_step_id- no longer requiredreorder_automation_step·step_ids- optional property addedreplace_automation_trigger·type· ⚠ Breaking - removed "subscriber_updated", "subscriber_added_via_api", "date_anniversary", "link_click", "campaign_opened", "campaign_finished"replace_automation_trigger·type- added "field_updated", "anniversary", "clicks_link"update_automation·name- no longer requiredupdate_automation·name· ⚠ Breaking - maxLength none → 255update_automation·enabled- optional property addedupdate_automation·reentry- optional property addedupdate_automation_email·subject- no longer requiredupdate_automation_email·from- optional property addedupdate_automation_email·from_name- optional property addedupdate_automation_email·reply_to- optional property addedupdate_automation_email·preheader- optional property added
Output schema changes
add_automation_step·moved_step_ids- optional property addedadd_automation_step·warnings- optional property addedcopy_automation_step·moved_step_ids- optional property addedcopy_automation_step·warnings- optional property addedcreate_automation·trigger_broken- optional property addedcreate_automation·step_error- optional property addeddelete_automation_step·moved_step_ids- optional property addeddelete_automation_step·warnings- optional property addeddry_run_automation·test_email- optional property addeddry_run_automation·warnings- optional property addeddry_run_automation·trigger_configured- optional property addeddry_run_automation·triggers- optional property addedreorder_automation_step·moved_step_ids- optional property addedreorder_automation_step·warnings- optional property addedreplace_automation_trigger·trigger_broken- optional property addedupdate_automation·enabled- optional property addedupdate_automation·repeatable- optional property addedupdate_automation·repeatable_settings- optional property addedupdate_automation·applied- optional property addedupdate_automation_email·from- optional property addedupdate_automation_email·from_name- optional property addedupdate_automation_email·reply_to- optional property addedupdate_automation_email·preheader- optional property addedupdate_automation_email·plain_text_error- optional property addedupdate_automation_trigger·trigger_broken- optional property added
Annotations
add_automation_step· destructiveHint false → trueupdate_automation· title "Rename Automation" → "Update Automation"update_automation· destructiveHint false → trueupdate_automation· idempotentHint true → false
Bug fixes
- A
403error from MailerLite now shows only the reason from MailerLite, for example a plan limit or a missing permission. The tool no longer tells the user to sign in again. A401error still gives this advice. create_automationandreplace_automation_triggernow refuse theabandoned_carttrigger when the account has no connected store. The tool makes no changes in this case.add_automation_step,delete_automation_stepandreorder_automation_stepnow refuse changes that break the flow of the automation.delete_automation_stepnow refuses to delete a condition or A/B split step unless you setbranch_to_keep.reorder_automation_stepcan now move one step alone, or a group of steps together withstep_ids.add_automation_stepremoves the new step if a later part of the same call fails.add_automation_stepnow reports an error when the sender is not accepted.update_automation_emailexplains why it refuses plain text or a preheader.
v4.14.1
Oct 15, 2026 · MCP protocol 2026-07-28 (also supports 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
The release makes send_test_automation match which emails the backend sends, and it now says that each call sends real emails again.
Description changes
send_test_automation
- Send test emails from an automation.
+ Send real test emails from an automation to a verified address on the account.
+ Sends every designed email that is eligible for sending at once, skipping the rest; delays and conditions are not simulated.
+ Not idempotent: each call sends the emails again.Annotations
send_test_automation· idempotentHint true → false
Bug fixes
send_test_automationnow sends only the emails that are designed and eligible for sending. It skips the other emails and counts them inundesigned_count.send_test_automationnow returns "Emails not designed yet" and sends nothing when no email can be sent.- The
send_test_automationguidance now says that the tool sends real emails at once and that each call sends them again.
v4.14.0
Oct 8, 2026 · MCP protocol 2026-07-28 (also supports 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release lets AI assistants edit existing automations, makes search report failures and its limits instead of hiding them, and moves the MCP endpoint to the 2.x protocol SDK.
Tools
- Added:
add_automation_step— Add a new email or delay step to an EXISTING automation. - Added:
copy_automation_step— Duplicate a step, with its configuration, and insert the copy into the workflow. - Added:
delete_automation_step— Delete a step from an automation's workflow. - Added:
reorder_automation_step— Move a step — and everything below it — to a new position in an automation's workflow. - Added:
replace_automation_trigger— Change an automation trigger's TYPE (e.g. from subscriber_joins_group to subscriber_joins_segment). - Added:
update_automation— Rename an existing automation. - Added:
update_automation_trigger— Update the configuration of an automation's existing trigger — for example the group_ids for subscriber_joins_group, or the segment_id for subscriber_joins_segment.
Description changes
search
Search across MailerLite campaigns, groups, forms, automations, and segments by free-text query, matching names and key fields (subject, type, status, slug).
This is a discovery tool that returns lightweight result stubs, not full records.
To get the full details of a result, pass its id to the fetch tool.
Always call search before fetch — fetch requires an id from these results (or a bare id plus an explicit type; see the fetch tool description).
Args:
- query (string, required): Case-insensitive text to match across resource names and fields.
- limit (number): Max results, 1-20 (default 10).
- Returns: { "results": [{ "id": string, "title": string, "url": string }] }.
+ Returns: { "results": [{ "id": string, "title": string, "url": string }], "warnings"?: string[] }.
Each id is a prefixed identifier like "campaign:123", "group:456", "form:789", "automation:012", or "segment:345" — pass it verbatim to fetch.
- Returns an empty results array (never an error) when nothing matches.
+ Returns an empty results array when nothing matches.
+ Limitations: only the first 50 records of each resource type are searched; use the list_* tools to browse everything.
+ "warnings" lists types that failed or were truncated; empty results with no warnings mean nothing matched.
+ If every lookup fails, the tool returns an error.
Examples:
- "find my black friday campaign" -> query="black friday"
- "which welcome automation do I have" -> query="welcome"
- For unfiltered listing use list_campaigns / list_automations / list_resources instead.Output schema changes
search·warnings— optional property added
Protocol
- Latest MCP protocol revision 2025-11-25 → 2026-07-28
Bug fixes
- Search no longer returns an empty result list when MailerLite API lookups fail. If every lookup fails, it returns an error. If only some resource types fail, it returns the remaining results with a
warningslist naming the types that could not be searched. - Search now documents that it only looks at the first 50 records of each resource type, so large accounts should use the list tools to browse everything.
Auth & transport
- The MCP endpoint now runs on the 2.x MCP SDK. Clients using the 2025-era protocol keep receiving JSON responses, and clients that support the 2026-07-28 protocol are served statelessly, with no
initializecall and no session ID. GETandDELETErequests to/mcpnow return 405 Method Not Allowed instead of an idle event stream or an empty response.- Calling an unknown tool now returns a JSON-RPC
-32602error instead of a tool result withisError: true. - Invalid tool arguments produce the same error text without the "MCP error -32602:" prefix.
tools/listno longer includes theexecutionfield on each tool, which had only stated the default. The schema$schemais now JSON Schema 2020-12 instead of draft-07.- Requests from browser-based clients with non-localhost Origins are accepted on
/mcp. Every request still requires an OAuth bearer token.
v4.13.1
Sep 24, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07) · ⚠ Breaking
This release makes several lookup tools return a normal not-found result instead of an error, tightens how fetch handles missing or malformed IDs, and stops fetch from exposing webhook secrets.
Description changes
assign_subscriber_to_group
- Add a subscriber to a group
+ Add a subscriber to a group.
+ If no subscriber matches the ID/email or no group matches the ID, this returns a normal (non-error) result with found: false rather than failing — a missing subscriber or group is an expected outcome, not a tool error.delete_subscriber
Delete a subscriber from the account.
+ If no subscriber matches the ID, this returns a normal (non-error) result with success: false rather than failing — a missing subscriber is an expected outcome, not a tool error.fetch
Fetch the full record for a single MailerLite resource using an identifier returned by the search tool.
+ Always call search first to obtain this id — never guess or fabricate one.
Args:
- - id (string, required): A prefixed identifier from search results formatted "<kind>:<id>" where kind is campaign, group, form, or automation (e.g.
+ - id (string, required): A prefixed identifier from search results formatted "<kind>:<id>" where kind is campaign, group, form, automation, or segment (e.g.
"campaign:123").
+ Alternatively, a bare id (no prefix) if "type" is also given.
+ - type (string, optional): One of campaign, group, form, automation, segment.
+ Required only when "id" is a bare id without a "<kind>:" prefix.
Returns: { "id": string, "title": string, "text": string, "url": string, "metadata": object }.
"text" is the full resource serialized as JSON; "metadata" carries kind-specific summary fields (e.g. status/type for campaigns, active_count for groups).
Examples:
- After search returns "automation:012" -> fetch with id="automation:012".
- - The id must include the kind prefix from search; a bare numeric id or an unsupported kind returns an error.
+ - If you already have a bare numeric id and know its kind -> fetch with id="123", type="group".
+ - An id without a "<kind>:" prefix and no "type" argument, an unsupported kind, or an id that matches nothing returns an actionable error telling you to call search first.get_campaign
- Get details of a specific campaign
+ Get details of a specific campaign.
+ If no campaign matches the ID, this returns a normal (non-error) result with found: false rather than failing — a missing campaign is an expected outcome, not a tool error.get_group_subscribers
Get subscribers in a specific group.
Results are cursor-paginated — pass the cursor from the previous response to fetch the next page.
+ If no group matches the ID, this returns a normal (non-error) result with found: false rather than failing — a missing group is an expected outcome, not a tool error.get_subscriber_activity
- Get activity history for a subscriber (opens, clicks, etc.)
+ Get activity history for a subscriber (opens, clicks, etc.).
+ If no subscriber matches the ID or email, this returns a normal (non-error) result with found: false rather than failing — a missing subscriber is an expected outcome, not a tool error.search
- Search across MailerLite campaigns, groups, forms, and automations by free-text query, matching names and key fields (subject, type, status, slug).
+ Search across MailerLite campaigns, groups, forms, automations, and segments by free-text query, matching names and key fields (subject, type, status, slug).
This is a discovery tool that returns lightweight result stubs, not full records.
To get the full details of a result, pass its id to the fetch tool.
+ Always call search before fetch — fetch requires an id from these results (or a bare id plus an explicit type; see the fetch tool description).
Args:
- query (string, required): Case-insensitive text to match across resource names and fields.
- limit (number): Max results, 1-20 (default 10).
Returns: { "results": [{ "id": string, "title": string, "url": string }] }.
- Each id is a prefixed identifier like "campaign:123", "group:456", "form:789", or "automation:012" — pass it verbatim to fetch.
+ Each id is a prefixed identifier like "campaign:123", "group:456", "form:789", "automation:012", or "segment:345" — pass it verbatim to fetch.
Returns an empty results array (never an error) when nothing matches.
Examples:
- "find my black friday campaign" -> query="black friday"
- "which welcome automation do I have" -> query="welcome"
- For unfiltered listing use list_campaigns / list_automations / list_resources instead.Input schema changes
fetch·type— optional property added
Output schema changes
assign_subscriber_to_group·id· ⚠ Breaking — no longer requiredassign_subscriber_to_group·name· ⚠ Breaking — no longer requiredassign_subscriber_to_group·active_count· ⚠ Breaking — no longer requiredassign_subscriber_to_group·sent_count· ⚠ Breaking — no longer requiredassign_subscriber_to_group·opens_count· ⚠ Breaking — no longer requiredassign_subscriber_to_group·open_rate· ⚠ Breaking — no longer requiredassign_subscriber_to_group·clicks_count· ⚠ Breaking — no longer requiredassign_subscriber_to_group·click_rate· ⚠ Breaking — no longer requiredassign_subscriber_to_group·unsubscribed_count· ⚠ Breaking — no longer requiredassign_subscriber_to_group·unconfirmed_count· ⚠ Breaking — no longer requiredassign_subscriber_to_group·bounced_count· ⚠ Breaking — no longer requiredassign_subscriber_to_group·junk_count· ⚠ Breaking — no longer requiredassign_subscriber_to_group·created_at· ⚠ Breaking — no longer requiredassign_subscriber_to_group·found— optional property addedget_campaign·id· ⚠ Breaking — no longer requiredget_campaign·name· ⚠ Breaking — no longer requiredget_campaign·found— optional property addedget_group_subscribers·found— optional property addedget_subscriber_activity·found— optional property added
Bug fixes
- Fetching an automation no longer returns the signing secret of its webhook steps.
- Fetch now returns the same error for every resource type when a well-formed ID matches nothing, and the error tells the caller to use search. Raw backend messages are no longer exposed. Deleted resources are treated as not found. This is still a tool error, so code that matched the old per-type wording will need updating.
- Looking up a campaign, a group's subscribers or a subscriber's activity, or deleting a subscriber or assigning one to a group, with an ID that matches nothing now returns a successful result flagged as not found instead of a tool error. A campaign that has been deleted is treated the same way.
- Subscriber IDs and email addresses are now URL-encoded in request paths, so addresses containing characters such as
+no longer risk breaking the request. - Links in search and fetch results now use the configured API address instead of always pointing to the production host. The production host is still the default when no address is configured.
Auth & transport
- No changes.
v4.13.0
Sep 22, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release adds campaign language and segment targeting, lets update_campaign change recipients, and corrects several inaccurate behaviours and descriptions around automations and template discovery.
Tools
- Added:
list_campaign_languages— List languages available for campaign localization, with their numeric IDs, for use as `language_id` on create_campaign or update_campaign.
Description changes
create_automation
Create a new automation workflow in MailerLite, including its trigger and an ordered list of email and delay steps.
IMPORTANT: This creates real resources.
- Email steps are created but their HTML content CANNOT be authored via the API — the user must design each email in the MailerLite visual editor before the automation can send.
+ Email steps are created without HTML content — use update_automation_email_content to author the HTML body via the API, or design each email in the MailerLite visual editor.
The new automation is left inactive.
Args:
- name (string): Automation name.
- trigger_type (enum): What starts the automation (e.g. subscriber_joins_group, form_completed, abandoned_cart, subscriber_joins_segment).
- trigger_config (object): Trigger-specific IDs — group_ids for subscriber_joins_group, segment_id for subscriber_joins_segment, form_id (+ form_type) for form_completed, shop_id for abandoned_cart.
Look IDs up first with list_resources.
- steps (array): Ordered steps; each is { type: "email" | "delay" }.
Email steps take email_subject; delay steps take delay_value and delay_unit.
Returns: a structured result with automation_id, dashboard_url, steps_created, email_steps_count, and next_steps guidance.
Examples:
- Welcome series: trigger_type="subscriber_joins_group", trigger_config={ group_ids: ["123"] }, steps=[{ type: "email", email_subject: "Welcome" }, { type: "delay", delay_value: 2, delay_unit: "days" }, { type: "email", email_subject: "Getting started" }].
- Validate the plan with build_custom_automation and confirm IDs with list_resources first.create_campaign
Create a new email campaign.
- The "from" email must be a verified sender on the account — use get_auth_status or check Settings > Domains in the MailerLite dashboard if unsure.
+ The "from" email must be a verified sender on the account — this is verified automatically before the campaign is created; check Settings > Domains in the MailerLite dashboard if you need to add or verify a sender.discover_automation_templates
Browse pre-built automation workflow templates, optionally matched to a user's goal.
Returns each template's id, name, trigger, and step flow.
Args:
- type (enum): all | welcome | promotion | reminder | event | feedback | date.
- user_intent (string, optional): The user's goal (e.g.
- "abandoned cart") used for keyword/AI matching.
- Returns: { templates: [{ id, name, trigger_label, complexity, email_count, total_duration, steps[] }], matched, match_method }.
+ "abandoned cart") used for keyword matching against template names/descriptions.
+ Returns: { templates: [{ id, name, trigger_label, complexity, email_count, total_duration, steps[], steps_are_sample }], matched, match_method }.
+ When a template has no real step data from the API, "steps" is filled with an illustrative sample flow and "steps_are_sample" is set to true.
Examples:
- "show me welcome templates" -> type="welcome".
- To create an automation from a result, pass its numeric id to install_template.list_automations
List automations in the account.
+ Each automation's `status` (active, inactive, broken, or draft) is derived from its enabled/complete/broken flags, since the API has no native status field.
Results are page-paginated — increment the page number to fetch more results.update_campaign
Update campaign details.
`name` is optional — if omitted, the campaign's existing name is preserved automatically, so subject/content-only edits don't require knowing or inventing a name.
+ Only campaigns with status "draft" can be updated.
+ Omitting `groups` and `segments` leaves existing recipients unchanged.Input schema changes
create_campaign·segments— optional property addedcreate_campaign·language_id— optional property addedupdate_campaign·groups— optional property addedupdate_campaign·segments— optional property addedupdate_campaign·language_id— optional property added
Output schema changes
cancel_campaign·language_id— optional property addedcancel_campaign·language— optional property addedcreate_campaign·language_id— optional property addedcreate_campaign·language— optional property addedget_campaign·language_id— optional property addedget_campaign·language— optional property addedschedule_campaign·language_id— optional property addedschedule_campaign·language— optional property addedupdate_campaign·language_id— optional property addedupdate_campaign·language— optional property added
Bug fixes
list_automationsnow reports a realstatus(active, inactive, broken or draft) for each automation. Previously the field was always empty, and the widget showed every disabled automation as a draft.update_campaignnow keeps a campaign's existing language whenlanguage_idis omitted. Before this, the language was silently reset to the account default on every update.create_campaignandupdate_campaignnow reject requests that set bothgroupsandsegments, rather than silently using only one of them.discover_automation_templatesno longer claims AI matching or shows a hardcoded expected open rate. Matching is by keyword only, and templates without real step data are flagged withsteps_are_sampleand a note that the flow is illustrative.- Guidance in automation tools and prompts no longer says email HTML cannot be authored through the API. It now points to
update_automation_email_content. - Guidance for
create_campaignno longer suggestsget_auth_statusfor checking senders. The sender is verified automatically before the campaign is created.
Auth & transport
- No changes.
v4.12.1
Sep 16, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release contains internal updates to our analytics, with no changes to tools, schemas or client-facing behaviour.
No tool or schema changes.
Auth & transport
- No changes.
v4.11.1
Sep 8, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07) · ⚠ Breaking
This release moves e-commerce reads into their own tool, adds status filtering to the subscriber count, and includes internal updates to our analytics.
Tools
- Added:
read_ecommerce_data— List or fetch MailerLite e-commerce data: shops, products, customers, orders, categories, carts, cart items, and the products in a category.
Description changes
get_subscriber_count
- Get the total count of subscribers in the account
+ Get the count of subscribers in the account.
+ By default returns the total across all statuses; pass status to get the count for just that status (e.g. unsubscribed).manage_ecommerce_cart_items
- List, fetch, create, update or delete the line items of a cart.
+ Create, update or delete the line items of a cart.
Requires `shop_id` and `cart_id`.manage_ecommerce_carts
- List, fetch or update shopping carts within a shop (carts cannot be created or deleted via the API).
+ Update a shopping cart within a shop (carts cannot be created or deleted via the API).
Requires `shop_id`.manage_ecommerce_categories
- List, fetch, create, update, delete or bulk-import product categories within a shop.
+ Create, update, delete or bulk-import product categories within a shop.
Requires `shop_id`.manage_ecommerce_category_products
- List the products in a category, or attach/detach a product to/from a category.
- Requires `shop_id` and `category_id`; attach/detach also require `product_id`.
+ Attach a product to a category, or detach it from one.
+ Requires `shop_id`, `category_id` and `product_id`.manage_ecommerce_customers
- List, fetch, create, update or delete customers within a shop.
+ Create, update or delete customers within a shop.
Requires `shop_id`.manage_ecommerce_orders
- List, fetch, create, update, delete or bulk-import orders within a shop.
+ Create, update, delete or bulk-import orders within a shop.
Requires `shop_id`.manage_ecommerce_products
- List, fetch, create, update, delete or bulk-import products within a shop.
+ Create, update, delete or bulk-import products within a shop.
Requires `shop_id`.manage_ecommerce_shops
- List, fetch, create, update or delete MailerLite e-commerce shops.
- Use `id` as the shop id for get/update/delete.
+ Create, update or delete MailerLite e-commerce shops.
+ Use `id` as the shop id for update/delete.Input schema changes
get_subscriber_count·status— optional property addedmanage_ecommerce_cart_items·action· ⚠ Breaking — removed "list", "get"manage_ecommerce_cart_items·limit· ⚠ Breaking — property removedmanage_ecommerce_cart_items·cursor· ⚠ Breaking — property removedmanage_ecommerce_carts·action· ⚠ Breaking — removed "list", "get"manage_ecommerce_carts·limit· ⚠ Breaking — property removedmanage_ecommerce_carts·cursor· ⚠ Breaking — property removedmanage_ecommerce_categories·action· ⚠ Breaking — removed "list", "get"manage_ecommerce_categories·limit· ⚠ Breaking — property removedmanage_ecommerce_categories·cursor· ⚠ Breaking — property removedmanage_ecommerce_category_products·action· ⚠ Breaking — removed "list"manage_ecommerce_category_products·product_id· ⚠ Breaking — now requiredmanage_ecommerce_category_products·limit· ⚠ Breaking — property removedmanage_ecommerce_category_products·cursor· ⚠ Breaking — property removedmanage_ecommerce_customers·action· ⚠ Breaking — removed "list", "get"manage_ecommerce_customers·limit· ⚠ Breaking — property removedmanage_ecommerce_customers·cursor· ⚠ Breaking — property removedmanage_ecommerce_orders·action· ⚠ Breaking — removed "list", "get"manage_ecommerce_orders·limit· ⚠ Breaking — property removedmanage_ecommerce_orders·cursor· ⚠ Breaking — property removedmanage_ecommerce_products·action· ⚠ Breaking — removed "list", "get"manage_ecommerce_products·limit· ⚠ Breaking — property removedmanage_ecommerce_products·cursor· ⚠ Breaking — property removedmanage_ecommerce_shops·action· ⚠ Breaking — removed "list", "get"manage_ecommerce_shops·limit· ⚠ Breaking — property removedmanage_ecommerce_shops·cursor· ⚠ Breaking — property removed
Bug fixes
- Read-only access to e-commerce data no longer requires approving a tool that can also create, update, delete or import it. Listing and fetching now live in a separate read-only tool.
Auth & transport
- No changes.
v4.11.0
Aug 28, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07) · ⚠ Breaking
This release fixes several requests that previously failed or returned wrong results, and stops returning webhook signing secrets from list and get calls.
Tools
- Added:
list_timezones— List timezones and their numeric IDs, for use as `schedule.timezone_id` when scheduling a campaign.
Description changes
get_dashboard_link
- Generate MailerLite dashboard URL for editing automation or email.
+ Generate a MailerLite dashboard URL for a resource, or for an account-level settings destination. resource_type: "automation", "campaign", "form", or "segment" (each needs resource_id); "group" (with resource_id, links to that group's filtered subscriber list; without it, links to the groups list); or one of the settings_* types — "settings_domains" (domain/sender verification), "settings_account" (company profile, postal address), "settings_api" (API keys), "settings_billing" (subscription, plan, invoices), "settings_security" (two-factor authentication enforcement), "settings_profile" (password, name, photo, email, language, newsletter — on the SSO account profile), "settings_team" (team members), "settings_webhooks" (webhook management), "settings_notifications" (email notifications), "settings_integrations" (integrations overview), "settings_subscribe" (double opt-in settings), "settings_unsubscribe" (unsubscribe page), "settings_preference_center" (subscriber preference center), "settings_brand_styles" (brand styles) — none of the settings_* types need resource_id.get_subscriber
Get subscriber information by ID or email.
+ Requires an ID or email — MailerLite has no way to look subscribers up by name.
+ If you only have a name, ask the user for the subscriber's email or ID rather than calling list_subscribers to search for them.
If no subscriber matches, this returns a normal (non-error) result with found: false rather than failing — a missing subscriber is an expected outcome, not a tool error.list_resources
- List resources by type.
- Pass resource_type as a singular value: "group", "form", "shop", or "segment".
+ List resources by type: "group", "form", "shop", or "segment" (plurals like "groups" are also accepted).list_subscribers
List subscribers in the account.
Results are cursor-paginated (default 25 per page) — pass the cursor from the previous response to fetch the next page.
+ This tool cannot filter by name — MailerLite's API only supports filtering by status.
+ Do not use this to search for or look up one specific subscriber; use get_subscriber with an ID/email instead, or ask the user for one.update_campaign
- Update campaign details
+ Update campaign details.
+ `name` is optional — if omitted, the campaign's existing name is preserved automatically, so subject/content-only edits don't require knowing or inventing a name.Input schema changes
get_automation_activity·status— no longer limited to "completed", "active", "canceled", "failed"get_dashboard_link·automation_id· ⚠ Breaking — property removedget_dashboard_link·resource_type· ⚠ Breaking — required property addedget_dashboard_link·resource_id— optional property addedlist_resources·resource_type— no longer limited to "group", "form", "shop", "segment"select_resource·resource_type— no longer limited to "group", "form", "shop", "segment"
Output schema changes
get_dashboard_link·automation_name· ⚠ Breaking — property removedget_dashboard_link·resource_type— optional property addedget_dashboard_link·resource_name— optional property addedget_dashboard_link·error— optional property addedget_webhook·data.secret· ⚠ Breaking — property removedlist_webhooks·data[].secret· ⚠ Breaking — property removed
Annotations
get_dashboard_link· title "Get Dashboard Edit Link" → "Get Dashboard Link"
Bug fixes
get_dashboard_linknow returns correct links for campaigns, forms, segments, groups and a range of account settings pages, where previously only automation requests worked. A bad ID now returns an error that names the resource type.list_webhooksandget_webhookno longer return webhook signing secrets.create_webhookandupdate_webhookstill return them.update_campaignno longer fails with "The name field is required" whennameis omitted. The campaign's existing name is preserved.get_automation_activityaccepts common status variants such ascancelledandcomplete, which previously failed validation. Unknown values are still rejected.list_resourcesandselect_resourceaccept plural resource types such asgroups, and tolerate mixed case and surrounding whitespace.
Auth & transport
- No changes.
v4.10.0
Aug 24, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07) · ⚠ Breaking
This release fixes several automation tools that wrote to the wrong step or discarded email designs, makes dry_run_automation report accurately, and fixes failures in create_automation, create_form and create_segment.
Description changes
create_form
Create a new signup form.
Requires at least one group ID — use list_resources with resource_type "group" to find available groups first.
+ Do not guess or invent group IDs.create_segment
- Create a new subscriber segment.
- Can be created with just a name (filter rules can be configured later in the MailerLite dashboard), or with filter rules.
- Filter format: {"rules": [[{"operator": "...", "args": ["field_id", "value"]}]]}.
- Rules are grouped in arrays — rules within the same inner array use AND logic, separate inner arrays use OR logic.
- Note: the filter format is complex; creating a name-only segment and configuring filters in the dashboard is recommended.
+ Create a new subscriber segment, with or without filter rules.
+ Filter format: [[{"operator": "...", "args": [...]}]] — an array of AND groups; groups are OR'd together.
+ Do NOT wrap it in a {"rules": [...]} object.
+ Reference for common operators (args[0] is always the field):
+ - in_last / not_in_last — args: [field, N, unit]; unit is one of y,M,w,d,h,m,s. field: subscribed_at, last_sent_at, last_activity_at, last_open_at, last_click_at, created_at.
+ Example — opened in the last 90 days: ["last_open_at", 90, "d"]
+ - less / greater — args: [field, value]. field: opens_count, clicks_count, sent, open_rate, click_rate.
+ Example — click rate under 20%: ["click_rate", 20]
+ - equals — args: [field, value]. field: source, opens_count, clicks_count, sent, timezone_id, open_rate, click_rate, location.country_code
+ - doesnt_equal — args: [field, value]. field: source, timezone_id, location.country_code
+ - in_any / not_in_any — args: [field, value | [values]]. field: groups, campaigns.sent/opened/clicked/delivered, automations.active/completed (not_in_any also allows automations.all), ecommerce.purchased_products.product_id/variant_id, location.country_code
+ - in_all / not_in_all — args: [field, [values]]. field: groups only
+ - is_set — args: [field] (no value). field: campaigns.sent/opened/clicked/delivered, timezone_id, location.country_code, automations.active/completed
+ - is_not_set — args: [field] (no value). field: groups, campaigns.sent/opened/clicked/delivered, timezone_id, location.country_code, automations.active/completed/all, ecommerce.purchased_products.product_id
+ - before / after — args: [field, date]. field: subscribed_at, created_at
+ - matches / doesnt_match / contains / doesnt_contain — args: [field, value]. field: email only
+ - text_field_contains/doesnt_contain/equals/doesnt_equal, numeric_field_less/less_or_equal/greater/greater_or_equal/equals/doesnt_equal, date_field_less/less_or_equal/greater/greater_or_equal/equals/doesnt_equal/in_last/after_interval, field_is_set/field_is_not_set — for CUSTOM fields only; args[0] is the field's ID from list_fields, as a STRING (e.g.
+ "5", not 5)
+ Example — opened in the last 90 days AND click rate under 20%: [[{"operator": "in_last", "args": ["last_open_at", 90, "d"]}, {"operator": "less", "args": ["click_rate", 20]}]]
+ An invalid operator/field pairing is rejected locally with the valid options before the API is called.
+ Omit filter to create a name-only segment and configure rules later in the dashboard.Input schema changes
add_subscriber·groups[]· ⚠ Breaking — pattern none → "^\\d+$"assign_subscriber_to_group·group_id· ⚠ Breaking — pattern none → "^\\d+$"create_automation·trigger_config.group_ids[]· ⚠ Breaking — pattern none → "^\\d+$"create_campaign·groups[]· ⚠ Breaking — pattern none → "^\\d+$"create_form·groups[]· ⚠ Breaking — pattern none → "^\\d+$"create_segment·filter· ⚠ Breaking — type object → arraycreate_segment·filter— additional properties allowedcreate_segment·filter· ⚠ Breaking — minItems none → 1create_segment·filter[]· ⚠ Breaking — items addedcreate_segment·filter{key}· ⚠ Breaking — propertyNames removeddelete_group·group_id· ⚠ Breaking — pattern none → "^\\d+$"get_group_subscribers·group_id· ⚠ Breaking — pattern none → "^\\d+$"import_subscribers_to_group·group_id· ⚠ Breaking — pattern none → "^\\d+$"unassign_subscriber_from_group·group_id· ⚠ Breaking — pattern none → "^\\d+$"update_automation_email_content·email_id— no longer requiredupdate_automation_email_content·step_index— optional property addedupdate_group·group_id· ⚠ Breaking — pattern none → "^\\d+$"
Output schema changes
create_form·settings· ⚠ Breaking — variants 1 → 2dry_run_automation·emails_with_warnings— optional property addedget_form·settings· ⚠ Breaking — variants 1 → 2update_automation_email_content·step_index— optional property addedupdate_automation_email_content·email_step_count— optional property addedupdate_form·settings· ⚠ Breaking — variants 1 → 2
Bug fixes
update_automation_emailno longer discards the email design when it changes a subject. Previously the HTML body was lost and the email reverted to undesigned, while the call still returned success.step_indexinupdate_automation_email,update_automation_email_contentandupdate_automation_delaynow counts steps in the order the automation runs them. Previously it could resolve to a different step thandry_run_automationreported, so subjects and content could land on the wrong email.update_automation_email_contentcan now address an email bystep_index, so you no longer need to hold an email ID across step updates. A step that has no email yet returns an explanation instead of a failed write.dry_run_automationnow reports real delay durations instead of "0 minutes", so scheduled send times advance correctly across delays.dry_run_automationnow counts designed and undesigned emails consistently with its warnings. It no longer says all emails are ready beneath warnings that say otherwise, and it adds a count of emails with warnings.update_automation_emailnow writes plain text to the email's current ID rather than a stale one.create_automationno longer reports a failure after the automation was created. The cause was a step that appeared twice in the output being wrongly treated as a circular reference.create_formno longer reports an error when the form was created with empty settings.create_segmentnow validates filter rules locally against the supported operators and fields. An invalid combination returns an error naming the valid options instead of a generic "The filter is not valid" response from the API.create_segmentfilters must be an array of AND groups, with no{"rules": [...]}wrapper. Custom field IDs must be passed as strings.- Group ID inputs across the group, subscriber, campaign, form and automation tools must now be numeric strings. A group name or other non-numeric value is rejected before the API is called.
Auth & transport
- No changes.
v4.9.1
Aug 20, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release lets an assistant replace the HTML body of an automation email, which previously could only be done in the dashboard.
Tools
- Added:
update_automation_email_content— Replace the HTML body of an automation email.
Annotations
update_automation_email· title "Update Automation Email Content" → "Update Automation Email"
Auth & transport
- No changes.
v4.9.0
Aug 20, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release improves the error message returned when a request refers to a deleted resource, so AI assistants can recover instead of retrying the same ID.
No tool or schema changes.
Bug fixes
- API requests that fail with 410 Gone and no message from the API now return an explanation that the ID refers to a deleted item and that the caller should list current resources to get a valid ID. Previously the error was only "API request failed: 410 Gone", which led callers to retry the same ID. This affects tools that look up an automation by ID, such as those that update, dry-run or send a test for an automation. A message supplied by the API still takes precedence.
Auth & transport
- No changes.
v4.8.1
Aug 20, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07) · ⚠ Breaking
This release lets list_campaigns accept any page size from 1 to 100 and makes looking up a missing subscriber return a normal result instead of an error.
Description changes
get_subscriber
- Get subscriber information by ID or email
+ Get subscriber information by ID or email.
+ If no subscriber matches, this returns a normal (non-error) result with found: false rather than failing — a missing subscriber is an expected outcome, not a tool error.Input schema changes
list_campaigns·limit· ⚠ Breaking — minimum -9007199254740991 → 1list_campaigns·limit· ⚠ Breaking — maximum 9007199254740991 → 100
Output schema changes
add_subscriber·email· ⚠ Breaking — no longer requiredadd_subscriber·found— optional property addedget_subscriber·email· ⚠ Breaking — no longer requiredget_subscriber·found— optional property addedupdate_subscriber·email· ⚠ Breaking — no longer requiredupdate_subscriber·found— optional property added
Bug fixes
list_campaignsnow accepts any whole-numberlimitfrom 1 to 100. Previously, values outside the set 1, 10, 25, 50 and 100 (such as 20) were rejected with an error even though the schema suggested they were valid.get_subscriberno longer fails with an API error when no subscriber matches the given ID or email. It returns a normal, non-error result withfound: falseand a message saying no subscriber was found, so clients can check that field instead of parsing error text.
Auth & transport
- No changes.
v4.8.0
Aug 14, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release contains no changes to server behaviour, tools or schemas; the changes are to local development setup and dependencies.
No tool or schema changes.
Auth & transport
- No changes.
v4.7.6
Jul 30, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release contains no user-visible changes to the MailerLite MCP server.
No tool or schema changes.
Auth & transport
- No changes.
v4.7.5
Jul 30, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release adds an endpoint that supports domain verification for listing the server as an app in OpenAI's app directory, with no changes to tools or schemas.
No tool or schema changes.
Auth & transport
- Added an endpoint that serves the verification challenge OpenAI requires when submitting an app. Existing endpoints, OAuth flows and sessions are unchanged.
v4.7.4
Jul 30, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release adds structured output schemas across the server's tools, with no other changes to behaviour.
Output schema changes
add_subscriber·(root)— output schema addedassign_subscriber_to_group·(root)— output schema addedbatch_requests·(root)— output schema addedcancel_campaign·(root)— output schema addedcreate_campaign·(root)— output schema addedcreate_field·(root)— output schema addedcreate_form·(root)— output schema addedcreate_group·(root)— output schema addedcreate_segment·(root)— output schema addedcreate_webhook·(root)— output schema addeddelete_automation·(root)— output schema addeddelete_campaign·(root)— output schema addeddelete_field·(root)— output schema addeddelete_form·(root)— output schema addeddelete_group·(root)— output schema addeddelete_segment·(root)— output schema addeddelete_subscriber·(root)— output schema addeddelete_webhook·(root)— output schema addedfetch·(root)— output schema addedget_automation_activity·(root)— output schema addedget_campaign·(root)— output schema addedget_campaign_link_recipients·(root)— output schema addedget_campaign_links·(root)— output schema addedget_campaign_subscribers·(root)— output schema addedget_form·(root)— output schema addedget_form_subscribers·(root)— output schema addedget_group_subscribers·(root)— output schema addedget_segment·(root)— output schema addedget_segment_subscribers·(root)— output schema addedget_subscriber·(root)— output schema addedget_subscriber_activity·(root)— output schema addedget_subscriber_count·(root)— output schema addedget_webhook·(root)— output schema addedimport_subscribers_to_group·(root)— output schema addedlist_fields·(root)— output schema addedlist_webhooks·(root)— output schema addedmanage_ecommerce_cart_items·(root)— output schema addedmanage_ecommerce_carts·(root)— output schema addedmanage_ecommerce_categories·(root)— output schema addedmanage_ecommerce_category_products·(root)— output schema addedmanage_ecommerce_customers·(root)— output schema addedmanage_ecommerce_orders·(root)— output schema addedmanage_ecommerce_products·(root)— output schema addedmanage_ecommerce_shops·(root)— output schema addedschedule_campaign·(root)— output schema addedsearch·(root)— output schema addedunassign_subscriber_from_group·(root)— output schema addedupdate_campaign·(root)— output schema addedupdate_field·(root)— output schema addedupdate_form·(root)— output schema addedupdate_group·(root)— output schema addedupdate_segment·(root)— output schema addedupdate_subscriber·(root)— output schema addedupdate_webhook·(root)— output schema added
Auth & transport
- No changes.
v4.7.3
Jul 30, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07) · ⚠ Breaking
This release corrects the safety metadata that tools advertise to clients, so destructive and open-world hints now better match what each tool actually does.
Tools
- ⚠ Renamed:
generate_email_content→validate_email_content - ⚠ Renamed:
suggest_subject_lines→validate_subject_lines
Description changes
add_subscriber
- Add a new subscriber to MailerLite.
+ Create a MailerLite subscriber, or update an existing subscriber with the same email.
+ It can also change status, group membership, and resubscribe a previously unsubscribed subscriber.batch_requests
Execute multiple MailerLite API requests in a single call.
+ Requests may create, overwrite, or delete account data depending on their HTTP methods.
Maximum 50 requests per batch.
Paths must start with "api/".
Webhooks are not supported in batch requests.import_subscribers_to_group
- Import multiple subscribers to a group at once
+ Import multiple subscribers to a group at once.
+ Existing subscribers may be updated or resubscribed, and enabling autoresponders can send automation emails.Annotations
add_subscriber· title "Add Subscriber" → "Add or Update Subscriber"add_subscriber· destructiveHint false → truebatch_requests· destructiveHint false → truebuild_custom_automation· openWorldHint true → falsecreate_automation· destructiveHint true → falsediscover_automation_templates· openWorldHint true → falsedry_run_automation· openWorldHint true → falsefetch· openWorldHint true → falseget_automation_activity· openWorldHint true → falseget_campaign· openWorldHint true → falseget_campaign_link_recipients· openWorldHint true → falseget_campaign_links· openWorldHint true → falseget_campaign_subscribers· openWorldHint true → falseget_dashboard_link· openWorldHint true → falseget_form· openWorldHint true → falseget_form_subscribers· openWorldHint true → falseget_group_subscribers· openWorldHint true → falseget_segment· openWorldHint true → falseget_segment_subscribers· openWorldHint true → falseget_subscriber· openWorldHint true → falseget_subscriber_activity· openWorldHint true → falseget_subscriber_count· openWorldHint true → falseget_webhook· openWorldHint true → falseimport_subscribers_to_group· destructiveHint false → trueinstall_template· destructiveHint true → falselist_automations· openWorldHint true → falselist_campaigns· openWorldHint true → falselist_email_templates· openWorldHint true → falselist_fields· openWorldHint true → falselist_form_templates· openWorldHint true → falselist_forms· openWorldHint true → falselist_resources· openWorldHint true → falselist_segments· openWorldHint true → falselist_subscribers· openWorldHint true → falselist_webhooks· openWorldHint true → falsemanage_ecommerce_carts· destructiveHint false → truemanage_ecommerce_category_products· destructiveHint false → trueschedule_campaign· destructiveHint false → truesearch· openWorldHint true → falsesend_test_automation· destructiveHint false → trueunassign_subscriber_from_group· destructiveHint false → trueupdate_automation_delay· destructiveHint false → trueupdate_automation_email· destructiveHint false → trueupdate_campaign· destructiveHint false → trueupdate_field· destructiveHint false → trueupdate_form· destructiveHint false → trueupdate_group· destructiveHint false → trueupdate_segment· destructiveHint false → trueupdate_subscriber· destructiveHint false → trueupdate_webhook· destructiveHint false → true
Auth & transport
- No changes.
v4.7.2
Jul 27, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release updates internal dependencies and contains no user-visible changes to tools, behaviour, or the MCP server.
No tool or schema changes.
Auth & transport
- No changes.
v4.7.1
Jul 15, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release contains no changes to tool behaviour, schemas or the server's public interface.
No tool or schema changes.
Auth & transport
- No changes.
v4.7.0
Jul 15, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release updates the server's underlying dependencies and has no changes to tools, schemas or client-facing behaviour.
No tool or schema changes.
Auth & transport
- No changes.
v4.6.0
Jul 15, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release changes how the /mcp endpoint encodes its responses and how session identifiers are issued; no tools or schemas changed.
No tool or schema changes.
Auth & transport
- The
/mcpendpoint now returns plain JSON responses instead of an SSE stream. Clients that relied on parsing an event stream from this endpoint should acceptapplication/json. - The server now issues a self-contained
Mcp-Session-Idat initialize that carries the session and client identity, so each stateless request can be tied to its session from that header alone.
v4.5.0
Jul 7, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release hardens the OAuth flow and rate-limit handling, and makes tool errors and list output more consistent and compact.
No tool or schema changes.
Bug fixes
- Rate-limited requests are no longer retried multiple times at each level, which previously could send up to 15 requests to an already rate-limited API. Requests now make one attempt plus at most three retries.
- Retry-After values are capped at 10 seconds, so an unusually large value can no longer stall a request.
- Responses that differ slightly from the expected schema are now passed through instead of causing an error.
- Delete operations, test sends, automation tests and group unassignment now retry on rate limits and return the same actionable error hints as other tools (re-authenticate on 401, back off on 429).
- Errors from most tools now include a hint based on the status: re-authenticate for 401 and 403, back off for 429, and check the ID for 404.
- Pagination cursors from subscriber and campaign list tools no longer include trailing query parameters.
- List tool results are returned as compact JSON, which reduces the token cost of each call.
- If the MailerLite user lookup fails during sign-in, the callback now returns a retryable 502 error. Previously it continued with placeholder identity, which could cause different users' grants to collide and usage to be misattributed.
- Declining access during authorization now shows a clear message instead of a "Missing code" error.
Auth & transport
- The OAuth state parameter is now signed and verified in the callback, which prevents forged state from being used to complete a sign-in. OAuth flows that are in progress during the upgrade will need to reconnect once.
- The upstream token expiry is now recorded, so
get_auth_statuscan report when the MailerLite token lapses. - The key used to sign the approval cookie also signs the OAuth state, so rotating it invalidates both at once.
v4.4.2
Jul 3, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release has no changes to tools, schemas, or protocol behaviour that clients would notice.
No tool or schema changes.
Auth & transport
- No changes.
v4.4.1
Jul 3, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release contains no changes to tools, schemas, or client-facing behaviour; the only change is internal.
No tool or schema changes.
Auth & transport
- No changes.
v4.4.0
Jun 23, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release adds e-commerce management to the server, covering shops, products, categories, customers, orders and carts, and tightens the e-commerce schemas so they are clearer and stricter for clients.
Tools
- Added:
manage_ecommerce_cart_items— List, fetch, create, update or delete the line items of a cart. - Added:
manage_ecommerce_carts— List, fetch or update shopping carts within a shop (carts cannot be created or deleted via the API). - Added:
manage_ecommerce_categories— List, fetch, create, update, delete or bulk-import product categories within a shop. - Added:
manage_ecommerce_category_products— List the products in a category, or attach/detach a product to/from a category. - Added:
manage_ecommerce_customers— List, fetch, create, update or delete customers within a shop. - Added:
manage_ecommerce_orders— List, fetch, create, update, delete or bulk-import orders within a shop. - Added:
manage_ecommerce_products— List, fetch, create, update, delete or bulk-import products within a shop. - Added:
manage_ecommerce_shops— List, fetch, create, update or delete MailerLite e-commerce shops.
Bug fixes
- E-commerce resources that belong to a parent, such as a shop or cart, now require the parent identifier in their schemas, so incomplete requests are rejected up front instead of failing later.
Auth & transport
- No changes.
v4.3.4
Jun 12, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release fixes an analytics issue affecting clients that authenticate with older tokens.
No tool or schema changes.
Bug fixes
- Analytics requests no longer fail or send an invalid account identifier when the access token was issued before user IDs were included; the account identifier is now omitted in that case.
Auth & transport
- No changes.
v4.3.3
Jun 12, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release contains no changes to tools, schemas, or client-facing behaviour.
No tool or schema changes.
Auth & transport
- No changes.
v4.3.1
Jun 12, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release adds user identification to the server's authentication status response and has no other client-visible changes.
Output schema changes
get_auth_status·userId— optional property added
Auth & transport
- No changes.
v4.3.0
Jun 10, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release adds usage analytics on the server side and makes no changes to tools, schemas or client-facing behaviour.
No tool or schema changes.
Auth & transport
- No changes.
v4.2.0
Jun 9, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07) · ⚠ Breaking
This release adds structured output schemas to every tool that returns structured content, makes automation listing pageable, tightens the image proxy, and standardises tool annotations.
Description changes
build_custom_automation
- Validate an automation plan before creating it.
- Provide the trigger type, steps, and optionally a resource type to discover available resources (groups, forms, shops, segments).
- Returns validation warnings and matching resources.
+ Validate an automation plan and discover the resources it needs BEFORE creating it.
+ This is a dry validation step and does NOT create anything.
+ Args:
+ - trigger_type (enum): subscriber_joins_group | form_completed | abandoned_cart | subscriber_joins_segment.
+ - steps (array): Planned steps in order; each { type: "email" | "delay", email_subject?, delay_value?, delay_unit? }.
+ - resource_type (enum, optional): group | form | shop | segment.
+ Defaults based on trigger_type.
+ - resource_name (string, optional): Partial-match filter for the resource lookup.
+ Returns: { valid, warnings[], complexity, available_resources[], resource_type }. warnings flag issues (missing subjects, emails too close together, no matching resource); available_resources lists the IDs to wire into create_automation's trigger_config.
+ Examples:
+ - Check a 3-email welcome flow and get the group IDs before calling create_automation.
+ - Resolve any warnings, then call create_automation.create_automation
- Create a new automation workflow in MailerLite.
+ Create a new automation workflow in MailerLite, including its trigger and an ordered list of email and delay steps.
+ IMPORTANT: This creates real resources.
+ Email steps are created but their HTML content CANNOT be authored via the API — the user must design each email in the MailerLite visual editor before the automation can send.
+ The new automation is left inactive.
+ Args:
+ - name (string): Automation name.
+ - trigger_type (enum): What starts the automation (e.g. subscriber_joins_group, form_completed, abandoned_cart, subscriber_joins_segment).
+ - trigger_config (object): Trigger-specific IDs — group_ids for subscriber_joins_group, segment_id for subscriber_joins_segment, form_id (+ form_type) for form_completed, shop_id for abandoned_cart.
+ Look IDs up first with list_resources.
+ - steps (array): Ordered steps; each is { type: "email" | "delay" }.
+ Email steps take email_subject; delay steps take delay_value and delay_unit.
+ Returns: a structured result with automation_id, dashboard_url, steps_created, email_steps_count, and next_steps guidance.
+ Examples:
+ - Welcome series: trigger_type="subscriber_joins_group", trigger_config={ group_ids: ["123"] }, steps=[{ type: "email", email_subject: "Welcome" }, { type: "delay", delay_value: 2, delay_unit: "days" }, { type: "email", email_subject: "Getting started" }].
+ - Validate the plan with build_custom_automation and confirm IDs with list_resources first.discover_automation_templates
- Browse automation workflow templates filtered by type.
+ Browse pre-built automation workflow templates, optionally matched to a user's goal.
+ Returns each template's id, name, trigger, and step flow.
+ Args:
+ - type (enum): all | welcome | promotion | reminder | event | feedback | date.
+ - user_intent (string, optional): The user's goal (e.g.
+ "abandoned cart") used for keyword/AI matching.
+ Returns: { templates: [{ id, name, trigger_label, complexity, email_count, total_duration, steps[] }], matched, match_method }.
+ Examples:
+ - "show me welcome templates" -> type="welcome".
+ - To create an automation from a result, pass its numeric id to install_template.fetch
- Fetch full details for a MailerLite resource identified by the search tool
+ Fetch the full record for a single MailerLite resource using an identifier returned by the search tool.
+ Args:
+ - id (string, required): A prefixed identifier from search results formatted "<kind>:<id>" where kind is campaign, group, form, or automation (e.g.
+ "campaign:123").
+ Returns: { "id": string, "title": string, "text": string, "url": string, "metadata": object }.
+ "text" is the full resource serialized as JSON; "metadata" carries kind-specific summary fields (e.g. status/type for campaigns, active_count for groups).
+ Examples:
+ - After search returns "automation:012" -> fetch with id="automation:012".
+ - The id must include the kind prefix from search; a bare numeric id or an unsupported kind returns an error.install_template
- Install an automation template to create a new automation.
+ Install a pre-built automation template, creating a new (inactive) automation in the account.
+ You MUST obtain template_id from discover_automation_templates first — template IDs are long numeric strings (e.g.
+ "178927102220830454"); a non-numeric value is rejected.
+ Args:
+ - template_id (string): Numeric template ID from discover_automation_templates results.
+ Returns: { success, automation_id, automation_name, dashboard_url, next_steps }.
+ Examples:
+ - After discover returns a "Welcome series" template with id "178...", call install_template with that exact id.
+ - Emails still need to be designed in the dashboard after installing.list_automations
List automations in the account.
+ Results are page-paginated — increment the page number to fetch more results.search
- Search MailerLite campaigns, groups, forms, and automations.
+ Search across MailerLite campaigns, groups, forms, and automations by free-text query, matching names and key fields (subject, type, status, slug).
+ This is a discovery tool that returns lightweight result stubs, not full records.
+ To get the full details of a result, pass its id to the fetch tool.
+ Args:
+ - query (string, required): Case-insensitive text to match across resource names and fields.
+ - limit (number): Max results, 1-20 (default 10).
+ Returns: { "results": [{ "id": string, "title": string, "url": string }] }.
+ Each id is a prefixed identifier like "campaign:123", "group:456", "form:789", or "automation:012" — pass it verbatim to fetch.
+ Returns an empty results array (never an error) when nothing matches.
+ Examples:
+ - "find my black friday campaign" -> query="black friday"
+ - "which welcome automation do I have" -> query="welcome"
+ - For unfiltered listing use list_campaigns / list_automations / list_resources instead.start_automation_conversation
- Gather automation requirements through conversation.
+ Analyze a user's automation request and return the clarifying questions needed before building it.
+ Use this FIRST when a user wants to create an automation but has not specified the trigger, the target resource, and the timing.
+ It returns the questions to ask; it does NOT create anything or call the API.
+ Args:
+ - user_request (string): The user's verbatim automation request.
+ Returns: a conversation guide with detected.{ has_trigger_type, has_resource_name, has_timing_info }, questions_to_ask[], and instructions for how to proceed.
+ Examples:
+ - "I want to set up a welcome email" -> returns questions about trigger, resource, and timing.
+ - Once you already have trigger + resource + timing, skip this and go to build_custom_automation / create_automation.Input schema changes
list_automations·limit· ⚠ Breaking — type number → integerlist_automations·limit· ⚠ Breaking — minimum none → 1list_automations·limit· ⚠ Breaking — maximum none → 100list_automations·page— optional property added
Output schema changes
build_custom_automation·(root)— output schema addedcreate_automation·(root)— output schema addeddiscover_automation_templates·(root)— output schema addeddry_run_automation·(root)— output schema addedgenerate_email_content·(root)— output schema addedget_auth_status·(root)— output schema addedget_dashboard_link·(root)— output schema addedinstall_template·(root)— output schema addedlist_automations·(root)— output schema addedlist_campaigns·(root)— output schema addedlist_email_templates·(root)— output schema addedlist_form_templates·(root)— output schema addedlist_forms·(root)— output schema addedlist_resources·(root)— output schema addedlist_segments·(root)— output schema addedlist_subscribers·(root)— output schema addedselect_resource·(root)— output schema addedsend_test_automation·(root)— output schema addedstart_automation_conversation·(root)— output schema addedsuggest_subject_lines·(root)— output schema addedupdate_automation_delay·(root)— output schema addedupdate_automation_email·(root)— output schema added
Annotations
add_subscriber· openWorldHint unset → trueassign_subscriber_to_group· openWorldHint unset → truebatch_requests· openWorldHint unset → truebuild_custom_automation· idempotentHint unset → truebuild_custom_automation· openWorldHint false → truecancel_campaign· openWorldHint unset → truecreate_automation· openWorldHint false → truecreate_campaign· openWorldHint unset → truecreate_field· openWorldHint unset → truecreate_form· openWorldHint unset → truecreate_group· openWorldHint unset → truecreate_segment· openWorldHint unset → truecreate_webhook· openWorldHint unset → truedelete_automation· openWorldHint unset → truedelete_campaign· openWorldHint unset → truedelete_field· openWorldHint unset → truedelete_form· openWorldHint unset → truedelete_group· openWorldHint unset → truedelete_segment· openWorldHint unset → truedelete_subscriber· openWorldHint unset → truedelete_webhook· openWorldHint unset → truediscover_automation_templates· openWorldHint false → truedry_run_automation· idempotentHint unset → truedry_run_automation· openWorldHint false → truefetch· openWorldHint unset → truegenerate_email_content· idempotentHint unset → trueget_auth_status· idempotentHint unset → trueget_auth_status· openWorldHint unset → falseget_automation_activity· idempotentHint unset → trueget_automation_activity· openWorldHint unset → trueget_campaign· idempotentHint unset → trueget_campaign· openWorldHint unset → trueget_campaign_link_recipients· idempotentHint unset → trueget_campaign_link_recipients· openWorldHint unset → trueget_campaign_links· idempotentHint unset → trueget_campaign_links· openWorldHint unset → trueget_campaign_subscribers· idempotentHint unset → trueget_campaign_subscribers· openWorldHint unset → trueget_dashboard_link· idempotentHint unset → trueget_dashboard_link· openWorldHint false → trueget_form· idempotentHint unset → trueget_form· openWorldHint unset → trueget_form_subscribers· idempotentHint unset → trueget_form_subscribers· openWorldHint unset → trueget_group_subscribers· idempotentHint unset → trueget_group_subscribers· openWorldHint unset → trueget_segment· idempotentHint unset → trueget_segment· openWorldHint unset → trueget_segment_subscribers· idempotentHint unset → trueget_segment_subscribers· openWorldHint unset → trueget_subscriber· idempotentHint unset → trueget_subscriber· openWorldHint unset → trueget_subscriber_activity· idempotentHint unset → trueget_subscriber_activity· openWorldHint unset → trueget_subscriber_count· idempotentHint unset → trueget_subscriber_count· openWorldHint unset → trueget_webhook· idempotentHint unset → trueget_webhook· openWorldHint unset → trueimport_subscribers_to_group· openWorldHint unset → trueinstall_template· openWorldHint false → truelist_automations· openWorldHint false → truelist_campaigns· openWorldHint unset → truelist_email_templates· openWorldHint false → truelist_fields· idempotentHint unset → truelist_fields· openWorldHint unset → truelist_form_templates· openWorldHint unset → truelist_forms· openWorldHint unset → truelist_resources· openWorldHint false → truelist_segments· openWorldHint unset → truelist_subscribers· openWorldHint unset → truelist_webhooks· idempotentHint unset → truelist_webhooks· openWorldHint unset → trueschedule_campaign· openWorldHint unset → truesearch· openWorldHint unset → truesend_test_automation· openWorldHint false → truestart_automation_conversation· idempotentHint unset → truesuggest_subject_lines· idempotentHint unset → trueunassign_subscriber_from_group· openWorldHint unset → trueupdate_automation_delay· openWorldHint false → trueupdate_automation_email· openWorldHint false → trueupdate_campaign· openWorldHint unset → trueupdate_field· openWorldHint unset → trueupdate_form· openWorldHint unset → trueupdate_group· openWorldHint unset → trueupdate_segment· openWorldHint unset → trueupdate_subscriber· openWorldHint unset → trueupdate_webhook· openWorldHint unset → true
Bug fixes
- The image proxy now accepts only HTTPS URLs on the permitted storage host (exact match or subdomain) and no longer follows redirects, closing a gap where look-alike hostnames could pass the check.
- A redirect blocked by the image proxy now returns a 403 response instead of surfacing as a generic 500 error.
list_automationscan now page past the first 100 automations. Results include the current page, last page and whether more results are available. A missinglimitdefaults to 50.- Rate-limit responses from the MailerLite API are now detected by status rather than by matching error text, so retries trigger reliably on 429s and do not trigger on other errors.
Auth & transport
- No changes.
v4.1.0
May 11, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release makes the MCP server stateless, so each request is handled on its own without relying on a server-side session.
No tool or schema changes.
Auth & transport
- The MCP transport now runs in stateless mode: the server no longer keeps session state between requests, so clients should not depend on a session persisting across calls.
v4.0.0
May 11, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07) · ⚠ Breaking
This release adds tools for inspecting which links in a sent campaign were clicked and by whom, and tightens validation of tool inputs.
Tools
- Added:
get_campaign_link_recipients— Get subscribers who clicked a specific link in a campaign. - Added:
get_campaign_links— Get all tracked links in a sent campaign, including their IDs, URLs, and click counts.
Input schema changes
add_subscriber·email· ⚠ Breaking — pattern none → "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"add_subscriber·fields{key}· ⚠ Breaking — propertyNames addedadd_subscriber·(root)— additional properties allowedassign_subscriber_to_group·(root)— additional properties allowedbatch_requests·requests[].body{key}· ⚠ Breaking — propertyNames addedbatch_requests·requests[]— additional properties allowedbatch_requests·(root)— additional properties allowedbuild_custom_automation·steps[]— additional properties allowedbuild_custom_automation·(root)— additional properties allowedcancel_campaign·(root)— additional properties allowedcreate_automation·trigger_config— additional properties allowedcreate_automation·steps[]— additional properties allowedcreate_automation·(root)— additional properties allowedcreate_campaign·from· ⚠ Breaking — pattern none → "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"create_campaign·reply_to· ⚠ Breaking — pattern none → "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"create_campaign·(root)— additional properties allowedcreate_field·(root)— additional properties allowedcreate_form·(root)— additional properties allowedcreate_group·(root)— additional properties allowedcreate_segment·filter{key}· ⚠ Breaking — propertyNames addedcreate_segment·(root)— additional properties allowedcreate_webhook·(root)— additional properties alloweddelete_automation·(root)— additional properties alloweddelete_campaign·(root)— additional properties alloweddelete_field·(root)— additional properties alloweddelete_form·(root)— additional properties alloweddelete_group·(root)— additional properties alloweddelete_segment·(root)— additional properties alloweddelete_subscriber·(root)— additional properties alloweddelete_webhook·(root)— additional properties alloweddiscover_automation_templates·(root)— additional properties alloweddry_run_automation·test_email· ⚠ Breaking — pattern none → "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"dry_run_automation·(root)— additional properties allowedfetch·(root)— additional properties allowedgenerate_email_content·(root)— additional properties allowedget_automation_activity·page· ⚠ Breaking — minimum none → -9007199254740991get_automation_activity·page· ⚠ Breaking — maximum none → 9007199254740991get_automation_activity·limit· ⚠ Breaking — minimum none → -9007199254740991get_automation_activity·limit· ⚠ Breaking — maximum none → 9007199254740991get_automation_activity·(root)— additional properties allowedget_campaign·(root)— additional properties allowedget_campaign_subscribers·limit· ⚠ Breaking — minimum none → -9007199254740991get_campaign_subscribers·limit· ⚠ Breaking — maximum none → 9007199254740991get_campaign_subscribers·page· ⚠ Breaking — minimum none → -9007199254740991get_campaign_subscribers·page· ⚠ Breaking — maximum none → 9007199254740991get_campaign_subscribers·(root)— additional properties allowedget_dashboard_link·(root)— additional properties allowedget_form·(root)— additional properties allowedget_form_subscribers·page· ⚠ Breaking — minimum none → -9007199254740991get_form_subscribers·page· ⚠ Breaking — maximum none → 9007199254740991get_form_subscribers·(root)— additional properties allowedget_group_subscribers·(root)— additional properties allowedget_segment·(root)— additional properties allowedget_segment_subscribers·(root)— additional properties allowedget_subscriber·(root)— additional properties allowedget_subscriber_activity·(root)— additional properties allowedget_webhook·(root)— additional properties allowedimport_subscribers_to_group·subscribers[].email· ⚠ Breaking — pattern none → "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"import_subscribers_to_group·subscribers[].fields{key}· ⚠ Breaking — propertyNames addedimport_subscribers_to_group·subscribers[]— additional properties allowedimport_subscribers_to_group·(root)— additional properties allowedinstall_template·(root)— additional properties allowedlist_automations·(root)— additional properties allowedlist_campaigns·limit· ⚠ Breaking — minimum none → -9007199254740991list_campaigns·limit· ⚠ Breaking — maximum none → 9007199254740991list_campaigns·(root)— additional properties allowedlist_email_templates·(root)— additional properties allowedlist_fields·limit· ⚠ Breaking — minimum none → -9007199254740991list_fields·limit· ⚠ Breaking — maximum none → 9007199254740991list_fields·page· ⚠ Breaking — minimum none → -9007199254740991list_fields·page· ⚠ Breaking — maximum none → 9007199254740991list_fields·(root)— additional properties allowedlist_form_templates·(root)— additional properties allowedlist_forms·page· ⚠ Breaking — minimum none → -9007199254740991list_forms·page· ⚠ Breaking — maximum none → 9007199254740991list_forms·(root)— additional properties allowedlist_resources·(root)— additional properties allowedlist_segments·page· ⚠ Breaking — minimum none → -9007199254740991list_segments·page· ⚠ Breaking — maximum none → 9007199254740991list_segments·(root)— additional properties allowedlist_subscribers·(root)— additional properties allowedschedule_campaign·schedule— additional properties allowedschedule_campaign·(root)— additional properties allowedsearch·(root)— additional properties allowedselect_resource·(root)— additional properties allowedsend_test_automation·email· ⚠ Breaking — pattern none → "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"send_test_automation·(root)— additional properties allowedstart_automation_conversation·(root)— additional properties allowedsuggest_subject_lines·(root)— additional properties allowedunassign_subscriber_from_group·(root)— additional properties allowedupdate_automation_delay·(root)— additional properties allowedupdate_automation_email·(root)— additional properties allowedupdate_campaign·from· ⚠ Breaking — pattern none → "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"update_campaign·(root)— additional properties allowedupdate_field·(root)— additional properties allowedupdate_form·(root)— additional properties allowedupdate_group·(root)— additional properties allowedupdate_segment·(root)— additional properties allowedupdate_subscriber·fields{key}· ⚠ Breaking — propertyNames addedupdate_subscriber·(root)— additional properties allowedupdate_webhook·(root)— additional properties allowed
Auth & transport
- No changes.
v3.2.3
Mar 5, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release adds support for sending several MailerLite API requests in one call.
Tools
- Added:
batch_requests— Execute multiple MailerLite API requests in a single call.
Auth & transport
- No changes.
v3.2.2
Mar 5, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release adds webhook management and automation activity and deletion tools; no other client-visible behaviour changed.
Tools
- Added:
create_webhook— Create a new webhook. - Added:
delete_automation— Delete an automation - Added:
delete_webhook— Delete a webhook - Added:
get_automation_activity— Get activity log for an automation. - Added:
get_webhook— Get a specific webhook by ID - Added:
list_webhooks— List all webhooks - Added:
update_webhook— Update an existing webhook
Auth & transport
- No changes.
v3.2.1
Mar 4, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release adds validation of segment filters and structured output for segment responses.
No tool or schema changes.
Auth & transport
- No changes.
v3.2.0
Mar 2, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07) · ⚠ Breaking
This release reworks the content and automation helper tools so the connected assistant drafts the content and the server validates it, and it clarifies pagination and sender requirements across several tools.
Description changes
build_custom_automation
- Parse and validate automation requirements from user description.
+ Validate an automation plan before creating it.
+ Provide the trigger type, steps, and optionally a resource type to discover available resources (groups, forms, shops, segments).
+ Returns validation warnings and matching resources.create_campaign
Create a new email campaign.
+ The "from" email must be a verified sender on the account — use get_auth_status or check Settings > Domains in the MailerLite dashboard if unsure.create_form
- Create a new signup form
+ Create a new signup form.
+ Requires at least one group ID — use list_resources with resource_type "group" to find available groups first.create_segment
- Create a new subscriber segment with filter rules
+ Create a new subscriber segment.
+ Can be created with just a name (filter rules can be configured later in the MailerLite dashboard), or with filter rules.
+ Filter format: {"rules": [[{"operator": "...", "args": ["field_id", "value"]}]]}.
+ Rules are grouped in arrays — rules within the same inner array use AND logic, separate inner arrays use OR logic.
+ Note: the filter format is complex; creating a name-only segment and configuring filters in the dashboard is recommended.generate_email_content
- Generate email content (subject and body) using AI based on a description.
+ Validate email content (subject and body) against MailerLite best practices.
+ Provide the subject and plain_text you have drafted, and this tool will check for issues like subject length, spam trigger words, missing call-to-action, and body length limits.get_campaign_subscribers
- Get subscriber activity for a sent campaign (opens, clicks, etc.)
+ Get subscriber activity for a sent campaign (opens, clicks, etc.).
+ Results are page-paginated — increment the page number to fetch more results.get_form_subscribers
- Get subscribers who signed up via a specific form
+ Get subscribers who signed up via a specific form.
+ Results are page-paginated — increment the page number to fetch more results.get_group_subscribers
- Get subscribers in a specific group
+ Get subscribers in a specific group.
+ Results are cursor-paginated — pass the cursor from the previous response to fetch the next page.get_segment_subscribers
- Get subscribers belonging to a specific segment
+ Get subscribers belonging to a specific segment.
+ Results are cursor-paginated — pass the cursor from the previous response to fetch the next page.list_campaigns
List campaigns with optional status and type filters.
+ Results are cursor-paginated — pass the cursor from the previous response to fetch the next page.list_forms
List forms by type (popup, embedded, or promotion).
+ Results are page-paginated — increment the page number to fetch more results.list_resources
- List groups, forms, e-commerce shops, or segments.
+ List resources by type.
+ Pass resource_type as a singular value: "group", "form", "shop", or "segment".list_segments
List subscriber segments.
+ Results are page-paginated — increment the page number to fetch more results.list_subscribers
- List subscribers in the account (paginated, default 25 per page).
+ List subscribers in the account.
+ Results are cursor-paginated (default 25 per page) — pass the cursor from the previous response to fetch the next page.schedule_campaign
Schedule a campaign to be sent.
+ Requires a verified sender on the account.
Use delivery "instant" to send immediately, or "scheduled" with a schedule object to send at a specific time.suggest_subject_lines
- Generate multiple subject line suggestions for an email based on its purpose.
+ Validate a list of email subject line candidates against MailerLite best practices.
+ Provide subject lines you have drafted, and this tool will check each one for length, spam trigger words, and other issues.Input schema changes
build_custom_automation·description· ⚠ Breaking — property removedbuild_custom_automation·trigger_type· ⚠ Breaking — required property addedbuild_custom_automation·steps· ⚠ Breaking — required property addedbuild_custom_automation·resource_type— optional property addedbuild_custom_automation·resource_name— optional property addedgenerate_email_content·email_description· ⚠ Breaking — property removedgenerate_email_content·trigger_type· ⚠ Breaking — property removedgenerate_email_content·automation_goal· ⚠ Breaking — property removedgenerate_email_content·subject· ⚠ Breaking — required property addedgenerate_email_content·plain_text· ⚠ Breaking — required property addedget_campaign_subscribers·limit· ⚠ Breaking — type number → integerget_campaign_subscribers·limit— no longer limited to 10, 25, 50, 100list_campaigns·limit· ⚠ Breaking — type number → integerlist_campaigns·limit— no longer limited to 1, 10, 25, 50, 100suggest_subject_lines·email_purpose· ⚠ Breaking — property removedsuggest_subject_lines·count· ⚠ Breaking — property removedsuggest_subject_lines·subject_lines· ⚠ Breaking — required property added
Annotations
build_custom_automation· title "Build Custom Automation" → "Validate Automation Plan"generate_email_content· title "Generate Email Content" → "Validate Email Content"get_auth_status· destructiveHint unset → falseget_auth_status· readOnlyHint unset → truesuggest_subject_lines· title "Suggest Email Subject Lines" → "Validate Subject Lines"
Auth & transport
- No changes.
v3.1.4
Feb 23, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release restores session handling that had been affected by a previous cleanup, with no changes to the available tools.
No tool or schema changes.
Bug fixes
- Fixed session state that stopped working after a previous release's cleanup, so connections that rely on persisted sessions behave as before.
Auth & transport
- No changes.
v3.1.3
Feb 23, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release resets all existing sessions, so connected clients must re-authenticate, and removes the server's request deduplication cache.
No tool or schema changes.
Bug fixes
- Removed the request deduplication cache, so repeated identical requests are no longer answered from a cache and are processed each time.
Auth & transport
- All existing sessions were invalidated; every connected client must sign in again after upgrading.
v3.1.0
Feb 23, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)
This release fixes an issue where OAuth-authenticated requests could be served incorrect cached responses.
No tool or schema changes.
Bug fixes
- OAuth-authenticated requests now include the authorisation header when the server checks for duplicate requests, so a cached response is no longer returned to a request made with different credentials.
Auth & transport
- OAuth requests now pass the authorisation header through to request deduplication, so cached responses are matched per credential.
v3.0.0
Feb 18, 2026 · MCP protocol 2025-11-25 (also supports 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07) · ⚠ Breaking
This release replaces the server's tool set and moves it to the latest MCP protocol revision, with fixes to campaign content, subscriber listing and OAuth setup.
Tools
- Added:
build_custom_automation— Parse and validate automation requirements from user description. - Added:
create_form— Create a new signup form - Added:
create_segment— Create a new subscriber segment with filter rules - Added:
discover_automation_templates— Browse automation workflow templates filtered by type. - Added:
dry_run_automation— Simulate automation flow without sending real emails. - Added:
generate_email_content— Generate email content (subject and body) using AI based on a description. - Added:
get_dashboard_link— Generate MailerLite dashboard URL for editing automation or email. - Added:
get_segment— Get details of a specific segment - Added:
get_segment_subscribers— Get subscribers belonging to a specific segment - Added:
install_template— Install an automation template to create a new automation. - Added:
list_email_templates— List email templates (visual designs) with optional search filter. - Added:
list_form_templates— List form design templates by type (popup, promotion, or embedded). - Added:
list_resources— List groups, forms, e-commerce shops, or segments. - Added:
select_resource— Confirms a user-selected resource (group, form, shop, or segment). - Added:
send_test_automation— Send test emails from an automation. - Added:
start_automation_conversation— Gather automation requirements through conversation. - Added:
suggest_subject_lines— Generate multiple subject line suggestions for an email based on its purpose. - Added:
update_automation_delay— Update the duration of a delay step in an automation. - Added:
update_automation_email— Update the subject line and plain text content of an email step in an automation. - ⚠ Removed:
batch - ⚠ Removed:
create_webhook - ⚠ Removed:
delete_automation - ⚠ Removed:
delete_webhook - ⚠ Removed:
forget_subscriber - ⚠ Removed:
get_automation - ⚠ Removed:
get_automation_activity - ⚠ Removed:
get_single_import - ⚠ Removed:
get_subscribers_in_segment - ⚠ Removed:
get_webhook - ⚠ Removed:
list_campaign_languages - ⚠ Removed:
list_groups - ⚠ Removed:
list_timezones - ⚠ Removed:
list_webhooks - ⚠ Removed:
update_webhook
Description changes
add_subscriber
Add a new subscriber to MailerLite.
- This can also be used to update an existing subscriber.create_automation
- Create a draft automation
+ Create a new automation workflow in MailerLite.create_campaign
- Create a new email campaign
+ Create a new email campaign.create_field
- Create a new field
+ Create a new custom subscriber fielddelete_field
- Delete a field
+ Delete a custom subscriber fielddelete_group
- Delete a group
+ Delete a subscriber groupdelete_segment
- Delete a segment
+ Delete a segment.delete_subscriber
- Delete a subscriber.
- This removes them from the account, but their information is kept in case they re-subscribe.
+ Delete a subscriber from the account.fetch
- Fetch full details for a MailerLite resource identified by the search tool.
+ Fetch full details for a MailerLite resource identified by the search toolget_campaign
- Get a specific campaign
+ Get details of a specific campaignget_campaign_subscribers
- Get subscriber activity for a sent campaign
+ Get subscriber activity for a sent campaign (opens, clicks, etc.)get_form
- Get a single form by its ID
+ Get details of a specific formget_form_subscribers
- Get subscribers who signed up to a specific form
+ Get subscribers who signed up via a specific formget_group_subscribers
- Get subscribers in a group
+ Get subscribers in a specific groupget_subscriber_activity
- Get activity history for a subscriber
+ Get activity history for a subscriber (opens, clicks, etc.)get_subscriber_count
- Get the total count of subscribers
+ Get the total count of subscribers in the accountimport_subscribers_to_group
- Import multiple subscribers to a group
+ Import multiple subscribers to a group at oncelist_automations
- List all automations
+ List automations in the account.list_campaigns
- List all campaigns
+ List campaigns with optional status and type filters.list_fields
- List all fields
+ List all custom subscriber fieldslist_forms
- List all forms of a specific type
+ List forms by type (popup, embedded, or promotion).list_segments
- List all segments
+ List subscriber segments.list_subscribers
- List all subscribers
+ List subscribers in the account (paginated, default 25 per page).schedule_campaign
- Schedule a campaign to be sent
+ Schedule a campaign to be sent.
+ Use delivery "instant" to send immediately, or "scheduled" with a schedule object to send at a specific time.search
Search MailerLite campaigns, groups, forms, and automations.
- Returns result identifiers that can be fetched for full detail.update_field
- Update a field
+ Update a custom subscriber field nameupdate_form
- Update a form
+ Update a form nameupdate_group
- Update a group
+ Update a group nameupdate_segment
- Update a segment
+ Update a segment nameupdate_subscriber
Update subscriber information.
- Note: this is a non-destructive operation, so omitting fields will not remove them.Input schema changes
add_subscriber·fields.*— now accepts nulladd_subscriber·fields.*· ⚠ Breaking — type any → string | numberadd_subscriber·groups[]· ⚠ Breaking — type object → stringadd_subscriber·groups[].id· ⚠ Breaking — property removedadd_subscriber·groups[].name· ⚠ Breaking — property removedadd_subscriber·groups[].active_count· ⚠ Breaking — property removedadd_subscriber·groups[].sent_count· ⚠ Breaking — property removedadd_subscriber·groups[].opens_count· ⚠ Breaking — property removedadd_subscriber·groups[].open_rate· ⚠ Breaking — property removedadd_subscriber·groups[].clicks_count· ⚠ Breaking — property removedadd_subscriber·groups[].click_rate· ⚠ Breaking — property removedadd_subscriber·groups[].unsubscribed_count· ⚠ Breaking — property removedadd_subscriber·groups[].unconfirmed_count· ⚠ Breaking — property removedadd_subscriber·groups[].bounced_count· ⚠ Breaking — property removedadd_subscriber·groups[].junk_count· ⚠ Breaking — property removedadd_subscriber·groups[].created_at· ⚠ Breaking — property removedadd_subscriber·groups[].updated_at· ⚠ Breaking — property removedadd_subscriber·groups[]— additional properties allowedadd_subscriber·status— optional property addedadd_subscriber·resubscribe— optional property addedcreate_automation·trigger_type· ⚠ Breaking — required property addedcreate_automation·trigger_config· ⚠ Breaking — required property addedcreate_automation·steps· ⚠ Breaking — required property addedcreate_campaign·type· ⚠ Breaking — now limited to "regular", "ab", "resend", "multivariate"create_campaign·from· ⚠ Breaking — format none → "email"get_auth_status·(root)— additional properties allowedget_campaign_subscribers·filter· ⚠ Breaking — property removedget_campaign_subscribers·include· ⚠ Breaking — property removedget_campaign_subscribers·type— optional property addedget_campaign_subscribers·search— optional property addedget_form_subscribers·limit· ⚠ Breaking — type number → integerget_form_subscribers·limit· ⚠ Breaking — minimum none → 1get_form_subscribers·limit· ⚠ Breaking — maximum none → 100get_form_subscribers·page· ⚠ Breaking — type number → integerget_subscriber_count·(root)— additional properties allowedlist_automations·filter· ⚠ Breaking — property removedlist_automations·page· ⚠ Breaking — property removedlist_automations·enabled_only— optional property addedlist_campaigns·filter· ⚠ Breaking — property removedlist_campaigns·limit— type integer → numberlist_campaigns·limit· ⚠ Breaking — now limited to 1, 10, 25, 50, 100list_campaigns·limit— minimum 1 → nonelist_campaigns·limit— maximum 100 → nonelist_campaigns·status— optional property addedlist_campaigns·type— optional property addedlist_fields·limit· ⚠ Breaking — type number → integerlist_fields·page· ⚠ Breaking — type number → integerlist_fields·filter· ⚠ Breaking — property removedlist_fields·keyword— optional property addedlist_fields·type— optional property addedlist_forms·limit· ⚠ Breaking — type number → integerlist_forms·limit· ⚠ Breaking — minimum none → 1list_forms·limit· ⚠ Breaking — maximum none → 100list_forms·page· ⚠ Breaking — type number → integerlist_forms·filter· ⚠ Breaking — property removedlist_forms·name— optional property addedlist_segments·limit· ⚠ Breaking — type number → integerlist_segments·limit· ⚠ Breaking — minimum none → 1list_segments·limit· ⚠ Breaking — maximum none → 100list_segments·page· ⚠ Breaking — type number → integerlist_subscribers·filter· ⚠ Breaking — property removedlist_subscribers·status— optional property addedschedule_campaign·scheduled_at· ⚠ Breaking — property removedschedule_campaign·delivery· ⚠ Breaking — required property addedschedule_campaign·schedule— optional property addedupdate_campaign·from· ⚠ Breaking — format none → "email"update_subscriber·fields.*— now accepts nullupdate_subscriber·fields.*· ⚠ Breaking — type any → string | number
Output schema changes
add_subscriber·(root)· ⚠ Breaking — output schema removedassign_subscriber_to_group·(root)· ⚠ Breaking — output schema removedcancel_campaign·(root)· ⚠ Breaking — output schema removedcreate_automation·(root)· ⚠ Breaking — output schema removedcreate_campaign·(root)· ⚠ Breaking — output schema removedcreate_field·(root)· ⚠ Breaking — output schema removedcreate_group·(root)· ⚠ Breaking — output schema removeddelete_campaign·(root)· ⚠ Breaking — output schema removeddelete_field·(root)· ⚠ Breaking — output schema removeddelete_form·(root)· ⚠ Breaking — output schema removeddelete_group·(root)· ⚠ Breaking — output schema removeddelete_segment·(root)· ⚠ Breaking — output schema removeddelete_subscriber·(root)· ⚠ Breaking — output schema removedfetch·(root)· ⚠ Breaking — output schema removedget_campaign·(root)· ⚠ Breaking — output schema removedget_campaign_subscribers·(root)· ⚠ Breaking — output schema removedget_form·(root)· ⚠ Breaking — output schema removedget_form_subscribers·(root)· ⚠ Breaking — output schema removedget_group_subscribers·(root)· ⚠ Breaking — output schema removedget_subscriber·(root)· ⚠ Breaking — output schema removedget_subscriber_activity·(root)· ⚠ Breaking — output schema removedget_subscriber_count·(root)· ⚠ Breaking — output schema removedimport_subscribers_to_group·(root)· ⚠ Breaking — output schema removedlist_automations·(root)· ⚠ Breaking — output schema removedlist_campaigns·(root)· ⚠ Breaking — output schema removedlist_fields·(root)· ⚠ Breaking — output schema removedlist_forms·(root)· ⚠ Breaking — output schema removedlist_segments·(root)· ⚠ Breaking — output schema removedlist_subscribers·(root)· ⚠ Breaking — output schema removedschedule_campaign·(root)· ⚠ Breaking — output schema removedsearch·(root)· ⚠ Breaking — output schema removedunassign_subscriber_from_group·(root)· ⚠ Breaking — output schema removedupdate_campaign·(root)· ⚠ Breaking — output schema removedupdate_field·(root)· ⚠ Breaking — output schema removedupdate_form·(root)· ⚠ Breaking — output schema removedupdate_group·(root)· ⚠ Breaking — output schema removedupdate_segment·(root)· ⚠ Breaking — output schema removedupdate_subscriber·(root)· ⚠ Breaking — output schema removed
Annotations
add_subscriber· title unset → "Add Subscriber"add_subscriber· destructiveHint unset → falseadd_subscriber· readOnlyHint unset → falseassign_subscriber_to_group· title unset → "Assign Subscriber to Group"assign_subscriber_to_group· destructiveHint unset → falseassign_subscriber_to_group· readOnlyHint unset → falsecancel_campaign· title unset → "Cancel Campaign"cancel_campaign· destructiveHint unset → falsecancel_campaign· readOnlyHint unset → falsecreate_automation· title unset → "Create Automation in MailerLite"create_automation· destructiveHint unset → truecreate_automation· idempotentHint unset → falsecreate_automation· openWorldHint unset → falsecreate_automation· readOnlyHint unset → falsecreate_campaign· title unset → "Create Campaign"create_campaign· destructiveHint unset → falsecreate_campaign· readOnlyHint unset → falsecreate_field· title unset → "Create Field"create_field· destructiveHint unset → falsecreate_field· readOnlyHint unset → falsecreate_group· title unset → "Create Group"create_group· destructiveHint unset → falsecreate_group· readOnlyHint unset → falsedelete_campaign· title unset → "Delete Campaign"delete_campaign· destructiveHint unset → truedelete_campaign· readOnlyHint unset → falsedelete_field· title unset → "Delete Field"delete_field· destructiveHint unset → truedelete_field· readOnlyHint unset → falsedelete_form· title unset → "Delete Form"delete_form· destructiveHint unset → truedelete_form· readOnlyHint unset → falsedelete_group· title unset → "Delete Group"delete_group· destructiveHint unset → truedelete_group· readOnlyHint unset → falsedelete_segment· title unset → "Delete Segment"delete_segment· destructiveHint unset → truedelete_segment· readOnlyHint unset → falsedelete_subscriber· title unset → "Delete Subscriber"delete_subscriber· destructiveHint unset → truedelete_subscriber· readOnlyHint unset → falsefetch· destructiveHint unset → falsefetch· idempotentHint unset → trueget_campaign· title unset → "Get Campaign"get_campaign· destructiveHint unset → falseget_campaign_subscribers· title unset → "Get Campaign Subscribers"get_campaign_subscribers· destructiveHint unset → falseget_form· title unset → "Get Form"get_form· destructiveHint unset → falseget_form_subscribers· title unset → "Get Form Subscribers"get_form_subscribers· destructiveHint unset → falseget_group_subscribers· title unset → "Get Group Subscribers"get_group_subscribers· destructiveHint unset → falseget_subscriber· destructiveHint unset → falseget_subscriber_activity· title unset → "Get Subscriber Activity"get_subscriber_activity· destructiveHint unset → falseget_subscriber_count· title unset → "Get Subscriber Count"get_subscriber_count· destructiveHint unset → falseimport_subscribers_to_group· title unset → "Import Subscribers to Group"import_subscribers_to_group· destructiveHint unset → falseimport_subscribers_to_group· readOnlyHint unset → falselist_automations· title unset → "List My Automations"list_automations· destructiveHint unset → falselist_automations· idempotentHint unset → truelist_automations· openWorldHint unset → falselist_campaigns· title unset → "List Campaigns"list_campaigns· destructiveHint unset → falselist_campaigns· idempotentHint unset → truelist_fields· title unset → "List Fields"list_fields· destructiveHint unset → falselist_forms· title unset → "List Forms"list_forms· destructiveHint unset → falselist_forms· idempotentHint unset → truelist_segments· title unset → "List Segments"list_segments· destructiveHint unset → falselist_segments· idempotentHint unset → truelist_subscribers· title unset → "List Subscribers"list_subscribers· destructiveHint unset → falselist_subscribers· idempotentHint unset → trueschedule_campaign· title unset → "Schedule Campaign"schedule_campaign· destructiveHint unset → falseschedule_campaign· readOnlyHint unset → falsesearch· destructiveHint unset → falsesearch· idempotentHint unset → trueunassign_subscriber_from_group· title unset → "Remove Subscriber from Group"unassign_subscriber_from_group· destructiveHint unset → falseunassign_subscriber_from_group· readOnlyHint unset → falseupdate_campaign· title unset → "Update Campaign"update_campaign· destructiveHint unset → falseupdate_campaign· readOnlyHint unset → falseupdate_field· title unset → "Update Field"update_field· destructiveHint unset → falseupdate_field· readOnlyHint unset → falseupdate_form· title unset → "Update Form"update_form· destructiveHint unset → falseupdate_form· readOnlyHint unset → falseupdate_group· title unset → "Update Group"update_group· destructiveHint unset → falseupdate_group· readOnlyHint unset → falseupdate_segment· title unset → "Update Segment"update_segment· destructiveHint unset → falseupdate_segment· readOnlyHint unset → falseupdate_subscriber· title unset → "Update Subscriber"update_subscriber· destructiveHint unset → falseupdate_subscriber· readOnlyHint unset → false
Protocol
- Latest MCP protocol revision 2025-06-18 → 2025-11-25
Bug fixes
- Campaigns created or updated with content through the server can now be opened in the MailerLite editor. Previously the editor asked you to pick a template instead of showing the existing content.
create_campaignnow returns a clearer error when the API responds with a 404, pointing to invalid group IDs or an unverified sender domain.list_subscribersnow requests 25 subscribers per page by default, which discourages assistants from paging through the whole list automatically.- Fixed an "Invalid URL string" error that could break the OAuth authorization flow.
Auth & transport
- The server now supports the MCP protocol revision 2025-11-25.
- The OAuth flow was updated to meet a new authorization requirement, and handling of incoming requests was corrected.
- The OAuth flow now supports resource indicators (RFC 8707).
- The server is now served from the
mcp.mailerlite.comdomain.
v2.2.2
Dec 4, 2025 · MCP protocol 2025-06-18 (also supports 2025-03-26, 2024-11-05, 2024-10-07) · ⚠ Breaking
This release fixes form responses failing validation when a form has no screenshot available.
Output schema changes
get_form·data.screenshot_url· ⚠ Breaking — now accepts nulllist_forms·data[].screenshot_url· ⚠ Breaking — now accepts nullupdate_form·data.screenshot_url· ⚠ Breaking — now accepts null
Bug fixes
- Retrieving, listing and updating forms no longer fails when a form has no screenshot; the screenshot URL is now returned as null in that case.
Auth & transport
- No changes.
v2.2.1
Dec 4, 2025 · MCP protocol 2025-06-18 (also supports 2025-03-26, 2024-11-05, 2024-10-07) · ⚠ Breaking
This release fixes the search tool for forms and campaigns and updates the OAuth provider library with security hardening for redirect handling.
Input schema changes
add_subscriber·groups[]· ⚠ Breaking — type string → objectadd_subscriber·groups[].id— optional property addedadd_subscriber·groups[].name· ⚠ Breaking — required property addedadd_subscriber·groups[].active_count— optional property addedadd_subscriber·groups[].sent_count— optional property addedadd_subscriber·groups[].opens_count— optional property addedadd_subscriber·groups[].open_rate— optional property addedadd_subscriber·groups[].clicks_count— optional property addedadd_subscriber·groups[].click_rate— optional property addedadd_subscriber·groups[].unsubscribed_count— optional property addedadd_subscriber·groups[].unconfirmed_count— optional property addedadd_subscriber·groups[].bounced_count— optional property addedadd_subscriber·groups[].junk_count— optional property addedadd_subscriber·groups[].created_at— optional property addedadd_subscriber·groups[].updated_at— optional property addedadd_subscriber·groups[]· ⚠ Breaking — additional properties restrictedbatch·requests[].body— type object → anybatch·requests[].body— additional properties allowed
Output schema changes
add_subscriber·groups[]· ⚠ Breaking — type string → objectadd_subscriber·groups[].id— optional property addedadd_subscriber·groups[].name— required property addedadd_subscriber·groups[].active_count— optional property addedadd_subscriber·groups[].sent_count— optional property addedadd_subscriber·groups[].opens_count— optional property addedadd_subscriber·groups[].open_rate— optional property addedadd_subscriber·groups[].clicks_count— optional property addedadd_subscriber·groups[].click_rate— optional property addedadd_subscriber·groups[].unsubscribed_count— optional property addedadd_subscriber·groups[].unconfirmed_count— optional property addedadd_subscriber·groups[].bounced_count— optional property addedadd_subscriber·groups[].junk_count— optional property addedadd_subscriber·groups[].created_at— optional property addedadd_subscriber·groups[].updated_at— optional property addedadd_subscriber·groups[]— additional properties restrictedget_campaign_subscribers·data[].subscriber.groups[]· ⚠ Breaking — type string → objectget_campaign_subscribers·data[].subscriber.groups[].id— optional property addedget_campaign_subscribers·data[].subscriber.groups[].name— required property addedget_campaign_subscribers·data[].subscriber.groups[].active_count— optional property addedget_campaign_subscribers·data[].subscriber.groups[].sent_count— optional property addedget_campaign_subscribers·data[].subscriber.groups[].opens_count— optional property addedget_campaign_subscribers·data[].subscriber.groups[].open_rate— optional property addedget_campaign_subscribers·data[].subscriber.groups[].clicks_count— optional property addedget_campaign_subscribers·data[].subscriber.groups[].click_rate— optional property addedget_campaign_subscribers·data[].subscriber.groups[].unsubscribed_count— optional property addedget_campaign_subscribers·data[].subscriber.groups[].unconfirmed_count— optional property addedget_campaign_subscribers·data[].subscriber.groups[].bounced_count— optional property addedget_campaign_subscribers·data[].subscriber.groups[].junk_count— optional property addedget_campaign_subscribers·data[].subscriber.groups[].created_at— optional property addedget_campaign_subscribers·data[].subscriber.groups[].updated_at— optional property addedget_campaign_subscribers·data[].subscriber.groups[]— additional properties restrictedget_form·data.groups[]· ⚠ Breaking — type string → objectget_form·data.groups[].id— required property addedget_form·data.groups[].name— required property addedget_form_subscribers·data[].groups[]· ⚠ Breaking — type string → objectget_form_subscribers·data[].groups[].id— optional property addedget_form_subscribers·data[].groups[].name— required property addedget_form_subscribers·data[].groups[].active_count— optional property addedget_form_subscribers·data[].groups[].sent_count— optional property addedget_form_subscribers·data[].groups[].opens_count— optional property addedget_form_subscribers·data[].groups[].open_rate— optional property addedget_form_subscribers·data[].groups[].clicks_count— optional property addedget_form_subscribers·data[].groups[].click_rate— optional property addedget_form_subscribers·data[].groups[].unsubscribed_count— optional property addedget_form_subscribers·data[].groups[].unconfirmed_count— optional property addedget_form_subscribers·data[].groups[].bounced_count— optional property addedget_form_subscribers·data[].groups[].junk_count— optional property addedget_form_subscribers·data[].groups[].created_at— optional property addedget_form_subscribers·data[].groups[].updated_at— optional property addedget_form_subscribers·data[].groups[]— additional properties restrictedget_group_subscribers·data[].groups[]· ⚠ Breaking — type string → objectget_group_subscribers·data[].groups[].id— optional property addedget_group_subscribers·data[].groups[].name— required property addedget_group_subscribers·data[].groups[].active_count— optional property addedget_group_subscribers·data[].groups[].sent_count— optional property addedget_group_subscribers·data[].groups[].opens_count— optional property addedget_group_subscribers·data[].groups[].open_rate— optional property addedget_group_subscribers·data[].groups[].clicks_count— optional property addedget_group_subscribers·data[].groups[].click_rate— optional property addedget_group_subscribers·data[].groups[].unsubscribed_count— optional property addedget_group_subscribers·data[].groups[].unconfirmed_count— optional property addedget_group_subscribers·data[].groups[].bounced_count— optional property addedget_group_subscribers·data[].groups[].junk_count— optional property addedget_group_subscribers·data[].groups[].created_at— optional property addedget_group_subscribers·data[].groups[].updated_at— optional property addedget_group_subscribers·data[].groups[]— additional properties restrictedget_subscriber·groups[]· ⚠ Breaking — type string → objectget_subscriber·groups[].id— optional property addedget_subscriber·groups[].name— required property addedget_subscriber·groups[].active_count— optional property addedget_subscriber·groups[].sent_count— optional property addedget_subscriber·groups[].opens_count— optional property addedget_subscriber·groups[].open_rate— optional property addedget_subscriber·groups[].clicks_count— optional property addedget_subscriber·groups[].click_rate— optional property addedget_subscriber·groups[].unsubscribed_count— optional property addedget_subscriber·groups[].unconfirmed_count— optional property addedget_subscriber·groups[].bounced_count— optional property addedget_subscriber·groups[].junk_count— optional property addedget_subscriber·groups[].created_at— optional property addedget_subscriber·groups[].updated_at— optional property addedget_subscriber·groups[]— additional properties restrictedget_subscriber_activity·data[].meta· ⚠ Breaking — type object → anyget_subscriber_activity·data[].meta— additional properties allowedget_subscribers_in_segment·data[].groups[]· ⚠ Breaking — type string → objectget_subscribers_in_segment·data[].groups[].id— optional property addedget_subscribers_in_segment·data[].groups[].name— required property addedget_subscribers_in_segment·data[].groups[].active_count— optional property addedget_subscribers_in_segment·data[].groups[].sent_count— optional property addedget_subscribers_in_segment·data[].groups[].opens_count— optional property addedget_subscribers_in_segment·data[].groups[].open_rate— optional property addedget_subscribers_in_segment·data[].groups[].clicks_count— optional property addedget_subscribers_in_segment·data[].groups[].click_rate— optional property addedget_subscribers_in_segment·data[].groups[].unsubscribed_count— optional property addedget_subscribers_in_segment·data[].groups[].unconfirmed_count— optional property addedget_subscribers_in_segment·data[].groups[].bounced_count— optional property addedget_subscribers_in_segment·data[].groups[].junk_count— optional property addedget_subscribers_in_segment·data[].groups[].created_at— optional property addedget_subscribers_in_segment·data[].groups[].updated_at— optional property addedget_subscribers_in_segment·data[].groups[]— additional properties restrictedlist_forms·data[].groups[]· ⚠ Breaking — type string → objectlist_forms·data[].groups[].id— required property addedlist_forms·data[].groups[].name— required property addedlist_subscribers·data[].groups[]· ⚠ Breaking — type string → objectlist_subscribers·data[].groups[].id— optional property addedlist_subscribers·data[].groups[].name— required property addedlist_subscribers·data[].groups[].active_count— optional property addedlist_subscribers·data[].groups[].sent_count— optional property addedlist_subscribers·data[].groups[].opens_count— optional property addedlist_subscribers·data[].groups[].open_rate— optional property addedlist_subscribers·data[].groups[].clicks_count— optional property addedlist_subscribers·data[].groups[].click_rate— optional property addedlist_subscribers·data[].groups[].unsubscribed_count— optional property addedlist_subscribers·data[].groups[].unconfirmed_count— optional property addedlist_subscribers·data[].groups[].bounced_count— optional property addedlist_subscribers·data[].groups[].junk_count— optional property addedlist_subscribers·data[].groups[].created_at— optional property addedlist_subscribers·data[].groups[].updated_at— optional property addedlist_subscribers·data[].groups[]— additional properties restrictedupdate_form·data.groups[]· ⚠ Breaking — type string → objectupdate_form·data.groups[].id— required property addedupdate_form·data.groups[].name— required property addedupdate_subscriber·groups[]· ⚠ Breaking — type string → objectupdate_subscriber·groups[].id— optional property addedupdate_subscriber·groups[].name— required property addedupdate_subscriber·groups[].active_count— optional property addedupdate_subscriber·groups[].sent_count— optional property addedupdate_subscriber·groups[].opens_count— optional property addedupdate_subscriber·groups[].open_rate— optional property addedupdate_subscriber·groups[].clicks_count— optional property addedupdate_subscriber·groups[].click_rate— optional property addedupdate_subscriber·groups[].unsubscribed_count— optional property addedupdate_subscriber·groups[].unconfirmed_count— optional property addedupdate_subscriber·groups[].bounced_count— optional property addedupdate_subscriber·groups[].junk_count— optional property addedupdate_subscriber·groups[].created_at— optional property addedupdate_subscriber·groups[].updated_at— optional property addedupdate_subscriber·groups[]— additional properties restricted
Bug fixes
- The search tool now returns results for forms and campaigns, which it previously did not handle correctly.
- Redirect URIs using dangerous schemes such as
javascript:,data:andvbscript:are now rejected during OAuth authorization, including variants using mixed case, whitespace or control characters. - An open redirect issue when completing OAuth authorization has been fixed.
Auth & transport
- OAuth redirect URI validation is stricter, as described above. Clients that register redirect URIs with non-standard pseudo-schemes may be rejected.
- The MCP handler now includes CORS support, including responses to preflight requests.
v2.2.0
Oct 10, 2025 · MCP protocol 2025-06-18 (also supports 2025-03-26, 2024-11-05, 2024-10-07)
This release contains no tool or schema changes and is mainly maintenance, with a new option to configure the API base URL.
No tool or schema changes.
Auth & transport
- No changes.
v2.1.9
Oct 9, 2025 · MCP protocol 2025-06-18 (also supports 2025-03-26, 2024-11-05, 2024-10-07)
This release contains deployment configuration changes only, with no changes to tool behaviour for clients of the server.
No tool or schema changes.
Auth & transport
- No changes.
v2.1.8
Oct 8, 2025 · MCP protocol 2025-06-18 (also supports 2025-03-26, 2024-11-05, 2024-10-07)
This release updates dependencies and internal schema handling, with no changes to the tools the server exposes.
No tool or schema changes.
Auth & transport
- No changes.
v2.1.7
Sep 29, 2025 · MCP protocol 2025-06-18 (also supports 2025-03-26, 2024-11-05, 2024-10-07)
This release adds search and fetch support to the MailerLite MCP server, which makes it compatible with clients that expect those two tools.
Tools
- Added:
fetch— Fetch full details for a MailerLite resource identified by the search tool. - Added:
search— Search MailerLite campaigns, groups, forms, and automations.
Auth & transport
- No changes.
v2.1.6
Sep 28, 2025 · MCP protocol 2025-06-18 (also supports 2025-03-26, 2024-11-05, 2024-10-07)
This release changes how the server registers its MCP resources internally, with no changes to tools, schemas or client-visible behaviour.
No tool or schema changes.
Auth & transport
- No changes.
v2.1.5
Sep 28, 2025 · MCP protocol 2025-06-18 (also supports 2025-03-26, 2024-11-05, 2024-10-07)
This release marks the read-only tools as such, so clients can tell which tools only fetch data and which can change it.
Annotations
get_automation_activity· readOnlyHint unset → trueget_campaign· readOnlyHint unset → trueget_campaign_subscribers· readOnlyHint unset → trueget_form· readOnlyHint unset → trueget_form_subscribers· readOnlyHint unset → trueget_group_subscribers· readOnlyHint unset → trueget_single_import· readOnlyHint unset → trueget_subscriber· readOnlyHint unset → trueget_subscriber_activity· readOnlyHint unset → trueget_subscriber_count· readOnlyHint unset → trueget_subscribers_in_segment· readOnlyHint unset → trueget_webhook· readOnlyHint unset → truelist_automations· readOnlyHint unset → truelist_campaign_languages· readOnlyHint unset → truelist_campaigns· readOnlyHint unset → truelist_fields· readOnlyHint unset → truelist_forms· readOnlyHint unset → truelist_groups· readOnlyHint unset → truelist_segments· readOnlyHint unset → truelist_subscribers· readOnlyHint unset → truelist_timezones· readOnlyHint unset → truelist_webhooks· readOnlyHint unset → true
Auth & transport
- No changes.
v2.1.4
Sep 28, 2025 · MCP protocol 2025-06-18 (also supports 2025-03-26, 2024-11-05, 2024-10-07)
This release has no user-visible changes beyond the tool annotation update published separately.
Annotations
get_automation· readOnlyHint unset → true
Auth & transport
- No changes.
v2.1.3
Sep 28, 2025 · MCP protocol 2025-06-18 (also supports 2025-03-26, 2024-11-05, 2024-10-07)
This release has no user-visible fixes and no changes to how the server behaves.
No tool or schema changes.
Auth & transport
- No changes.
v2.1.2
Sep 25, 2025 · MCP protocol 2025-06-18 (also supports 2025-03-26, 2024-11-05, 2024-10-07)
This release contains only dependency maintenance and no changes to tool behaviour that clients would notice.
No tool or schema changes.
Auth & transport
- No changes.
v2.1.1
Sep 23, 2025 · MCP protocol 2025-06-18 (also supports 2025-03-26, 2024-11-05, 2024-10-07)
This release contains an internal maintenance change only, with no changes to tools, schemas or client-facing behaviour.
No tool or schema changes.
Auth & transport
- No changes.
v2.1.0
Sep 23, 2025 · MCP protocol 2025-06-18 (also supports 2025-03-26, 2024-11-05, 2024-10-07)
This release reorganises the server's internal structure and updates dependencies, with no changes to tools or behaviour that clients would notice.
No tool or schema changes.
Auth & transport
- No changes.
v2.0.6
Sep 23, 2025 · MCP protocol 2025-06-18 (also supports 2025-03-26, 2024-11-05, 2024-10-07)
This release contains no user-visible changes to the MailerLite MCP server's behaviour; the commit list for v2.0.6 was empty, so there is nothing further to report.
No tool or schema changes.
Auth & transport
- No changes.
v2.0.5
Sep 23, 2025 · MCP protocol 2025-06-18 (also supports 2025-03-26, 2024-11-05, 2024-10-07)
This release is a maintenance update that simplifies how the server registers its tools internally, with no change to the tools clients see.
No tool or schema changes.
Auth & transport
- No changes.
v2.0.4
Sep 23, 2025 · MCP protocol 2025-06-18 (also supports 2025-03-26, 2024-11-05, 2024-10-07)
This release registers the server's resources and prompts so that MCP clients can discover and use them.
No tool or schema changes.
Bug fixes
- Resources and prompts defined by the server are now registered, so clients can list and retrieve them.
Auth & transport
- No changes.
v2.0.3
Sep 15, 2025 · MCP protocol 2025-06-18 (also supports 2025-03-26, 2024-11-05, 2024-10-07)
This release has no changes to tools or schemas and adds a production server URL.
No tool or schema changes.
Auth & transport
- A production server URL was added as an available endpoint for connecting clients.
v2.0.2
Sep 15, 2025 · MCP protocol 2025-06-18 (also supports 2025-03-26, 2024-11-05, 2024-10-07)
Initial release with 52 tools.
Tools
add_subscriberassign_subscriber_to_groupbatchcancel_campaigncreate_automationcreate_campaigncreate_fieldcreate_groupcreate_webhookdelete_automationdelete_campaigndelete_fielddelete_formdelete_groupdelete_segmentdelete_subscriberdelete_webhookforget_subscriberget_auth_statusget_automationget_automation_activityget_campaignget_campaign_subscribersget_formget_form_subscribersget_group_subscribersget_single_importget_subscriberget_subscriber_activityget_subscriber_countget_subscribers_in_segmentget_webhookimport_subscribers_to_grouplist_automationslist_campaign_languageslist_campaignslist_fieldslist_formslist_groupslist_segmentslist_subscriberslist_timezoneslist_webhooksschedule_campaignunassign_subscriber_from_groupupdate_campaignupdate_fieldupdate_formupdate_groupupdate_segmentupdate_subscriberupdate_webhook