Mailerlite MCP

Live

API KEY

EMAIL

Marketing

The Mailerlite MCP connector gives AI agents secure, per-user access to MailerLite — letting agents manage subscribers, groups, automations, and campaigns on behalf of the authorizing user. Every operation is tied to the MailerLite account owner who authorized the agent, keeping all email marketing actions fully auditable.

  • Acts as the user: Subscriber updates, campaign creates, and automation edits are tied to the MailerLite account owner who authorized the agent — not a shared service credential.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: Permissions enforced per-user. 90-day audit trail.
Mailerlite MCP
agent · Acme Q3
Run
List all my active subscribers and show me which groups they belong to.
S
subscribers_list
85ms
Mailerlite MCP agent
You have 1,240 active subscribers across 4 groups — your largest group is 'Newsletter' with 892 members.
Sources: 1,240 subscribers, all groups
mailerlitemcpmcp
1,240 subscribers
18:29
Message Claude...

Tools your marketing agent reaches for on Mailerlite MCP, scoped per user.

CALL ANY TOOL
Tools cover the core MailerLite operations available to agents — from listing subscribers and groups to managing automation email metadata and scheduling draft campaigns for delivery.
mailerlitemcp_add_subscriber
Add Subscriber
Add a new subscriber to your MailerLite account, optionally assigning them to groups and setting custom fields.
Parameters
Name
Type
Required
Description
email
string
Required
The email address of the subscriber
fields
object
Optional
Custom fields for the subscriber
groups
array
Optional
Group IDs to add the subscriber to
name
string
Optional
The name of the subscriber
resubscribe
boolean
Optional
Whether to resubscribe a previously unsubscribed subscriber
status
string
Optional
Subscriber status (default: active)
mailerlitemcp_assign_subscriber_to_group
Assign Subscriber To Group
mailerlitemcp_batch_requests
Batch Requests
mailerlitemcp_build_custom_automation
Build Custom Automation
mailerlitemcp_cancel_campaign
Cancel Campaign
mailerlitemcp_create_automation
Create Automation
mailerlitemcp_create_campaign
Create Campaign
mailerlitemcp_create_field
Create Field
mailerlitemcp_create_form
Create Form
mailerlitemcp_create_group
Create Group
mailerlitemcp_create_segment
Create Segment
mailerlitemcp_create_webhook
Create Webhook
mailerlitemcp_delete_automation
Delete Automation
mailerlitemcp_delete_campaign
Delete Campaign
mailerlitemcp_delete_field
Delete Field
mailerlitemcp_delete_form
Delete Form
mailerlitemcp_delete_group
Delete Group
mailerlitemcp_delete_segment
Delete Segment
mailerlitemcp_delete_subscriber
Delete Subscriber
mailerlitemcp_delete_webhook
Delete Webhook
mailerlitemcp_discover_automation_templates
Discover Automation Templates
mailerlitemcp_dry_run_automation
Dry Run Automation
mailerlitemcp_fetch
Fetch
mailerlitemcp_generate_email_content
Generate Email Content
mailerlitemcp_get_auth_status
Get Auth Status
mailerlitemcp_get_automation_activity
Get Automation Activity
mailerlitemcp_get_campaign
Get Campaign
mailerlitemcp_get_campaign_link_recipients
Get Campaign Link Recipients
mailerlitemcp_get_campaign_links
Get Campaign Links
mailerlitemcp_get_campaign_subscribers
Get Campaign Subscribers

For more tools, view docs.

Build your Agent
Same auth pattern across every framework.
Python · LlamaIndex
from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="mailerlitemcp")

mcp = MultiServerMCPClient({
"mailerlitemcp": {
"url": "https://mcp.scalekit.com/mailerlitemcp",
"headers": {"Authorization": "Bearer " + token}
}
})
tools = await mcp.get_tools()
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "mailerlitemcp" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/mailerlitemcp
// Pass: Authorization: Bearer + token
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "mailerlitemcp" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/mailerlitemcp
// Pass: Authorization: Bearer + token
from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="mailerlitemcp")
# Connect to MCP at https://mcp.scalekit.com/mailerlitemcp
# Pass: Authorization: Bearer + token
Try these prompts
Paste any prompt into your agent to get started.
Subscribers & groups
Copy the prompt
Copied
List all my active subscribers and show which groups each belongs to.
Copy the prompt
Copied
Show me all subscribers with 'bounced' status so I can clean my list.
Campaigns & automations
Copy the prompt
Copied
Create a new regular campaign called 'June Newsletter' with a welcome HTML email and schedule it to send tomorrow at 10am.
Copy the prompt
Copied
Get the full detail of my 'Welcome Series' automation and update the first email's subject line to 'Welcome — here's what to expect'.
SEE HOW AUTH WORKS
User authorises once. Every agent call after uses their token with scope enforcement.
1
Authorize
Your user connects
Mailerlite MCP
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Mailerlite MCP
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Mailerlite MCP
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Mailerlite MCP
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other connectors.
SALES
Outbound prospecting agent
Build targeted prospect lists with Apollo, enrich with firmographic data, and draft personalised outreach. Runs on a schedule.
GTM
HubSpot to Slack updates agent
Watch HubSpot deal stage changes and post structured updates to the right Slack channel. Reps stop checking the CRM all day.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought.
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.
// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access Mailerlite MCP as the user or as a shared key?
Scalekit resolves a per-user credential for each call. The Mailerlite MCP audit log shows the real user identity, not a shared service account.
Where is the Mailerlite MCP token stored?
In Scalekit's AES-256 encrypted vault, isolated per tenant. Tokens are auto-refreshed before expiry and revocable from a single dashboard without code changes.
Can I limit what the agent is allowed to do in Mailerlite MCP?
Pass a toolNames filter to listScopedTools. Scalekit enforces the allowed set before every API call — the agent cannot invoke tools outside the approved list.
What happens when a user revokes Mailerlite MCP access?
The token is invalidated at the next tool call. The agent fails closed rather than falling back to a shared key. Other users are unaffected and the revocation event is logged with a timestamp.
Can the agent send campaigns or create subscribers on behalf of any user in my system?
No. Each token Scalekit issues is scoped to the MailerLite account of the specific user who authorized the agent. A campaign created or subscriber added by the agent is tied to that account only. Cross-user operations require separate authorization flows, each recorded in Scalekit's audit log.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""mailerlitemcp"": {
""url"": ""https://mcp.scalekit.com/mailerlitemcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.mailerlitemcp]
url = ""https://mcp.scalekit.com/mailerlitemcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""mailerlitemcp"": {
""url"": ""https://mcp.scalekit.com/mailerlitemcp"",
""type"": ""http""
}
}
}