Skip the install. Get this working in under 2 minutes.
Start a free trial on cloud.anythingmcp.com, add the OneSignal in one click, then point your AI client (Claude, ChatGPT, Copilot or Cursor) at the generated MCP endpoint. No Docker, no git clone, zero engineering experience required.
Summary
Let your AI work with OneSignal: review sent push, email and SMS messages with their delivery results and outcomes, look up segments, users and templates, and send or schedule messages, cancel them, create segments and update user tags after you confirm.
Try asking
Example prompts for OneSignal
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → OneSignal, paste your credentials, mint an MCP API key and you're done. No Docker, no
git clone, no local server.
OneSignal
Let your AI work with OneSignal: review sent push, email and SMS messages with their delivery results and outcomes, look up segments, users and templates, and send or schedule messages, cancel them, create segments and update user tags after you confirm.
Setup
- In OneSignal open the app, then Settings → Keys & IDs. Copy the App ID (a UUID) into
ONESIGNAL_APP_ID. - On the same page click Add Key under App API keys, give the key a name and create it. The value starts with
os_v2_app_and is shown only once: paste it intoONESIGNAL_APP_API_KEYstraight away, without a Key prefix. - Install the connector and run
onesignal_view_app: it shows the app's name and subscription counts and checks that the App ID and the key belong together. The key works only for this app; for another app, install the connector again with that app's ID and key.
Who can do what: the key acts for the whole app, not for one person. Whoever uses the connector sees the app's users and, while the send tools are on, can send to its audience. Share the MCP server only with people allowed to do that.
What it reads: the app with its subscription counts, sent push, email and SMS messages with delivery counts and per-platform stats, outcomes (clicks, confirmed deliveries, sessions and your custom outcomes, kept about 30 days), segments, users by alias (usually external_id) with their tags and subscriptions, and message templates. onesignal_export_message_history has OneSignal build a CSV file of who received or clicked a message; sent events exist only for messages to 1,000 or more recipients.
Confirm first: onesignal_send_push, onesignal_send_email and onesignal_send_sms send real messages to real people, now or at a scheduled time. The AI shows you the content, the audience and the time first and sends only after you confirm; for a segment or more than one recipient it waits for an explicit "yes, send". onesignal_cancel_message stops a scheduled message, and onesignal_create_segment and onesignal_update_user (tags, language, timezone, country) also run only after you confirm. onesignal_delete_user is switched off at install.
Nobody matched: a send answers with the message id. An empty id means nobody matched the targeting, and the errors list says why, for example "All included players are not subscribed".
Common errors: 401 "Access denied": the key is wrong, deleted or rotated, or belongs to another app than the App ID. 400 "Failed to parse app_id": the App ID is not a valid UUID; copy it again from Keys & IDs. 400 on a send: the content or targeting is invalid, for example no English content, or segments combined with aliases. 403: the key is restricted by an IP allowlist, or your plan does not include the feature. 429: OneSignal's rate limit is reached; wait and try again.
The connector does not cover organization-level tasks (all apps, creating apps, managing API keys, audit logs), subscription and alias management, Live Activities, inbox messages, journeys, or CSV exports of all subscriptions and custom events.
Prerequisites: ONESIGNAL_APP_ID, ONESIGNAL_APP_API_KEY
Install the connector locally
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Open http://localhost:3000/connectors/store, pick OneSignal and paste in the env vars listed under Prerequisites.
Available tools
| Tool | What it does |
|---|---|
onesignal_view_app | Get the OneSignal app this connector is set up for: id, name, total and messageable subscriptions, created and updated times and… |
onesignal_list_messages | List the app's messages (push, email, SMS), newest first, 50 at most per page: id, name, contents or subject, segments, schedule… |
onesignal_view_message | Get one OneSignal message with its content, targeting, schedule, delivery counts, per-platform stats and, on request, outcomes (clicks… |
onesignal_view_outcomes | Get the app's outcome totals for the last hour, day or month: clicks (os__click.count), confirmed deliveries… |
onesignal_export_message_history | Start an export of who received (events sent) or clicked (events clicked) one message: OneSignal builds a CSV file and returns its download… |
onesignal_list_segments | List the app's segments: id, name, description, created and updated times, read-only and active flags |
onesignal_view_user | Get a OneSignal user by alias (usually external_id): identity aliases, properties (tags, language, timezone, country, first and last… |
onesignal_list_templates | List the app's message templates: id, name, created and updated times, optionally only push, email or SMS ones |
onesignal_view_template | Get one OneSignal template with its channel and content (headings, contents, email subject and body, platforms) |
onesignal_send_push | Send a push notification with OneSignal to segments (included_segments) or to specific users by alias (include_aliases with target_channel… |
onesignal_send_email | Send an email with OneSignal to segments (included_segments) or to specific users by alias (include_aliases with target_channel email), now… |
onesignal_send_sms | Send an SMS with OneSignal to segments (included_segments) or to specific users by alias (include_aliases with target_channel sms), now or… |
onesignal_cancel_message | Stop a scheduled or still outgoing OneSignal message; what was already delivered stays delivered |
onesignal_create_segment | Create a segment in the OneSignal app from filters on tags, sessions, language, app version, location or country |
onesignal_update_user | Update a OneSignal user's properties by alias (usually external_id): set tags (string key-value pairs) and language, timezone or country |
onesignal_delete_user | Permanently delete a OneSignal user with all aliases, properties and subscriptions, by alias |
Example prompts
- "Which push notifications did we send last week, and how many were delivered and clicked?"
- "Show me clicks and confirmed deliveries across the app for the last day, split by platform."
- "Look up the user with external_id 4821 and show me their tags and subscriptions."
- "Schedule a push to the Subscribed Users segment for Friday at 9:00 with the title Weekend sale, and show me content, audience and time before you send it."
Next steps
Was this guide helpful?
