Mailercloud MCP connector for AI agents

Tools your agent reaches for on Mailercloud, scoped per user.

CALL ANY TOOL

Campaign analysis, audience health, and contact management: email marketing ops scoped per user.

mailercloudmcp_analyze_campaign

Deep-dive analysis of a single campaign's performance. retur

Deep-dive analysis of a single campaign's performance. returns a letter grade, weighted performance scores vs industry benchmarks, deliverability health assessment, contextual insights, and prioritized actionable recommendations to improve future sends.

Parameters

Name

Type

Required

Description

campaign_id

string

Required

The unique ID of the campaign.

api_key

string

Optional

Your MailerCloud API key for authentication.

cost_per_email

number

Optional

Optional cost per email sent, used to calculate ROI in reports.

mailercloudmcp_analyze_latest_campaigns

Analyze recent completed campaigns as a batch (default 5, up

mailercloudmcp_audit_campaign_draft

Pre-send quality audit for a campaign draft. checks subject

mailercloudmcp_batch_create_contacts

Create multiple contacts at once in bulk.

mailercloudmcp_campaign_health_dashboard

Quick portfolio-level health check across recent campaigns.

mailercloudmcp_compare_campaigns

Side-by-side comparison of two or more campaigns. shows perf

mailercloudmcp_create_campaign

Create a new email campaign in mailercloud. requires name, s

mailercloudmcp_create_contact

Create a new contact in a mailercloud list. email and list_i

mailercloudmcp_create_list

Create a new contact list in mailercloud.

mailercloudmcp_create_tag

Create a new tag for organizing contacts.

mailercloudmcp_create_template

Create a new html email template.

mailercloudmcp_create_webhook

Create a new webhook to receive event notifications.

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

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="mailercloudmcp")

mcp = MultiServerMCPClient({
    "mailercloudmcp": {
        "url": "https://mcp.scalekit.com/mailercloudmcp",
        "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: "mailercloudmcp" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/mailercloudmcp
// 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: "mailercloudmcp" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/mailercloudmcp
// 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="mailercloudmcp")
# Connect to MCP at https://mcp.scalekit.com/mailercloudmcp
# Pass: Authorization: Bearer + token

Try these prompts

Copy any prompt into your agent. Each maps directly to a Mailercloud tool. Click to copy, paste into your agent, done.

Get started

Copy the prompt

Copied

Create a contact if it doesn’t exist, or update it if it does?

Copy the prompt

Copied

Update an existing webhook’s configuration?

Advanced

Copy the prompt

Copied

Enable or disable a webhook?

Copy the prompt

Copied

Send a transactional email via MailerCloud Email API?

SEE HOW AUTH WORKS

Your users connect once. Their Mailercloud credentials stay vaulted, every call is scope-checked, and every action is logged.

Authorize

Your user connects

Mailercloud 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

Store

Their

Mailercloud 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

Resolve

When your agent calls a

Mailercloud 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

Audit

Every

Mailercloud 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.

Apollo

View agent

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.

HubSpot

Slack

View agent

Why Scalekit

Secure your agent's access. Connectors ship in minutes

Other connector libraries treat auth as a demo afterthought. Scalekit starts with identity, scope enforcement, and audit. Connectors follow.

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

03.

Multi-tenancy is architectural

04.

One connector today. Ten tomorrow.

“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 Mailercloud as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Mailercloud OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Mailercloud?
Yes. Pass a tool name filter to listScopedTools so the marketing agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Mailercloud.

What happens when a user revokes Mailercloud access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent send email campaigns without review?
Only if you expose send tools. Campaign audit, analysis, and contact tools are separate from sends, so you can run a reporting agent that cannot touch a live audience.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit