MoEngage MCP connector
The MoEngage connector lets Claude, ChatGPT, Cursor, or the Elaichi agent draft campaigns, build segments, and check audience counts in MoEngage, with each person signed in as themselves and every action logged.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
52 tools
How to connect
How to connect MoEngage to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect MoEngage once
-
Open Connections, choose Add connection, and pick MoEngage.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in MoEngage. MoEngage's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
MoEngage MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
MoEngage MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
MoEngage MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect MoEngage to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with MoEngage through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Lifecycle marketing
Draft a campaign from a brief
Describe the win-back push or onboarding email you want, and the agent builds the draft in MoEngage, checks it against the content guide, and leaves it for you to review before anything goes live.
-
Growth
Size an audience before you commit
Ask how many users lapsed in the last 30 days but bought twice before, and get a live segment count from MoEngage without opening the segment builder.
-
CRM
Build a segment in plain language
Describe who you want to reach, and the agent turns it into a saved MoEngage segment with filters validated against the fields that actually exist.
-
Content
Reuse approved blocks instead of rewriting
Search the content blocks your team already approved, drop one into a draft, or edit a block once so every campaign that uses it picks up the change.
-
Product marketing
Preview a message as a real customer
Create a personalization preview to see how a message renders with a specific user's attributes, then send an inline test before the campaign is scheduled.
-
Marketing ops
Pause or resume campaigns on request
Update a campaign's status in MoEngage when a launch slips or a product issue comes up, with the change recorded against the person who asked for it.
Try asking
- “Count users who lapsed 30 days after buying twice”
- “Draft a win-back push for the lapsed buyers segment”
- “Find approved content blocks for the spring sale email”
Compare
Elaichi vs Zapier MCP vs Composio for MoEngage
All three can connect MoEngage to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over MoEngage tools | Allow or restrict single MoEngage tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per MoEngage call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
MoEngage tools for your AI agents
52 tools are ready to call through Elaichi's MCP endpoint the moment you connect MoEngage, governed by the same roles, restrictions, and audit log as everything else in Elaichi. MoEngage builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting MoEngage gets you
6 screens from the product, each doing one job for your MoEngage account.
The agent
Ask MoEngage questions and get live answers.
Count a segment, check a draft, or find a content block without opening MoEngage.
- campaigns
- segments
- content blocks
- previews
Ask Elaichi to work across your apps.
Count users who lapsed 30 days after buying twice
Draft a win-back push for the lapsed buyers segment
Find approved content blocks for the spring sale email
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint connects MoEngage to every client.
Claude, ChatGPT, and Cursor reach MoEngage through one governed endpoint, no SDK, no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
52 MoEngage tools, ready without writing code.
Campaigns, segments, content blocks, and previews, covered with no custom code to maintain.
- Discover schema
- Create campaign draft
- Patch campaign components
- Validate campaign draft
ElaichiToolsToolboxes
Every team gets its own MoEngage toolbox.
Lifecycle gets campaigns, Growth gets segments, Content gets blocks, each scoped to the team.
- Lifecycle marketing
- Growth
- Content
- CRM
ElaichiToolboxesShared connections
Share a MoEngage connection, never a credential.
One person connects MoEngage, teammates draft and count through it, nobody sees the login.
- Lifecycle EMEA
- Growth
- Content
- CRM
ElaichiConnectionsAudit log
Know who changed which MoEngage campaign.
Every draft, status change, and segment count is logged with who, when, and what.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule drafts the weekly MoEngage digest.
Campaigns are fetched, grouped, drafted into a digest, approved by a person, then posted back.
MoEngage digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch campaigns
MoEngage
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
MoEngage
Queued
Collections and dashboards
MoEngage health numbers arrive without anyone asking.
Four metrics, 14 days of campaigns created, and a team breakdown, computed without a model.
MoEngage health
Refreshed 4 minutes ago · every 15 minutes · from the campaigns collection
Campaigns
1,284 ↓ 12%
Segments
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Campaigns created
Last 14 days
By team
Share of activity
Lifecycle EMEA 34%
Growth 27%
Content 21%
CRM 18%
FAQ
Frequently asked questions
How do I connect MoEngage to Claude?
Connect MoEngage in Elaichi first, which opens MoEngage's own OAuth sign-in, so you approve access in MoEngage and come straight back. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and MoEngage is available in Claude.
Does MoEngage work with ChatGPT and Cursor as well as Claude?
Yes. Once MoEngage is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi agent. You connect MoEngage once and every client sees it.
What can an AI agent actually do with my MoEngage data?
It can draft a campaign in MoEngage, change parts of it, validate it, create a personalization preview, send an inline test, and update its status. It can create and list segments, start a count and wait for the number, check that segment filters are valid, and suggest values for a field. It can also create, edit, and search content blocks and pull up the content guide. Short concrete asks, like 'count users who opened a push this week', work better than long paragraphs.
Does connecting MoEngage give the AI every campaign and segment in my workspace?
No. Every call runs as the person who signed in to MoEngage, so the agent sees the MoEngage campaigns, segments, and content blocks that person can already see and nothing more. Elaichi can narrow that further with roles and restrictions, and it never widens it.
Can I stop an agent from changing campaign status or editing content blocks in MoEngage?
Yes. Restrictions in Elaichi apply per action, so you can allow drafting and previewing in MoEngage while blocking status changes or content block edits. A restricted action is never advertised to Claude, ChatGPT, or Cursor, so no prompt can reach it.
What happens to a MoEngage connection when someone leaves?
Offboarding that person in Elaichi ends their MoEngage access at once, in every client. A MoEngage connection they had shared keeps working for everyone else on the team. Disconnecting MoEngage once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Does the MoEngage MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. MoEngage is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for MoEngage?
Yes. Both let Claude, ChatGPT or Cursor use MoEngage. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every MoEngage call.
How is Elaichi different from Composio for MoEngage?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to MoEngage: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put MoEngage in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.