ReadingResearchRadarInvestment framework
Sign in / Sign up
← Back to reading
NewsMaterial3 min readDisconfirmAI Editorial

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.

2026-11-17 02:16 GMT+8

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.

Sign in / Sign up
ReadingResearchRadarInvestment framework

The second layer is identity isolation, which represents the most specific design choices in the article. MoEngage implemented three measures: the MCP server reuses existing JWT authentication, with the AgentCore runtime validating tokens before requests reach the server; workspace and user context travel via request headers rather than tool parameters, meaning the model cannot see or modify these values; and each user session runs in an isolated environment within the AgentCore runtime, ensuring one user's conversation cannot read another's session state. The article notes that multi-tenant systems cannot allow models to decide whose data they are reading, and these three designs revolve around this principle.

The third layer is inference and generation: agents call Anthropic Claude Sonnet 4.6, 5, and 5.5 on Amazon Bedrock to plan tool calls, generate content, and summarize results. The MCP server itself does not run models; inference occurs within the agents calling it.

In a typical request, after a user logs into MoEngage and asks a question, the client sends the request carrying the user's existing JSON Web Token. The AgentCore runtime validates the token and starts an isolated session. The agent asks the Bedrock model which tools to call. The MCP server calls the MoEngage API with the user's tenant context and returns the results. The agent assembles the answer. Throughout this process, the user does not need to open separate dashboards.

Regarding performance, the data reported in the article are self-reported by MoEngage: customer Glance saw campaign go-live speed increase by 50%, push notification click-through rates improved by 38%, and content variant output was approximately triple the original rate; the platform overall reports a 60–70% reduction in manual workload for marketing and product teams regarding channel, timing, and frequency decisions, with goal-driven decisioning bringing a 20–30% improvement in conversion rates. These figures have not been independently replicated, nor do they provide sample sizes or control conditions.

The article concludes that the same pattern applies to other software providers with mature API surfaces: start from existing specifications, keep identity outside the model, and let managed runtimes handle production concerns. AgentCore runtime regional availability varies by AWS region. Framework agnosticism means MoEngage can swap models or agent frameworks without touching the MCP server—a benefit that also implies the current architecture remains coupled to the AgentCore runtime and that coupling has not yet been broken.

Sources

  • aws.amazon.comAmazon Web Services↗
Continue researching →