moengage-mcp.yml

Documentation

Documentation link · transport

Tools

• discover_schema — Returns the exact request shape for a campaign type, component, template, or modifier — required and forbidden fields, a proven minimum example, and the rules for that type. Call before building any payload.
• create_campaign_draft — Create a campaign draft in one call.
• patch_campaign_components — Update one or more components of an existing draft.
• validate_campaign_draft — Dry-run the full publish validation against a draft without changing it; returns field-level errors.
• create_personalization_preview — Render personalization for sample users to spot-check content before creating.
• test_campaign_inline — Send a test message from an inline payload to verify content.
• test_campaign_by_draft_id — Send a test message for an existing draft to verify it.
• update_campaign_status — STOP, PAUSE, or RESUME an already-running campaign (not drafts).
• get_content_guide — Validated authoring guidance for content. Request a topic (jinja, email_html, email_deliverability) and an optional section.
• create_content_block — Create a reusable content block, such as a shared email footer.
• edit_content_block — Update an existing reusable content block.
• search_content_blocks — Find content blocks by label.
• get_content_blocks_by_ids — Fetch content blocks by ID.
• create_custom_segment — Create a custom segment from event and attribute filters.
• list_segments — Browse existing custom segments in the workspace.
• get_segment — Read a single segment's definition.
• start_segment_count — Kick off an async user count for a segment, including channel-level reachability.
• poll_segment_count — Poll for the result of an async segment count.
• get_value_suggestions — Get suggested values for an event or user attribute while building a segment.
• search_flows — Find flows by name, status, or other criteria.
• get_flow — Read a flow's configuration.
• get_flow_version — Read a specific version of a flow.
• get_flow_analytics — The flow-level health view — how the flow is performing overall.
• get_flow_channel_analytics — Channel-scoped analytics for a flow.
• update_flow_status — Pause or stop a flow.
• list_dashboards — List the analytics dashboards available in the workspace.
• get_dashboard — Return the full metadata for a single dashboard by ID.
• get_chart_data — Fetch the analytical data for a specific chart within a dashboard.
• search_campaigns — Search campaigns across all channels by name, status, ID, channel, delivery type, or date range. Status filters ACTIVE, DRAFT, EXPIRED, NOT_SENT, PAUSED, SCHEDULED, SENDING, SENT, STOPPED, UNDER_REVIEW, REJECTED.
• get_campaign — Fetch a single campaign's full configuration and content.
• get_campaign_meta — Fetch a single campaign's metadata.
• get_campaign_stats — Aggregate performance — delivery rate, opens, clicks, CTR, and channel-specific metrics. Up to 50 campaigns per call.
• get_detailed_campaign_stats — Breakdowns by conversion goal, device/platform, locale, and A/B variation.
• get_delivery_stats — The delivery funnel — reachable users, frequency-cap removals, send/delivery failures, and per-platform device stats.
• get_click_performance — Per-URL click breakdown, with total and unique counts.
• get_device_analytics — Performance by device dimensions — OEM, app version, or dormancy, with multi-dimensional splits.
• discover_analyze_schema — Returns the request shape for a behavior, funnel, or retention analysis.
• run_behavior_analysis — Analyze how users perform a chosen event over time.
• run_funnel_analysis — Measure conversion across an ordered sequence of events.
• run_retention_analysis — Measure how users return over time after a starting event.
• find_events — Discover trackable events in the workspace.
• find_event_attributes — Discover the attributes available on a given event.
• find_user_attributes — Discover user attributes available for targeting and analysis.
• submit_feedback — Report tool-quality issues back to MoEngage.

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.

Work with this as data

Every MCP server here is available over the APIs.io API and to AI agents over MCP.

curl "https://apis.io/api/v1/mcp/moengage-mcp-yml"

curl "https://apis.io/api/v1/mcp?limit=25"