MoEngage Team Explains: How a Multi-Tenant Platform Enables Secure AI Agent Data Access Without Rebuilding APIs
In a joint article with AWS, MoEngage explains how its Merlin AI uses FastMCP to convert existing OpenAPI specifications into MCP tools, achieves session isolation on the AgentCore runtime, and keeps tenant identity in request headers invisible to the model. The article outlines four agent modes, five tool categories, and three identity isolation design choices, while reporting customer-reported operational metrics.
A marketing team 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. This article, co-written by MoEngage and AWS, describes exactly how to compress this path into a single conversation—and the architectural choices behind it.
MoEngage's Merlin AI runs four groups of agents: dedicated agents embedded in Studio (Copywriter, Designer, Segment Assist, Jinja Assist, In-app Template Builder, Flow Assist), conversational agents spanning campaigns and analytics, continuously running agents customizable by CRM teams, and decisioning agents that make decisions for each individual customer. All four share the same foundation: foundation models on Amazon Bedrock handle reasoning and generation, the AgentCore runtime handles hosting, and MCP standardizes data access.
The core architectural question is: how to give agents secure, tenant-isolated access to real-time data without rebuilding hundreds of existing APIs. MoEngage's solution has three layers. The first is tool generation: its platform APIs are already compatible with OpenAPI 3.0, so the team used the FastMCP framework to generate MCP tools directly from the specification, turning each operation into a tool with structured schema, description, and parameter validation. Tools are grouped into five categories—campaign, analytics, segmentation, content, flow—and tool definitions update in sync when the specification changes.