LABSCO SUMMARY
This connection can send push notifications to your users, which puts it in the same category as the WhatsApp one.
A misfired push reaches every device on a subscription list and cannot be recalled. The read-only tools — health, config, reference — are safe to leave connected and genuinely useful for checking configuration. The send path is guarded per their material, but treat the guard as a backstop rather than a policy: decide deliberately whether an agent should hold this at all.
What it is
OneSignal's hosted endpoint. Their official Cursor plugin is a wrapper around this same address, so the plugin and a direct connection reach the same tools.
What you get
- onesignal_health, onesignal_config, onesignal_reference_overview — read-only status and reference
- Sending and other write operations, which their material describes as guarded
Requirements
OAuth, or a OneSignal API key in the Authorization header.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Checking configuration
Health and config reads without any ability to send.
02
Looking up the API
The reference overview from the same connection you are building against.
03
Sending deliberately
The write path is guarded; treat it as a decision, not a convenience.
BEFORE YOU INSTALL
What to know first
Requires
- an MCP client that can reach a remote endpoint
- OAuth initiated by the client, or a OneSignal API key in the Authorization header
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://api.onesignal.com/mcp/oauthRequirements
- OAuth initiated by the client, or a OneSignal API key in the Authorization header