# Umeng / 友盟+ MCP

> Umeng / 友盟+ connects your AI client directly to China's leading mobile analytics and push notification system. Use this server to send targeted pushes, track user retention (Day-7 rates), monitor active users, and audit app performance metrics without navigating complex dashboards. It turns deep mobile growth data into a natural conversation with your agent.

## Overview
- **Category:** marketing-automation
- **Price:** Free
- **Tags:** mobile-analytics, push-notifications, user-retention, campaign-management, growth-hacking

## Description

**Umeng+** connects your agent directly to Umeng's mobile analytics system. You don't gotta jump through complex dashboards or learn a new portal just to check numbers; you talk straight to your data using plain English commands. It turns deep, hard-to-get mobile growth metrics into something natural for your AI client to pull out.

## Tools

### cancel_push
Stops a push notification task that is currently pending in the system.

### get_active_users
Retrieves the total count of mobile users who were active within a specified period.

### get_app_summary
Pulls high-level analytics data, giving an overall summary of your application's performance and growth.

### get_duration_stats
Calculates statistics on how long users spend in the app during a session.

### get_event_data
Retrieves detailed logs for specific custom user actions or events within the application.

### get_new_users
Gets metrics detailing how many new accounts have registered in your mobile app.

### get_push_status
Checks the current status of a specific push notification task ID (e.g., 'Pending', 'Failed').

### get_retention
Calculates and returns user retention statistics, tracking how many users return over time.

### list_push_tasks
Shows a list of all recent push notification tasks that have been run or scheduled.

### send_push
Sends a new push notification campaign using a defined template or custom message.

## Prompt Examples

**Prompt:** 
```
Send a broadcast push saying 'Flash Sale starts now!' to all users.
```

**Response:** 
```
I've initiated the broadcast push for you. The task ID is '8821'. I'll monitor the delivery status and let you know once the distribution reaches your user base.
```

**Prompt:** 
```
Show me the active user metrics for today.
```

**Response:** 
```
I've retrieved your analytics for today. You currently have 15,200 active users, with a 5% increase compared to yesterday. Your average session duration is 4.5 minutes.
```

**Prompt:** 
```
What is the retention rate for users who joined last Monday?
```

**Response:** 
```
I've calculated the retention stats for that cohort. The Day-7 retention rate for users who joined last Monday is 28.5%, which is slightly above your project average of 25%.
```

## Capabilities

### Send and manage push notifications
Your agent executes targeted or broadcast push messages and provides real-time delivery and click data.

### Audit user growth metrics
Retrieves specific numbers for active users, new registrations, and key retention statistics across defined time periods.

### Analyze detailed user behavior
Accesses custom event logs and session duration data to pinpoint exactly how users interact with the app.

### Monitor overall application health
Pulls high-level summaries of app performance, helping you track growth and identify major trends quickly.

### Manage push tasks lifecycle
Lists recent campaigns and cancels any pending or unscheduled push operations directly through the interface.

## Use Cases

### Analyzing a campaign failure.
A marketing manager notices the Day-7 retention rate dropped after last week’s push. They ask their agent, 'What happened?' The agent runs `get_retention` and cross-references it with `get_event_data` to show that users stopped engaging right after a specific feature update, solving the mystery immediately.

### Launching an urgent sale.
The sales team needs to drop an immediate announcement. Instead of drafting and scheduling in a web portal, they tell their agent, 'Send a broadcast push saying 50% off for the next hour.' The agent uses `send_push` and confirms the task ID using `get_push_status`.

### Auditing app performance before QBRs.
A Product Ops engineer needs data on user activity. They ask their agent for a summary, running `get_app_summary`, and then narrow it down by requesting both the total new registrations (`get_new_users`) and average session length (`get_duration_stats`).

### Cleaning up failed tasks.
A developer sees a bunch of old, pending push campaigns. They use `list_push_tasks` to see the list, identify the outdated campaign, and then call `cancel_push` before anyone accidentally hits 'send'.

## Benefits

- Stop clicking through five different dashboards. With this server, you ask your agent to run `get_retention` or `get_active_users`, and the full data set comes back in one response.
- You can execute complex marketing flows without manual steps. Just tell your agent 'Send a flash sale push,' and it uses `send_push` while tracking the delivery status via `get_push_status`.
- Pinpoint user friction points instantly. Instead of guessing, ask for detailed logs using `get_event_data` to see exactly what users are doing when they drop off.
- Keep your campaigns clean and controlled. Use `list_push_tasks` first, then use `cancel_push` if you need to pull back a scheduled message before it goes live.
- Get the full picture of app health with one command. The `get_app_summary` tool pulls together key metrics so you don't have to combine data from multiple sources.

## How It Works

The bottom line is that you talk to your AI client like talking to a teammate; it handles the complex API calls to Umeng in the background.

1. Subscribe to this server and provide your Umeng App Key and App Master Secret.
2. Connect your preferred AI client (like Claude or Cursor) to the MCP Server endpoint.
3. Ask your agent a question, such as 'Show me the Day-7 retention rate for last month' or 'Send a flash sale push now.' The agent executes the necessary tool calls and presents the results.

## Frequently Asked Questions

**How do I check if a push notification worked? (using get_push_status)**
Use `get_push_status` with the task ID. It tells you if the message is pending, sent, or failed, letting you know exactly what happened during distribution.

**What metrics does get_retention provide? (using get_retention)**
It provides user retention statistics, helping you track how many users return over time. This is key for figuring out if your campaigns are actually keeping people engaged.

**Can I see what happened right after a user signed up? (using get_event_data)**
Yes, `get_event_data` lets you retrieve logs for specific custom actions. You can pinpoint exactly which events users triggered shortly after their initial registration.

**How do I check if my push campaign is running? (using list_push_tasks)**
Calling `list_push_tasks` gives you a rundown of all recent campaigns. This is your central audit log for everything that's been pushed out.

**What’s the difference between get_app_summary and get_active_users? (using get_app_summary)**
The `get_app_summary` gives a broad, high-level overview of overall performance. `get_active_users` is more specific; it just pulls the current numerical count of active users.

**If I need to stop a push notification campaign immediately, how do I use the `cancel_push` tool?**
You call `cancel_push` with the task ID of the operation you want to halt. The agent confirms if the cancellation request is accepted by Umeng's system. This stops distribution instantly and prevents further messages from being sent out.

**How do I filter session duration data using `get_duration_stats`?**
You pass specific parameters to `get_duration_stats`, such as a date range or a user cohort identifier. The tool returns only the session metrics that match your criteria, giving you highly focused insights instead of general totals.

**When sending targeted messages, how does `send_push` handle segmentation?**
You must provide specific targeting parameters when calling `send_push`. This allows the tool to restrict delivery only to defined user segments (e.g., 'iOS users' or 'users in Texas'). It prevents general broadcasts and ensures precise messaging.

**How do I find my Umeng App Key and Master Secret?**
Log in to the [Umeng portal](https://www.umeng.com/), select your application from the dashboard, and you will find your App Key and App Master Secret in the application settings under 'App Info'.

**Does Umeng require different keys for iOS and Android?**
Yes. Umeng typically uses separate App Keys for different platforms. Ensure you authorize the correct key depending on which platform's analytics or push notifications you wish to manage.

**Can I cancel a push task through the agent?**
Yes! Use the `cancel_push` tool with the specific task ID. Your agent will communicate with Umeng to stop the delivery of any pending notification broadcast.