Umeng / 友盟+ MCP. Track retention and manage mobile campaigns via chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
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.
What your AI agents can do
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.
Your agent executes targeted or broadcast push messages and provides real-time delivery and click data.
Retrieves specific numbers for active users, new registrations, and key retention statistics across defined time periods.
Accesses custom event logs and session duration data to pinpoint exactly how users interact with the app.
Pulls high-level summaries of app performance, helping you track growth and identify major trends quickly.
Lists recent campaigns and cancels any pending or unscheduled push operations directly through the interface.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
Umeng / 友盟+ MCP Server: 10 Tools for Mobile Ops
These ten tools let your agent perform everything from sending targeted pushes to calculating detailed user retention rates.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Umeng / 友盟+ on Vinkius019d8494cancel push
Stops a push notification task that is currently pending in the system.
019d8494get active users
Retrieves the total count of mobile users who were active within a specified period.
019d8494get app summary
Pulls high-level analytics data, giving an overall summary of your application's performance and growth.
019d8494get duration stats
Calculates statistics on how long users spend in the app during a session.
019d8494get event data
Retrieves detailed logs for specific custom user actions or events within the application.
019d8494get new users
Gets metrics detailing how many new accounts have registered in your mobile app.
019d8494get push status
Checks the current status of a specific push notification task ID (e.g., 'Pending', 'Failed').
019d8494get retention
Calculates and returns user retention statistics, tracking how many users return over time.
019d8494list push tasks
Shows a list of all recent push notification tasks that have been run or scheduled.
019d8494send push
Sends a new push notification campaign using a defined template or custom message.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Umeng / 友盟+, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Umeng / 友盟+. 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.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Dashboard fatigue shouldn't dictate your workflow.
Right now, if you want to audit a campaign or check user health, you have to jump into the Umeng portal. You pull up the 'User Growth' tab for active users, then open the 'Behavioral Analysis' section to get session duration stats. Then, you copy-paste that data into a separate spreadsheet just to see how retention correlates with new registrations.
With this MCP server, your agent handles all those clicks and tabs automatically. You ask it to correlate metrics, and it runs `get_active_users` alongside `get_retention`, spitting out the clean summary right back to you.
Umeng / 友盟+ MCP Server: Send pushes instantly.
Before, scheduling a cross-functional blast meant drafting copy in one system, getting approval in another, and manually triggering the push via a third dashboard. It was slow, prone to human error, and always required multiple logins.
Now you just talk to your agent. You tell it what message to send, and it uses `send_push` to execute the campaign instantly—and provides real-time status updates. The friction point is gone.
What you can do with this MCP connector
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.
019d8495-27df-7216-936d-89ae3db7cfce 
How Umeng / 友盟+ MCP Works
- 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.
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.
Who Is Umeng / 友盟+ MCP For?
Growth Managers, Product Ops Engineers, and Data Analysts. This server helps people who are tired of jumping between dashboards—the ones who need real-time performance data and campaign execution without leaving their primary workspace.
Manages the push notification lifecycle; uses send_push to deploy campaigns and list_push_tasks to audit what's running.
Coordinates marketing pushes and monitors user health. They rely on get_retention and get_active_users to measure campaign impact.
Pulls system-wide mobile metrics for reporting, calling tools like get_event_data or get_duration_stats for specific behavioral deep dives.
What Changes When You Connect
- Stop clicking through five different dashboards. With this server, you ask your agent to run
get_retentionorget_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_pushwhile tracking the delivery status viaget_push_status. - Pinpoint user friction points instantly. Instead of guessing, ask for detailed logs using
get_event_datato see exactly what users are doing when they drop off. - Keep your campaigns clean and controlled. Use
list_push_tasksfirst, then usecancel_pushif 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_summarytool pulls together key metrics so you don't have to combine data from multiple sources.
Real-World 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'.
The Tradeoffs
Trying to get all metrics from one tool
Asking the agent simply for 'user data.' This is too vague and will only return a generic summary, missing critical details like specific event logs or retention cohort breakdowns.
→
Be specific. You need multiple tools working together. Ask for get_active_users combined with get_retention to get the full picture of user health.
Forgetting to check task status
Running send_push and assuming it worked instantly, only to find out later that the campaign failed or is stuck in 'pending' limbo.
→
Always follow a send operation with get_push_status to verify successful deployment before reporting success.
Confusing general data with behavior
Asking for the total number of users (get_active_users) when what you really need is why they left. This only gives a headcount, not insight.
→
To understand user behavior, use get_event_data or get_duration_stats. These tools tell you about actions, not just counts.
When It Fits, When It Doesn't
Use this server if your core need is monitoring mobile performance in the Chinese market and executing push campaigns. Specifically, if you regularly need to calculate user retention rates (get_retention), send targeted pushes (send_push), or audit custom events (get_event_data).
Don't use it if you are trying to analyze web traffic (you need a different analytics platform) or if your main goal is general market research. If you just need basic contact info, don't bother—this toolset only handles mobile performance metrics and push actions. It’s deep infrastructure data; treat it like one.
Common Questions About Umeng / 友盟+ MCP
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, 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.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.