This post was co-written with Ashwin Srinivasan, Nishan Das and Karthik Baile from MoEngage.
A marketing or product team member planning a weekend flash sale often opens three tools before writing a single line of copy. First they open the analytics dashboard to see what worked last time, then the content library to find the right tone, and then the campaign builder to build the campaign itself. Repeat that across email, push, SMS, and WhatsApp, and much of a marketing team’s week goes to navigating tools instead of making decisions.
The MoEngage Model Context Protocol (MCP) Connector gives an MCP-compatible assistant, such as Claude or ChatGPT, secure, tenant-scoped access to a brand’s segments, campaign history, and content library.
This capability points to a broader shift in software platforms. Beyond a user interface for business users and an API for engineering teams, a third layer is emerging, where a user describes an outcome in plain language and an agent carries out the steps across the platform. For a customer engagement platform, that means a capability already exposed as an API can become a tool an agent calls, and a campaign that once moved across several tools can move through one conversation instead.
MoEngage, the agentic customer engagement platform that more than 1,350 consumer brands use across channels including push, email, in-app, SMS, WhatsApp, and Rich Communication Services (RCS), set out to build this layer. MoEngage built Merlin AI, a set of artificial intelligence (AI) agents that work with live platform data.
Source link







