MailerLite
by MailerLite
Draft, schedule and send email campaigns to your subscriber list from chat, plus manage subscribers, groups and automations. One listed tool sends email to real people. 45 tools listed, OAuth sign-in, no scopes to decline.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect MailerLite via MCP
https://mcp.mailerlite.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
MailerLite Tools & Capabilities (45)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Sends cannot be recalled. MailerLite documents cancellation only for a campaign in the
readystate. An instant send has no undo, and no vendor page describes one. - No scopes to decline. All three RFC 9728 descriptor forms and the authorization server metadata omit
scopes_supportedentirely, verified live on 2026-08-20. There is no read-only grant, so the connection that lets an assistant read your open rates also lets it send. - No safety annotations are readable. The endpoint returns HTTP 401 to an anonymous handshake, so no
readOnlyHintordestructiveHintcould be checked. Every read/write judgement on this page is ours, derived from tool names and MailerLite's prose. - No parameter schemas either. For the same reason, this page publishes no
inputSchemadetail. Tool behaviour is described from the vendor's REST reference, which the MCP tools mirror by name. - The tool listing is 36 tools short of what MailerLite documents, so a capability absent from the 45 above is not necessarily absent from the server.
- It is beta. MailerLite's MCP page opens by calling this the beta version, so the tool set and behaviour may change without notice.
- Rate limits apply. MailerLite publishes a global limit of 120 requests per minute returning HTTP 429, and a separate limit of five requests per minute on import creation — which covers bulk subscriber import.
- You remain responsible for list hygiene. MailerLite's terms, quoted in its own getting-started page, place responsibility for preventing abuse on the account holder when subscribers are collected outside MailerLite's forms. An assistant importing a list does not shift that.
- Classic accounts are excluded. MailerLite documents that accounts created before 22 March 2022 run MailerLite Classic on API v1 or v2, which this API generation does not serve.
Frequently asked questions
Can the MailerLite MCP server actually send an email campaign?
Yes. `schedule_campaign` sends as well as schedules. MailerLite's campaigns reference documents the endpoint behind it as the way to schedule a campaign or send it immediately, and its `delivery` parameter accepts `instant` alongside the future-dated options. Choosing `instant` dispatches the campaign to its recipient list straight away. There is no separate send tool and no draft-only mode.
Can you undo a campaign that the assistant already sent?
No. MailerLite documents a cancel path only for a campaign still in the `ready` state, meaning one scheduled but not yet dispatched. Once delivery starts there is nothing to cancel, because the mail has left. `cancel_campaign` is therefore a genuine safety net for a scheduled send and no help at all for an instant one.
Can the connector trigger an automation that emails people?
Yes, indirectly, and this is the send path that is easy to miss. MailerLite documents `subscriber_joins_group` as an automation trigger type. Three listed tools put subscribers into groups, so adding someone to a group that an active automation watches starts that automation and sends its emails. No tool is named for sending.
What OAuth scopes does connecting MailerLite to Claude grant?
None are advertised. We read all three RFC 9728 descriptor forms plus the authorization server metadata on 2026-08-20, and not one of the four documents carries a `scopes_supported` key at all. The consent screen therefore has nothing to narrow: you cannot grant read access while withholding the ability to send a campaign or delete a subscriber.
What is the difference between delete_subscriber and forget_subscriber?
Retention. MailerLite documents `delete_subscriber` as removing someone from your account while keeping their information in case they re-subscribe. `forget_subscriber` removes them and completely deletes all their information within 30 days, and MailerLite describes it as the GDPR-compliant option. Both are listed tools, and neither prompts before running.
Do you need a paid plan to use the MailerLite MCP server?
On the Claude side, yes. MailerLite's own integration page states the connector works with Claude's Pro, Max, Team and Enterprise plans, which rules out Claude's free tier. MailerLite publishes no separate plan requirement on its own account, and its documentation labels the MCP server itself a beta release.
How many tools does the MailerLite MCP server have?
Anthropic's directory lists 45. MailerLite's own MCP page documents 76 by name, including 36 that the directory never mentions. The undisclosed set is not trivial: it holds a test-email sender, an automation-template installer, eight e-commerce dispatchers and several create and delete tools. We could not settle the live figure, because the endpoint requires OAuth.
Does MailerLite's MCP server let AI read my subscribers' email addresses?
Yes. Subscriber records are personal data, and the tools that return them hand full records to the assistant. MailerLite's own response examples show each subscriber carrying an email address, status, custom fields and engagement counts. Sixteen of the 45 listed tools touch subscriber records, and no advertised scope lets you withhold that access while permitting anything else.
Sources
- MailerLite MCP server documentation (retrieved 2026-08-20) · retrieved 2026-08-20
- MailerLite MCP example prompts (retrieved 2026-08-20) · retrieved 2026-08-20
- MailerLite campaigns API reference, including the schedule-or-send-immediately endpoint (retrieved 2026-08-20) · retrieved 2026-08-20
- MailerLite subscribers API reference, delete and forget semantics (retrieved 2026-08-20) · retrieved 2026-08-20
- MailerLite automations API reference, trigger types (retrieved 2026-08-20) · retrieved 2026-08-20
- MailerLite webhooks API reference, event catalogue (retrieved 2026-08-20) · retrieved 2026-08-20
- MailerLite getting started, rate limits and terms (retrieved 2026-08-20) · retrieved 2026-08-20
- MailerLite Claude integration page, client plan requirement (retrieved 2026-08-20) · retrieved 2026-08-20
- Full documentation corpus as Markdown (retrieved 2026-08-20, 30,792 words) · retrieved 2026-08-20
- Anthropic Connectors Directory entry (from the committed 2026-08-16 directory snapshot) · retrieved 2026-08-16
- Live OAuth posture check, RFC 9728 and RFC 8414 metadata on
mcp.mailerlite.com(2026-08-20) · retrieved 2026-08-20 - MailerLite support — · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Communication
- Developer
- MailerLite
- Tools
- 45
- Domain
- mcp.mailerlite.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.