Understand this story
Using Amazon Bedrock AgentCore Gateway, MoEngage turned approximately 400 internal REST APIs distributed across private VPCs in 7 AWS Regions into permission-controlled agent tools. This approach requires no MCP server code from product teams and no separate network configuration for each integration, and there are no public endpoints anywhere in the path. According to an article published by AWS Machine Learning, this saved about 6 months of platform engineering effort and shortened new API onboarding from days to hours. MoEngage also established a principle: each engineering team maintains only the OpenAPI spec, while the AI platform team is uniformly responsible for the MCP layer.
AI-generated from public reports
Latest development · Report
How MoEngage Used AgentCore Gateway to Turn Over 400 APIs into Agent ToolsDevelopments
1 confirmed developments
MoEngage uses AgentCore Gateway to turn private APIs into Agent tools
Source:AWS Machine Learning
Reports and discussion timeline
Browse reports and discussion by time. Their evidence levels remain distinct.
Oct 30
AWS Machine LearningFirst-party
How MoEngage Used AgentCore Gateway to Turn Over 400 APIs into Agent Tools
Using Amazon Bedrock AgentCore Gateway, MoEngage converted approximately 400 internal REST APIs distributed across private VPCs in 7 AWS Regions into permission-controlled agent tools, saving about 6 months of platform engineering effort and reducing new API onboarding from several days to a few hours. The solution requires no MCP server code from product teams, no per-integration network configuration, and involves no public endpoints anywhere in the path. MoEngage also established a principle: engineering teams only maintain OpenAPI specs, while the AI platform team is solely responsible for the MCP layer.