How to Use the MoEngage MCP in Claude

Q: How do I configure the MoEngage MCP Server inside Claude Desktop?

You need to edit your local claudedesktopconfig.json file. Add the server configuration under your mcpServers block with your API credentials, then restart the desktop app to load the new tools.

Run MoEngage campaign checks and trigger push alerts directly from Claude Desktop or your web browser.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect MoEngage MCP to Claude Desktop

Create your Vinkius account to connect MoEngage to Claude Desktop and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup MoEngage with Claude Desktop

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Run live campaign diagnostics right inside Claude Desktop

Stop jumping back and forth between your terminal and the MoEngage dashboard. This MCP Server lets your local Claude Desktop app query campaign performance and check connection states directly using `check_moengage_status` and `get_campaign_stats`. Because Claude Desktop runs tools locally via stdio, you get instant feedback on active segments without exposing API keys to the public web. You can inspect campaigns like `get_campaign` and see exactly why a push notification is pending.

Track user events instantly from the Claude Web chat

If you're using claude.ai in your browser, you can plug in this remote connector to update customer profiles on the fly. Fire off test events using `track_event` and `track_events_bulk` to see how your segments respond in real time. Claude Web renders these interactive payloads directly in your chat window. You can modify user traits with `upsert_customer` and instantly verify the changes without writing a single line of backend script.

Draft and test push notifications in one conversational step

Claude Desktop lets you write a push notification draft and send it to your test device immediately. Your agent uses `send_push` and `update_device` to target specific test tokens without leaving the chat interface. You get a live preview of the message payload inside Claude. If the layout looks broken, tell the agent to tweak the JSON structure and fire another test run until the push renders perfectly on your test screen.

Setup guide

Set up MoEngage MCP in Claude Web or Desktop

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.
3

Start a conversation

Open a new chat. The MoEngage MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the MoEngage MCP configuration

Copy the JSON snippet on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under moengage-mcp.

json

{
  "mcpServers": {
    "moengage-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by MoEngage. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect MoEngage now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about MoEngage MCP in Claude Desktop

You need to edit your local `claude_desktop_config.json` file. Add the server configuration under your `mcpServers` block with your API credentials, then restart the desktop app to load the new tools.

Yes, you can connect to the MoEngage MCP Server on claude.ai by adding a custom connector in your integration settings. Paste your remote HTTPS server URL, and your browser-based Claude Desktop agent will immediately gain access to tools like `list_campaigns`.

No, when you run the server locally on Claude Desktop, your MoEngage keys stay on your machine. The desktop application executes the tools locally as subprocesses, keeping your admin credentials secure.

The server returns the raw API error from your MoEngage workspace. You can ask Claude to parse the failure reason, fix the bad payloads, and retry the batch using `track_events_bulk`.

When running tools via Claude Desktop, your customer profiles and device tokens are processed entirely in memory through your local stdio transport. No MoEngage data is cached locally or written to Claude's app logs.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript