OneSignal MCP. Automate Comms, Check Metrics, & Manage Players.
OneSignal MCP lets you manage all customer push notifications directly from your AI agent. Send campaigns to segments, schedule messages, track delivery metrics (like open rates and failure reasons), and list specific player IDs—all without touching the OneSignal dashboard.
Give Claude and any AI agent real-world access
Send push notifications to specific segments or individual device IDs.
Schedule future messages or instantly cancel notifications that need pulling back.
Retrieve metrics and detailed reports on how many users received a message and if it failed, and why.
List all registered devices or check specific player details to verify an ID is active.
Ask an AI about this
Waiting for input…
What AI agents can do with OneSignal MCP with 10 Tools
Use these tools to manage everything from sending alerts to checking player records, all through simple conversation with your AI client.
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 MCPCancel Notification
Stops a scheduled alert from being delivered to users.
Create Notification
Sends an immediate or targeted OneSignal message.
Delete Player
Removes a specific device ID from the user's registered devices.
Get App
Fetches detailed configuration information for one of your OneSignal apps.
Get Notification
Retrieves the current status and details of a specific notification ID.
Get Outcomes
Pulls overall outcome data for your entire OneSignal application.
Get Player
Retrieves comprehensive details about a specific player device ID.
List Apps
Generates a list of every configured OneSignal application you have access to.
List Notifications
Lists all historical notifications that were sent for your app.
List Players
Provides a list of all registered device IDs currently tracked by OneSignal.
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 each 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,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
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 CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Managing customer communications used to be a dashboard nightmare.
Today, if you want to send an alert or check performance, you have to stop what you're doing. You click into the OneSignal portal, find the 'Send' button, select your audience segment from a dropdown menu, write the copy, hit schedule, and then maybe open a *second* tab just to see how many people opened it.
With this MCP, that whole sequence vanishes. You simply tell your agent what you want—a targeted message for new users today—and you get an immediate confirmation of its launch status. Everything happens in one conversation, meaning zero context switching.
The OneSignal MCP gives you command over comms.
You no longer have to manually retrieve lists of users or check if a specific message was delivered. You can ask the agent to pull all registered devices using `list_players`, and then immediately use that data to launch a campaign via `create_notification`.
It changes your work from an operational chore requiring multiple clicks into a direct conversation with measurable outcomes.
What OneSignal MCP does for your AI
Need to send an urgent announcement or check if a user actually saw that last promotion? This MCP connects your entire customer communication layer through natural conversation. You tell your agent what you need, and it handles the API calls for sending alerts across both mobile and web platforms. Need to target only high-value users who signed up in the last week? Just ask.
The agent will manage complex segmentation rules before launching the message. When you're done with the launch, you don't have to leave your workflow just to check metrics; you can fetch detailed reports on delivery status and engagement levels for any campaign. If you prefer a central place to connect all your operational tools, Vinkius brings this MCP alongside thousands of others, giving your agent one command center for everything.
It’s about getting immediate answers and executing complex comms strategies without ever opening the OneSignal web interface.
019d75e5-c99b-707d-b205-dc372a188057 How to set up OneSignal MCP
The bottom line is: you use natural language prompts to trigger complex communication actions and data retrievals managed by this MCP.
Subscribe to this MCP and provide your OneSignal REST API Key and App ID.
Optionally, supply a User Auth Key if you need full account control for listing all apps or managing configurations.
Start chatting with your AI client. You can then ask the agent to send an alert, check a user's status, or pull delivery reports.
Who uses OneSignal MCP
This connector is built for the Growth Marketing Manager who hates context switching, or the Support Agent who needs instant comms verification. If you spend time jumping between dashboards just to send an alert or check metrics, this MCP saves your afternoon.
Launching A/B tests for push notifications or scheduling a major product announcement across multiple segments.
Verifying whether a specific user received a critical system alert by checking their player ID metadata and delivery logs.
Testing notification payloads for new features and listing all current applications to maintain an overview of the communication stack.
Benefits of connecting OneSignal MCP
Launch messages instantly: Use the create_notification tool to send campaigns or alerts to any defined segment without leaving your chat environment.
Stop wasted effort: If a promotion needs pulling back, simply ask the agent to execute cancel_notification. It handles the scheduling logic immediately.
Know who saw it: Check delivery status for specific comms using get_notification or audit player details with get_player, providing immediate accountability.
Targeting made simple: The MCP allows you to run complex queries, such as listing all registered devices via list_players, ensuring your campaigns hit the right people.
Audit everything: Need a full picture of your comms infrastructure? Use list_apps and get_outcomes to review every configuration point in one chat session.
OneSignal MCP use cases
The marketing team needs to send an emergency update.
A manager realizes a critical bug is affecting users. Instead of logging into the web portal, they simply prompt their agent: 'Send a message about the outage now.' The agent uses create_notification and targets the 'All Users' segment instantly.
Support needs to prove delivery failure.
A user complains they never got a welcome email. A support specialist asks their agent to check the status of that notification using get_notification. The system replies with the exact metrics, confirming if it was sent and where it failed.
Developer needs to clean up old accounts.
A developer identifies a defunct testing account. They ask their agent to delete that player's record using delete_player so the test data doesn't clutter the active user list.
Product owner wants an infrastructure overview.
The PO needs to know what notification types exist. They prompt: 'List all connected apps and their details.' The agent runs list_apps and get_app, giving them a full, clean inventory.
OneSignal MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Checking delivery status manually
Having to navigate to the 'Analytics' tab in the OneSignal dashboard, then search for the specific notification ID and wait for reports to load.
Just ask your agent: 'What was the outcome of notification 550e8400...' The agent executes get_notification or get_outcomes instantly, giving you metrics without leaving your chat.
Sending a message to an unknown group
Trying to guess which segment of users are active. This often leads to sending messages to people who don't care and wasting resources.
First, ask the agent to run list_players to see what devices exist. Then, you can use that list information when calling create_notification, ensuring high-value targeting.
Trying to delete a player in multiple steps
Finding a device ID via the main dashboard, copying it, and then switching tabs to find the deletion tool.
Tell your agent: 'Delete this specific player.' The agent uses delete_player directly with the provided ID, keeping the entire process conversational.
When to use OneSignal MCP
Use this MCP if your core requirement involves managing user communication—sending alerts, tracking delivery status, or segmenting audiences. If you need to perform basic CRUD operations (like creating a new record in a CRM) or run complex financial calculations, this isn't the right tool; look for a database-type MCP instead. However, if you only need to read general user profile data without linking it to comms history, a dedicated user management tool is better suited. If your goal is simply to list what apps are available but never actually send anything, list_apps works, but remember that this MCP's strength lies in the action: launching communication and pulling metrics on those launches.
Frequently asked questions about OneSignal MCP
Can the OneSignal MCP send messages globally? +
Yes, it supports sending alerts to both mobile and web platforms. You only need to specify the target segment or user ID when calling create_notification.
What is the difference between list_players and get_player in OneSignal MCP? +
list_players returns a broad inventory of all registered device IDs. If you know the specific ID, use get_player to pull detailed metadata for that single player.
Does this MCP support scheduling future notifications? +
Yes. You can schedule messages using the capabilities exposed through create_notification, allowing you to plan campaigns days or weeks ahead of time.
How do I check if a user was successfully reached? +
You use the agent to fetch specific data by requesting the notification ID with get_notification. This gives you real-time status and delivery metrics for accountability.
Is there a way to mass delete users via OneSignal MCP? +
The toolset provides delete_player, which deletes one registered device at a time. You must list the players first using list_players and then pass them individually for deletion.