MoEngage MCP Server for CrewAIGive CrewAI instant access to 13 tools to Check Moengage Status, Get Campaign, Get Campaign Stats, and more
Connect your CrewAI agents to MoEngage through Vinkius, pass the Edge URL in the `mcps` parameter and every MoEngage tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.
Ask AI about this MCP Server for CrewAI
The MoEngage MCP Server for CrewAI is a standout in the Growth Engine category — giving your AI agent 13 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
from crewai import Agent, Task, Crew
agent = Agent(
role="MoEngage Specialist",
goal="Help users interact with MoEngage effectively",
backstory=(
"You are an expert at leveraging MoEngage tools "
"for automation and data analysis."
),
# Your Vinkius token. get it at cloud.vinkius.com
mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)
task = Task(
description=(
"Explore all available tools in MoEngage "
"and summarize their capabilities."
),
agent=agent,
expected_output=(
"A detailed summary of 13 available tools "
"and what they can do."
),
)
crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About MoEngage MCP Server
Connect your MoEngage account to any AI agent and manage customer engagement through natural conversation.
When paired with CrewAI, MoEngage becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call MoEngage tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
What you can do
- User Management — Create/update user attributes and device data
- Event Tracking — Track custom user events and behaviors
- Push Notifications — Trigger transactional and marketing push messages
- Campaign Management — Launch and pause multi-channel campaigns
- Analytics — Retrieve campaign performance and user statistics
The MoEngage MCP Server exposes 13 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 13 MoEngage tools available for CrewAI
When CrewAI connects to MoEngage through Vinkius, your AI agent gets direct access to every tool listed below — spanning customer-engagement, push-notifications, behavioral-analytics, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.
Check moengage status on MoEngage
Verify connectivity
Get campaign on MoEngage
Get campaign details
Get campaign stats on MoEngage
Get campaign stats
Get customer on MoEngage
Get customer details
Get segment on MoEngage
Get segment details
List campaigns on MoEngage
List campaigns
List segments on MoEngage
List segments
Search customers on MoEngage
Search customers
Send push on MoEngage
Send push notification
Track event on MoEngage
Track an event
Track events bulk on MoEngage
Track events in bulk
Update device on MoEngage
Update device info
Upsert customer on MoEngage
Create or update customer
Connect MoEngage to CrewAI via MCP
Follow these steps to wire MoEngage into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.
Install CrewAI
pip install crewaiReplace the token
[YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.comCustomize the agent
role, goal, and backstory to fit your use caseRun the crew
python crew.py. CrewAI auto-discovers 13 tools from MoEngageWhy Use CrewAI with the MoEngage MCP Server
CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with MoEngage through the Model Context Protocol.
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
MoEngage + CrewAI Use Cases
Practical scenarios where CrewAI combined with the MoEngage MCP Server delivers measurable value.
Automated multi-step research: a reconnaissance agent queries MoEngage for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff
Scheduled intelligence reports: set up a crew that periodically queries MoEngage, analyzes trends over time, and generates executive briefings in markdown or PDF format
Multi-source enrichment pipelines: chain MoEngage tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow
Compliance and audit automation: a compliance agent queries MoEngage against predefined policy rules, generates deviation reports, and routes findings to the appropriate team
Example Prompts for MoEngage in CrewAI
Ready-to-use prompts you can give your CrewAI agent to start working with MoEngage immediately.
"Show performance for the 'Spring Sale Push' campaign."
"Send a transactional push notification to user 8901."
"Track a 'Subscription Upgraded' event for user Sarah."
Troubleshooting MoEngage MCP Server with CrewAI
Common issues when connecting MoEngage to CrewAI through Vinkius, and how to resolve them.
MCP tools not discovered
Agent not using tools
Timeout errors
Rate limiting or 429 errors
MoEngage + CrewAI FAQ
Common questions about integrating MoEngage MCP Server with CrewAI.
How does CrewAI discover and connect to MCP tools?
tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.Can different agents in the same crew use different MCP servers?
mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.What happens when an MCP tool call fails during a crew run?
Can CrewAI agents call multiple MCP tools in parallel?
process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.Can I run CrewAI crews on a schedule (cron)?
crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.Explore More MCP Servers
View all →
Gitea
10 toolsManage self-hosted Git via Gitea — list and manage repositories, track issues and pull requests, handle organizations, and audit branches directly from any AI agent.

Guidebook
10 toolsAutomate mobile app content management via Guidebook — manage guides, sessions, speakers, and custom lists directly from any AI agent.

Marqo AI (Vector Search & Embeddings)
6 toolsManage semantic search via Marqo — execute tensor queries, index JSON documents, and audit vector indices.

EODHD Financial
10 toolsAccess real-time and historical stock market data — prices, fundamentals, dividends, splits and more for global exchanges.
