OneSignal MCP for AI. Manage targeted alerts and user data from your chat.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
OneSignal MCP Server connects your AI agent directly to OneSignal's full suite of marketing and communication tools. Send targeted push notifications, manage complex user segments, dispatch emails, and track delivery metrics—all from a single chat interface.
Manage player data and campaign outcomes without ever logging into the OneSignal dashboard.
What your AI can do
Cancel scheduled alert
Stops a notification that was scheduled to send out at a specific time.
Send push notification
Sends an immediate, proactive push notification to a specified segment or list of players.
Remove player
Permanently deletes a specific user's device record from your active player database.
Send immediate push notifications, emails, or SMS messages to specific user segments.
Retrieve detailed profiles for individual users (players) and manage their device records.
List, check, and apply dynamic targeting criteria to your subscriber groups (segments).
Pull detailed delivery metrics, including open rates, click-through rates, and failure counts for past sends.
List recent notifications or cancel alerts that are set to go out at a later time.
Ask an AI about this
Waiting for input…
OneSignal MCP Server: 12 Tools for Communication & User Management
These tools allow you to manage everything related to user communication, from sending a single push alert to analyzing the performance metrics of entire campaigns.
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 OneSignal on VinkiusCancel Scheduled Alert
Stops a notification that was scheduled to send out at a specific time.
Send Push Notification
Sends an immediate, proactive push notification to a specified segment or list of...
Remove Player
Permanently deletes a specific user's device record from your active player database.
Get Api Status
Checks the current connection status and health of the OneSignal API integration.
Get App Details
Retrieves general information about your connected OneSignal application setup.
Get Notification Stats
Pulls detailed delivery metrics (opens, clicks) for a specific notification ID.
Get Player Details
Retrieves the complete profile and metadata for a single user device ID.
List Onesignal Apps
Requires a User Auth Key. Lists all OneSignal applications connected under an...
List Recent Notifications
Shows a list of the most recently sent or scheduled notification broadcasts.
List App Outcomes
Lists final outcomes or results from specific marketing campaigns run through...
List App Segments
Lists and describes the various pre-defined user groups or target segments available...
List App Players
Retrieves a list of all active device IDs that are currently subscribed to your app.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
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 OneSignal, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ 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 OneSignal. 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 connection provides 12 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Checking open rates used to require switching tabs and copying IDs.
Today, checking campaign success is a nightmare. You launch the alert, then you have to jump into the analytics tab, find the correct notification ID from the history list, wait for the report to load, and finally copy-paste three numbers (delivered, opened, clicked) into your presentation deck. It takes 15 minutes just to gather basic stats.
With this MCP server, you ask your agent: 'Show me the delivery analytics for last week's promotion.' The AI handles the ID lookup and data parsing using `get_notification_stats`. You get a single, summarized answer in the chat. Done.
OneSignal MCP Server lets you manage user profiles via the agent.
Used to update or check a user's profile meant logging into the admin panel, finding their device ID, navigating to the player management section, and manually updating tags. If you missed one click, the data was wrong.
Now, you just tell your agent: 'Get me the details for player 12345.' The `get_player_details` tool pulls everything—metadata, tags, status—and presents it instantly. You're talking to the data, not a dashboard.
What your AI can actually do with this
OneSignal MCP Server lets your AI client talk directly to OneSignal’s entire communication stack. You can send targeted alerts, check user profiles, and audit campaign results without ever opening the OneSignal dashboard. It gives you complete control over your push notifications, segments, and player data straight from your chat interface.
Dispatching Targeted Notifications
You use the send_push_notification tool to immediately send proactive alerts to specific groups or lists of players. Before sending anything out, you can check which target audiences are available by calling list_app_segments; this function shows you all the pre-built user segments in your account so you know exactly who you're hitting.
You also get a comprehensive list of every active device ID that’s subscribed to your app using list_app_players, ensuring nobody gets left behind.
Managing and Querying Player Data
If you need details on an individual user, the get_player_details tool pulls up the complete profile and all metadata for one specific device ID. Need a full list of those players? You use list_app_players again to pull that master roster. If a player moves or leaves, you can permanently wipe their record from your system using remove_player.
The server also lets you check the overall connection status and health of the OneSignal API integration by running get_api_status, so you know if everything's up and running.
Auditing Campaign Performance and History
You don’t just send messages; you track them. After a campaign runs, you can pull detailed delivery metrics—like how many users opened the message or what the click-through rate was—by calling get_notification_stats using a specific notification ID. You also get the final business outcome of large campaigns by running list_app_outcomes, which reports on the overall results for those sends.
To see recent activity, use list_recent_notifications; this shows you a list of both the most recently sent alerts and any broadcasts that are scheduled to go out later.
Controlling Scheduled Sends and Setup Checks
You gotta manage future blasts, too. If something needs to change, you can cancel an alert that was set to send at a specific time using cancel_scheduled_alert. Before relying on the system, you can get general information about your connected OneSignal application setup with get_app_details, or if your account manages multiple apps, you use list_onesignal_apps (which requires a User Auth Key) to see everything connected.
This server lets your agent handle every part of your communication stack—from listing all available segments via list_app_segments right down to checking the API status with get_api_status. You've got full control over sending, tracking, and cleaning up user data without leaving your chat client.
019dd131-f031-7107-8320-d849a12216c7 Here's how it actually works
The bottom line is: your AI client acts as an instant growth operations manager, letting you handle complex marketing tasks without ever opening multiple tabs or manually copying IDs.
Subscribe to the server and enter your OneSignal App ID and REST API Key into your AI client.
Ask your agent to perform an action, like 'Show me the performance metrics for campaign X.'
The agent calls the relevant tool (e.g., get_notification_stats), processes the data, and gives you a plain-text summary in the chat.
Who is this actually for?
Marketing Ops Managers and Growth Marketers who spend hours switching between dashboards to check metrics. Product Owners who need to automate transactional alerts based on user actions. If you're tired of manual logging to verify open rates or manually updating player tags, this is for you.
Uses list_app_segments and send_push_notification together to run A/B tests or launch flash sales instantly by targeting specific user groups.
Runs checks like get_player_details and list_app_players to maintain data integrity, ensuring every transactional notification hits the correct device record.
Uses tools like list_recent_notifications and get_notification_stats to report back on campaign success rates or troubleshoot delivery failures for key accounts.
What Changes When You Connect
Run full campaign audits without switching apps. Use get_notification_stats to instantly pull metrics like open rates and click-through rates for any notification ID, giving you immediate performance feedback.
Target users with precision. Instead of guessing, use list_app_segments to see your existing groups, then run send_push_notification on a defined segment—no manual list building required.
Maintain clean user data. If a player leaves or changes devices, you can run get_player_details first and then execute remove_player to keep your CRM accurate.
Automate alerts and cleanup. Use cancel_scheduled_alert if a sale ends early, or use list_recent_notifications to quickly check what went out yesterday.
Understand campaign success. If you run a major marketing push, call list_app_outcomes to see the final business result tied to that specific promotion.
See it in action
Running an emergency alert
The support team needs to warn users about a critical bug. Instead of manually listing every affected user ID, they ask their agent: 'Send a push notification using the segment named 'Beta Testers' with this message.' The agent executes send_push_notification immediately, reaching all 4,500 targeted devices in seconds.
Investigating low engagement
The growth manager sees that the last email campaign underperformed. They ask their agent to 'Check the metrics for notification ID ntf_8923.' The agent calls get_notification_stats, reports back that the click rate was only 14.8%, and helps the team determine if the targeting needs adjusting.
Cleaning up stale data
The product owner identifies a group of users who haven't logged in for six months. They first call get_player_details on three sample IDs to verify metadata, then use the agent to identify and execute remove_player calls across all inactive accounts, keeping the database clean.
Verifying segment structure
Before launching a major promotion, the marketing lead needs to know if their target group is defined correctly. They ask the agent to 'List all available segments,' which calls list_app_segments, allowing them to verify that the 'High-Value Customers' tag actually exists and has enough users.
The honest tradeoffs
Treating it like a basic messaging tool
The user just sends a message without defining who gets it, leading to either mass broadcast failure or sending the alert only to themselves.
Always start by checking your audience. Use list_app_segments first to verify the target group exists, and then run send_push_notification against that segment ID.
Ignoring data cleanup
The user sends a message but forgets about inactive users, leaving stale device records that clutter analytics and slow down future operations.
After reviewing player lists with list_app_players, proactively run get_player_details on sample IDs. If the data is clean, use remove_player for accounts confirmed as defunct.
Confusing listing with action
The user calls list_recent_notifications but then assumes that just seeing a notification in the list means it was successful. They don't know the actual delivery status.
First, use list_recent_notifications to get the ID of the alert they want to check. Then, pass that specific ID into get_notification_stats to see confirmed metrics.
When It Fits, When It Doesn't
Use this server if your core problem is omnichannel communication and user data management. You need to send targeted alerts (via send_push_notification) based on defined groups (list_app_segments), and you need a single place to audit the results (get_notification_stats).
Don't use this if your primary need is just simple, one-off email sending that doesn't rely on user metadata. For pure email management without push capabilities, an email service API wrapper is better. If your goal is complex backend logic (e.g., running a database query across multiple tables), you need a dedicated data access layer tool instead of this marketing wrapper.
Always confirm the recipient list using list_app_segments before sending. And if something goes wrong, always check system health first with get_api_status.
Questions you might have
How do I check if my connection is working with get_api_status? +
Run get_api_status first. It confirms your credentials and API key are valid, telling you immediately if the server can communicate with OneSignal.
What should I use to send a message to only 'VIP' users? +
Use list_app_segments first to confirm the 'VIP' segment exists. Then, call send_push_notification, referencing that confirmed segment ID for accurate targeting.
Can I delete a user record using remove_player? +
Yes, this tool permanently deletes a specific device ID from your player list. Use it when you know the user has abandoned the platform and their data needs to be scrubbed for compliance.
How do I view past alerts using list_recent_notifications? +
Run list_recent_notifications to see a history of all broadcasts. This gives you IDs you can then pass into the get_notification_stats tool for detailed performance analysis.
How do I use `list_onesignal_apps` to check my account connections? +
You must pass your User Auth Key to successfully list applications. This tool pulls a manifest of all OneSignal apps linked to your account, verifying which services are available for management through the server.
What specific metrics does `list_app_outcomes` provide for campaigns? +
This function retrieves deep performance data beyond simple counts. You get campaign outcomes like conversion rates and revenue attribution, allowing you to measure true business impact rather than just engagement volume.
How do I retrieve detailed user information using `get_player_details`? +
The tool pulls a comprehensive record for any player ID. It includes the device metadata (iOS/Android), custom tags, and last activity timestamp, giving you enough context to target highly specific groups.
What is the purpose of `cancel_scheduled_alert`? +
You pass a unique alert ID to stop any pending notification immediately. This feature lets you correct mistakes or pull back an unintended broadcast before it reaches users.
Can my AI automatically find the Player ID for a specific user to send a test push? +
Yes! Use the list_users tool. Your agent will respond with complete metadata for registered devices, including unique Player IDs and tags, allowing you to trigger targeted pushes instantly.
How do I find my OneSignal App ID and REST API Key? +
Log in to OneSignal, select your app, navigate to Settings > Keys & IDs, and you will find your unique App ID and secret REST API key there.
Can I use the AI to cancel a scheduled notification? +
Absolutely. Use the cancel_notification tool with the Notification ID. The agent will instruct OneSignal to stop the broadcast immediately, provided it hasn't been fully delivered yet.
We've already built the connector for OneSignal. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 12 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.