Skip to main content

The #1 agentic semantic tool search: 91.6% first-try accuracy on S1 Search Bench • Explore Tool Discovery →

Live 40 Actions

MoEngage MCP Server
for AI Agents

Connect your AI agent to StackOne's MoEngage MCP server and give it 40 MCP tools out of the box. Auth, tool execution, and security all managed.

Start Free Book Demo Read Docs →
MoEngage logo
MoEngage MCP Server
Built by StackOne StackOne
DrataGPLocalyzeFlipMindtoolsScreenloop

Coverage

40 Agent Actions

Create, read, update, and delete across MoEngage — and extend your agent's capabilities with custom actions.

MCP Actions → Build Actions →

Authentication

Agent Tool Authentication

Per-user OAuth in one call. Your MoEngage MCP server gets session-scoped tokens with zero credentials stored on your infra.

Agent Auth →

Security

Agent Protection

Every MoEngage tool response scanned for prompt injection in milliseconds — 88.7% accuracy, all running on CPU.

Prompt Injection Defense →

Performance

Max Agent Context. Min Cost.

Free up to 96% of your agent's context window to enhance reasoning and reduce cost, on every MoEngage call.

Tools Discovery →

What is the MoEngage MCP Server?

A MoEngage MCP server lets AI agents read and write MoEngage data through the Model Context Protocol — Anthropic's open standard for connecting LLMs to external tools. StackOne's MoEngage MCP server ships with 40 pre-built actions, fully extensible via the Connector Builder — plus managed authentication, prompt injection defense, observability, and agent execution runtime. Connect it from MCP clients like Claude Desktop, Claude Code, Cursor, Goose, and VS Code, or from agent frameworks like OpenAI Agents SDK, LangChain, and Vercel AI SDK.

All MoEngage MCP Tools

Every action from MoEngage's API, ready for your agent. Create, read, update, and delete — scoped to exactly what you need.

User (S2S)s

  • Export User (S2S)

    Export user (S2S)

  • Delete User (S2S)

    Delete user (S2S)

Campaigns

  • Search Campaigns

    Search campaigns

  • Update Campaign

    Update a campaign

Catalog Items

  • Search Catalog Items

    Fetch catalog items by id.

  • Update Catalog Items

    Update attributes of existing catalog items.

Content Blocks

  • Create Content Block

    Create a new content block in MoEngage

  • Update Content Block

    Update an existing content block in MoEngage

Custom Push Templates

  • Create Custom Push Template

    Create a new custom push notification template in MoEngage.

  • Update Custom Push Template

    Update an existing custom push notification template in MoEngage.

Custom SMS Templates

  • Create Custom SMS Template

    Create a new custom SMS template in MoEngage.

  • Update Custom SMS Template

    Update an existing custom SMS template in MoEngage.

Custom In-App Templates

  • Create Custom In-App Template

    Create a new custom in-app template in MoEngage.

  • Update Custom In-App Template

    Update an existing custom in-app template in MoEngage.

Other (26)

  • Create Event

    Create event

  • Create Business Event

    Create business event

  • Create / Send Campaign (asap, Scheduled, Weekly, Event-triggered, Business-event, Geofence, Device, Push-personalised)

    Create or send any MoEngage campaign — push, email, SMS, in-app, web-push — at any delivery mode

  • Create Catalog

    Create a new catalog in MoEngage

  • Add Catalog Attributes

    Add new attribute definitions to an existing catalog's schema.

  • Create File / CSV-Upload Segment

    Create a file-based custom segment from a public CSV URL

  • Create Filter Segment

    Create a filter/rule-based custom segment

  • Add Users To File Segment (CSV)

    Add users from a CSV file to an existing file/CSV-uploaded segment.

  • Create Email Template

    Create a new email template via the V2 email templates API in MoEngage.

  • Get Campaign Meta

    Get paginated campaign metadata. Filter by id, channel, status, name, tags or date ranges via campaign_fields.

  • Search / List Content Blocks

    Search content blocks in the workspace; returns content block IDs needed for update_content_block.

  • Get Specific Content Blocks By ID

    Fetch one or more content blocks by their IDs, including raw content.

  • Get Custom Segment By ID

    Retrieve a custom segment by its ID

  • List Custom Segments

    List all custom segments in the workspace

  • Get All Email Templates

    Retrieve all email templates in the MoEngage workspace.

  • Get Specific Email Template

    Retrieve a single email template by its ID.

  • Get User Subscription Preferences (READ)

    Get user subscription preferences

  • Update / Modify Filter Segment (Mutates)

    Update an existing filter-based custom segment

  • Update User Subscription Preferences (per-category, MUTATES)

    Update user subscription preferences

  • Delete Catalog Items (bulk)

    Delete items from a catalog in bulk.

  • Remove Users From File Segment (CSV)

    Remove users (listed in a CSV) from an existing file/CSV-uploaded segment.

  • Track User

    Track user

  • Merge User

    Merge user

  • Bulk / Batch Import Users + Events

    Bulk import

  • Trigger Business Event

    Trigger business event

  • Ingest Catalog Items

    Bulk-ingest items into a catalog.

MoEngage AI Agent Use Cases

Connect your AI agent to MoEngage and help your team scale the marketing operations they run by hand today.

Lead Nurture Sequences

Use StackOne to connect your AI agent to your marketing automation, CRM, and email tools to automate lead nurture email sequences.

View
HubSpotSalesforceActiveCampaignKlaviyoSendGridMailchimpLemlistGmail
Campaign Performance Reports

Use StackOne to connect your AI agent to your marketing automation, email, and analytics platforms to automate campaign performance reporting.

View
HubSpotMailchimpActiveCampaignKlaviyoSalesforceBrazeSendGridMarketo
Content Repurposing

Use StackOne to connect your AI agent to your document stores, email platforms, and messaging tools to automate content repurposing and distribution.

View
Google DriveConfluenceNotionMailchimpSendGridSlackGmailMicrosoft Teams
More Marketing Automation use cases

Set Up Your MoEngage MCP Server in Minutes

One endpoint. Any framework. Your agent is talking to MoEngage in under 10 lines of code.

MCP Clients

Claude Desktop setup guide
Claude Code setup guide
Cursor setup guide
Goose setup guide

Agent Frameworks

Claude Desktop
{
  "mcpServers": {
    "stackone": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?x-account-id=<account_id>",
        "--header",
        "Authorization: Basic <YOUR_BASE64_TOKEN>"
      ]
    }
  }
}

Check More Marketing Automation MCP Servers

Klaviyo

162+ actions

Zoho CRM

127+ actions

Intercom

113+ actions

HubSpot

106+ actions

SendGrid

100+ actions

Braze

98+ actions

Pardot

88+ actions

All Marketing Automation MCP Servers →

Platform Resources

MCP Code Mode: Keeping Tool Responses Out of Agent Context

Anthropic's code_execution processes data already in context. Custom MCP code mode keeps raw tool responses in a sandbox. 14K tokens vs 500.

11 min

Comparing BM25, TF-IDF, and Hybrid Search for MCP Tool Discovery

Benchmarking BM25, TF-IDF, and hybrid search for MCP tool discovery across 916 tools. The 80/20 TF-IDF/BM25 hybrid hits 21% Top-1 accuracy in under 1ms.

10 min

Indirect Prompt Injection Defense for MCP Tools: A Technical Guide

MCP tools that read emails, CRM records, and tickets are indirect prompt injection vectors. Here's how we built a two-tier defense that scans tool results in ~11ms.

12 min

MoEngage MCP Server FAQ

Does StackOne have a MoEngage MCP server?
Yes. StackOne offers a hosted MoEngage MCP server with 40 pre-built actions, and every action is tested and QA'd by StackOne. Connect it to Claude, Cursor, and any other MCP client, or to any agent framework through the AI Action SDK. It ships with managed agent authentication, prompt injection defense, and tool discovery with server-side execution that preserve your agent's context window and keep reasoning performance.
MoEngage MCP server vs direct API integration — what's the difference?
A MoEngage MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software — backend code calling MoEngage. A MoEngage MCP server is for AI agents — MCP clients like Claude and Cursor, plus framework agents built with OpenAI, LangChain, or Vercel AI — discovering and calling MoEngage at runtime. StackOne provides both.
How does MoEngage authentication work for AI agents?
MoEngage authentication for AI agents works through a StackOne Connect Session. Create one via the dashboard or the SDK — you get an auth link and ready-to-paste config for Claude Desktop, Cursor, and other MCP clients. Your user authenticates their own MoEngage account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via origin_owner_id.
Are MoEngage MCP tools vulnerable to prompt injection?
Yes — MoEngage MCP tools can be vulnerable to indirect prompt injection. Any tool that reads user-written content — documents, messages, tickets, records, or free-text fields — is a potential vector. StackOne Defender scans every tool response before it enters the agent's context — regex patterns in ~1ms, then a MiniLM classifier in ~4ms. 88.7% accuracy, CPU-only.
What is the context bloat of a MoEngage agent and how do I avoid it?
Context bloat happens when MoEngage tool schemas and API responses eat your MoEngage agent's memory, preventing it from reasoning effectively. A single MoEngage query can return a massive JSON response, and connecting multiple tools compounds the problem. Tools Discovery and Code Mode reduce context bloat — loading only relevant tools per query and keeping raw responses out of the agent's context.
Can I limit which actions my MoEngage agent can access?
Yes — you can limit which actions your MoEngage agent can access directly from the StackOne dashboard. Toggle actions on or off, or restrict them to specific accounts, with no code changes to your agent. Session tokens can be scoped to exact actions so if one leaks, exposure stays contained.
Can I create custom agent actions for my MoEngage MCP server?
Yes — you can create custom agent actions for your MoEngage MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research MoEngage's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a MoEngage MCP server?
Skip a MoEngage MCP server if your integration is purely software-to-software — direct MoEngage API integration is simpler when no AI agent is involved. For deterministic, compliance-critical operations (financial transactions, regulatory reporting), direct API gives you predictable behavior without agent-driven decision-making. MCP shines when AI agents need to dynamically discover and call MoEngage actions at runtime.
What AI frameworks and AI clients does the StackOne MoEngage MCP server support?
The StackOne MoEngage MCP server supports both. MCP clients (paste-and-go apps): Claude Desktop, Claude Code, Cursor, VS Code, Goose. Agent frameworks (code SDKs you build with): OpenAI Agents SDK, Anthropic, Vercel AI, Google ADK, CrewAI, Pydantic AI, LangChain, LangGraph, Azure AI Foundry.

Put your AI agents to work

All the tools you need to build and scale AI agent integrations, with best-in-class connectivity, execution, and security.

Start Free Book Demo