MoEngage MCP connector
The MoEngage connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, 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.
- Connects over OAuth
- Free 14-day trial
- No credit card
Count users who lapsed 30 days after buying twice
Working in MoEngage with Elaichi
-
Get content guide
-
Search content blocks
-
Get content blocks by IDS
How to connect MoEngage to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
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 Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
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. 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.
MoEngage MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with MoEngage through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in MoEngage is logged.
-
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”
What connecting MoEngage gets you
6 screens from Elaichi, each doing one job for your MoEngage account.
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, Cursor or Microsoft Copilot
The agent
Ask MoEngage questions and get live answers.
Count a segment, check a draft, or find a content block without opening MoEngage.
Copy the endpoint
AI apps
One endpoint connects MoEngage to every client.
Claude, ChatGPT, Cursor, Microsoft Copilot, and Microsoft Copilot reach MoEngage through one governed endpoint, no SDK, no shared key.
Tool catalog
52 MoEngage tools, ready without writing code.
Campaigns, segments, content blocks, and previews, covered with no custom code to maintain.
Toolboxes
Every team gets its own MoEngage toolbox.
Lifecycle gets campaigns, Growth gets segments, Content gets blocks, each scoped to the team.
Shared connections
Share a MoEngage connection, never a credential.
One person connects MoEngage, teammates draft and count through it, nobody sees the login.
Audit log
Know who changed which MoEngage campaign.
Every draft, status change, and segment count is logged with who, when, and what.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
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 Jake Morgan
Approve Deny -
Post the digest
MoEngage
Queued
Workflows
A schedule drafts the weekly MoEngage digest.
Campaigns are fetched, grouped, drafted into a digest, approved by a person, then posted back.
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%
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.
Why connect MoEngage's MCP server through Elaichi
MoEngage builds and runs this MCP server. Elaichi sits in front of it, so MoEngage's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to MoEngage's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT, Cursor and Microsoft Copilot reach MoEngage's tools at the same Elaichi address as every other connected app. Nobody adds MoEngage's server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own MoEngage sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches MoEngage's server. By default, a tool MoEngage does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to MoEngage
MoEngage builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the MoEngage team.
For IT and engineering
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 | Free for one person; $15 per user per month on Gold. | 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.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting status changes or content block edits. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
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, Microsoft Copilot, 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, Microsoft Copilot, 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 of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot