moengage-mcp
This MCP server integrates with the MoEngage marketing platform, enabling headless management of campaigns and email templates via API-key authentication.
Campaign Management
Search & Retrieve: Search campaigns with filters (channel, status, delivery type, tags, date range) including full targeting/segmentation details. Retrieve campaign metadata (status, channel, reachability counts) and individual executions of recurring campaigns.
Personalized Previews: Render campaign content with
{{UserAttribute[...]}}and{{EventAttribute[...]}}placeholders resolved for sample data.Create & Update: Create Email or Push campaigns with extensive options (scheduling, segmentation, UTM, A/B testing, etc.) and patch existing campaigns with status-aware validation.
Lifecycle Management: Stop, pause, or resume 1–10 campaigns in a single call.
Testing: Send real test emails or push notifications to specific recipients.
Stats: (Currently disabled upstream) Performance statistics including delivery funnel and conversion goals.
Email Template Management
Search & Analyze: Search templates by name, ID, source, type, or creator. Parse a template's HTML into a structured content map (text nodes, images, Jinja expressions) without exposing raw HTML.
Compare: Structured diff of two templates' text content (e.g., original vs. translated).
Build & Publish: Compose and validate templates from components, then publish to MoEngage.
Update & Localize: Update existing templates, create translated/localized market variants (with RTL and image override support), or patch specific text nodes without a full rebuild.
Server Utilities
Retrieve server metadata including configured data center and dashboard base URL.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@moengage-mcpsearch for email campaigns targeting users who logged in this week"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
moengage-mcp
A Model Context Protocol (MCP) server for the MoEngage marketing platform. Exposes campaign and email-template tools over stdio, built on FastMCP.
Unlike MoEngage's official MCP (analytics-oriented, interactive OAuth), this server
uses the documented Campaign/Content API
with plain API-key auth — it runs headless, and it reads campaign targeting
(the full segmentation_details filter tree via search_campaigns), which the
official server does not expose.
Tools
Campaigns (9)
Tool | Mutates | Purpose |
| no | Search/filter campaigns; returns config including the full targeting filter tree ( |
| no | Thin identity view: status, channel, delivery type, team, tags, dates (no targeting) |
| no | Individual runs of a recurring (periodic) campaign |
| no | Render campaign content with placeholders resolved for sample attributes |
| no | ⚠ Disabled upstream — hidden unless |
| yes | Create a campaign |
| yes | Update campaign config |
| yes | Activate / pause / stop a campaign |
| yes | Send a real test push/email to named recipients |
Email templates (9)
Tool | Mutates | Purpose |
| no | Search templates with filters and pagination |
| no | Parse template HTML into structured content nodes |
| no | Structured diff of two templates |
| no | Build + validate a template, return a structured preview (no publish); |
| no | Data center + dashboard base URL |
| yes | Build + validate + publish to MoEngage |
| yes | Update an existing template |
| yes | Publish a translated market variant |
| yes | Modify specific text nodes without a rebuild |
Tools return structured previews, never raw HTML — large payloads would overflow an agent's context window.
Gating writes: the server ships all tools; restrict the mutating ones in
your MCP client (e.g. Claude Code permissions.allow listing only the read
tools). Read and write tools share MoEngage's campaign-API rate limits
(5/min, 25/hr, 100/day) — avoid fanning out calls.
Related MCP server: mcp-rule
Install & run
pip install git+https://github.com/poddubnyoleg/moengage_mcp.git
moengage-mcp # stdioClaude Code / Claude Desktop config:
{
"mcpServers": {
"moengage": {
"type": "stdio",
"command": "moengage-mcp"
}
}
}Configuration
Environment variables (or a local .env, see .env.example):
Variable | Required | Description |
| yes | Campaign/Content API key (dashboard → Settings → APIs) |
| yes | Workspace (app) ID |
| yes | Regional DC, e.g. |
| no | Brand links for the email footer component — inline JSON or a file path (schema in |
| no | Set |
API errors (including 401 on rotated keys) come back as structured error dicts, so a consuming agent can report them instead of failing opaquely.
Notes
content/email/TEMPLATE_GUIDELINES.mddocuments an example house style the template validator enforces (component order, CTA compliance, Jinja rules) — adapt to your brand.Audience reachability counts are only returned by MoEngage for one-time scheduled campaigns, not periodic ones.
License
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/poddubnyoleg/moengage_mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server