The OneSignal MCP connector routes your AI agent's tool calls to OneSignal's own MCP server through Scalekit. Each user signs in to OneSignal once, and Scalekit stores and refreshes their tokens, so your agent never handles credentials. It comes with 54 tools.
- Tools
- 54
- What they doRead · write · destructive
- 29 · 10 · 1529 read10 write15 destructive
- Users sign in with
- OAuth
- OAuth app
- Your own OneSignal MCP server app
Setup
Install the SDK
Terminal window npm install @scalekit-sdk/node dotenvTerminal window pip install scalekit-sdk-python python-dotenvSet your credentials
Add your Scalekit credentials to your
.envfile. Find values in app.scalekit.com > Developers > API Credentials..env SCALEKIT_ENVIRONMENT_URL=<your-environment-url>SCALEKIT_CLIENT_ID=<your-client-id>SCALEKIT_CLIENT_SECRET=<your-client-secret>Create the OneSignal MCP connection
In AgentKit > Connections, create an OneSignal MCP connection and copy its redirect URI. The name you give it is the
connection_nameyour code passes. See Configure connections.Register an OAuth app
OneSignal MCP server connections use your own OAuth app. Register one with OneSignal MCP server and add the redirect URI you copied.
Then enter the app's Client ID and Client Secret on the OneSignal MCP connection.
Authorize a user and make your first call
quickstart.mts import { ScalekitClient } from '@scalekit-sdk/node'import 'dotenv/config'import { createInterface } from 'node:readline/promises'const scalekit = new ScalekitClient(process.env.SCALEKIT_ENVIRONMENT_URL,process.env.SCALEKIT_CLIENT_ID,process.env.SCALEKIT_CLIENT_SECRET,)const actions = scalekit.actionsconst connector = 'onesignalmcp'const identifier = 'user_123'// Generate an authorization link for the userconst { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })console.log('Authorize OneSignal MCP:', link)const rl = createInterface({ input: process.stdin, output: process.stdout })await rl.question('Press Enter after authorizing...')rl.close()// Make your first callconst result = await actions.executeTool({connector,identifier,toolName: 'onesignalmcp_list_apps',toolInput: {},})console.log(result)Terminal window npx tsx quickstart.mtsquickstart.py import osfrom scalekit import ScalekitClientfrom dotenv import load_dotenvload_dotenv()scalekit_client = ScalekitClient(env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),client_id=os.getenv("SCALEKIT_CLIENT_ID"),client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),)actions = scalekit_client.actionsconnection_name = "onesignalmcp"identifier = "user_123"# Generate an authorization link for the userlink_response = actions.get_authorization_link(connection_name=connection_name,identifier=identifier,)print("Authorize OneSignal MCP:", link_response.link)input("Press Enter after authorizing...")# Make your first callresult = actions.execute_tool(tool_input={},tool_name="onesignalmcp_list_apps",connection_name=connection_name,identifier=identifier,)print(result)Terminal window python quickstart.pyEach user signs in once. See Authorize a user for the full flow and statuses.
Tools
Pass the exact name toexecute_toolonesignalmcp_check_send_volumeCheck whether an email send needs IP or domain warmup, given the sender domain and an estimated recipient count.Read-onlyCheck Send Volume
Check whether an email send needs IP or domain warmup, given the sender domain and an estimated recipient count. Nothing is saved. Mainly a step in the email drafting flow rather than something users ask for directly: call it whenever the draft is email, before recommending a send or a schedule. It also answers the same question after the fact, when diagnosing a send that went badly. Pass the recipient count that send actually reached and the domain it went out on, and the advice tells you whether it was large enough relative to the domain's history to have needed a ramp. It takes a recipient count and a domain, no draft required. The email_deliverability skill owns that flow. Returns advice (none, recommended, required, or unspecified), factors explaining the verdict (exceeds_volume_threshold, exceeds_peak_30_day_recommendation), and baseline sending history for the domain (peak_daily_volume_30d, peak_date, contributing_app_count, where the app count covers every app sending on that domain). Preserve the returned advice in the final user-facing summary, including after adding a ramp to an existing draft. If advice is required, explicitly say warmup is required or necessary; saying only that the ramp matters or describing the risks is not enough. If advice is recommended, present it as a recommendation instead. The recommended schedule name describes the stages, not the strength of this verdict. For a small enough send the check short-circuits to advice: none with a zeroed baseline, without consulting sending history. The threshold is decided by the API, so do not guess at it or quote a number. In that case say the send is too small to need warmup, and do not present the zeroed baseline as the domain's real sending history. If the API returns HTTP 400 with Something went wrong, do not retry the identical request. Check get_email_domains for the selected domain. Only call it deactivated when that state is explicitly returned; otherwise report that the check failed and the warmup verdict and baseline are unavailable. Do not infer no sending history from this error or from empty provider reports. A successful recommended_warm_up_schedule response is an app-based proposal, not a replacement domain-volume verdict.
Inputs
app_idstringrequired- OneSignal App ID.
estimated_recipientsintegerrequired- Estimated number of recipients for the send. Required.
sender_domainstringrequired- The actual sending domain, for example mail.example.com. Use a domain explicitly identified by the user and confirmed in get_email_domains, or the app's configured sending domain when available. A registered domain alone is not proof it is the default sender. If the sender is ambiguous, ask which domain. Do not infer it from a from address or silently substitute another domain. Check get_email_domains first: only state 2 (active) or 4 (manually_verified) is eligible for the domain-history lookup. State 1 (unverified) needs DNS verification; explain this prerequisite instead of running the check. State 3 (inactive) is deactivated. Do not treat a successful tiny-send check as proof of domain verification, because it skips the history lookup.
onesignalmcp_get_active_warm_up_schedulesList the email warmup ramps that are in flight for this app right now: which campaigns are ramping, and the app's combined day-by-day schedule with the planned quota and how much has actually gone out.Read-onlyGet Active Warm Up Schedules
List the email warmup ramps that are in flight for this app right now: which campaigns are ramping, and the app's combined day-by-day schedule with the planned quota and how much has actually gone out. Nothing is saved. Returns notifications, one entry per running warmup campaign with its id and title, and total_schedule, an ordered list of days with start, quota (recipients planned for that day across every running ramp) and acked (how many actually went out). An empty notifications list means no ramp is running. Two uses. Before proposing a new ramp, call this to see whether one is already running, because recommended_warm_up_schedule pushes a new schedule out past any warmup already in flight and the user should be told why their ramp starts later than they asked for. When diagnosing deliverability, call this to find out whether the window being judged overlaps a live ramp: a ramp holds sending volume down deliberately, so low send counts and thin per-provider samples during one are expected and are not evidence of a delivery problem. App-scoped and live-only. It covers every running warmup on this app and says nothing about ramps that have finished, been canceled, or are still sitting on a draft. Neither notifications nor total_schedule carries a sending domain, and the quota and acked totals are summed across every running ramp, so on an app that sends from more than one domain a live ramp here may belong to a different domain than the one being asked about. Do not attribute one domain's numbers to a ramp without saying the ramp is app-wide. For those, read kind and email_warm_up on get_notification for the specific campaign. Within a day that is still under way acked lags quota, so acked below quota is not on its own a sign the ramp is failing.
Inputs
app_idstringrequired- OneSignal App ID.
onesignalmcp_get_app_channel_availabilityGet enabled push, email, SMS, and In-App Messaging channels for an app.Read-onlyGet App Channel Availability
Get enabled push, email, SMS, and In-App Messaging channels for an app. Returns only channel availability, not credentials or platform configuration.
Inputs
app_idstringrequired- OneSignal app ID (UUID).
onesignalmcp_get_app_push_platformsRead which push platforms a OneSignal app already has credentials for.Read-onlyGet App Push Platforms
Read which push platforms a OneSignal app already has credentials for. Use it during SDK setup before `provision_app_credentials`, and to check an iOS project's Bundle ID against the stored one. Returns only the non-secret presence fields of the app object: `apns_env` (set when an APNs credential is stored), `apns_key_id` and `apns_team_id` (set for a `.p8` key, empty for a `.p12` certificate), `apns_bundle_id` (the Bundle ID the stored APNs credential serves), `fcm_sender_id` (set when FCM is configured), `chrome_web_origin` (set when web push is configured), `safari_site_origin` (set when Safari web push has its own certificate), and `channels.push.platforms` (the server's list of configured push platforms). Credential contents are never returned. Upstream errors (401, 403, 404) pass through unchanged.
Inputs
app_idstringrequired- The OneSignal app to read (UUID).
onesignalmcp_get_custom_eventsList the custom event definitions indexed for a OneSignal app, including each event's properties, sources, most recent occurrence, usage locations (segment/journey), storage and total counts, and retention duration.Read-onlyGet Custom Events
List the custom event definitions indexed for a OneSignal app, including each event's properties, sources, most recent occurrence, usage locations (segment/journey), storage and total counts, and retention duration. Requires OAuth authentication.
Inputs
app_idstringrequired- OneSignal app ID.
onesignalmcp_get_email_domainsGet email domain DNS verification status for the current app.Read-onlyGet Email Domains
Get email domain DNS verification status for the current app. Returns all registered email domains, each with a state and with its DNS records (SPF, DKIM, DMARC, MX, tracking CNAME). DNS records. Every record carries a status: 3 (or "passed") means verified/passing; anything else (or "failed") is not. Use these to check whether a domain's DNS is set up correctly before suggesting DNS setup steps. Domain state. Separate from the records, each domain has a state field. It is either numeric (1 unverified, 2 active, 3 deactivated, 4 manually verified) or a string, where "inactive" means deactivated. Never name a deactivated domain (state 3 or "inactive") when listing or suggesting domains, even if all of its DNS records pass, and do not offer to reactivate it. The only exception: when a send or check_send_volume has already failed on that exact domain, say plainly that it is deactivated, because that explains the failure. This domain state is NOT the same field as email_platform_state from get_email_setup_status, where "3" means active (a healthy, fully configured sender); do not carry these semantics across. An empty result here does not mean the sender is deactivated: a sender configured directly with a third-party provider (e.g. Mailgun) can return no domains. If get_email_setup_status is available, read email_platform_state on its own terms rather than applying the deactivated domain state. History interpretation. Domain state describes current verification, not whether this domain sent mail previously. An unverified domain does not prove zero historical sends or a zero sending baseline. When reporting or history is unavailable for this state, say that history cannot be retrieved until the domain is active; never say there is no sending history, that this is its first send, or that an empty report proves nothing was sent.
Inputs
app_idstringrequired- OneSignal App ID.
onesignalmcp_get_email_reputationRetrieve the app's overall (app-wide) email reputation summary: aggregate bounce rate and spam complaint rate across all sending, returned for the last 24 hours, 7 days, and 30 days.Read-onlyGet Email Reputation
Retrieve the app's overall (app-wide) email reputation summary: aggregate bounce rate and spam complaint rate across all sending, returned for the last 24 hours, 7 days, and 30 days. These are the same app-wide rates OneSignal's abuse-prevention system tracks to automatically warn or disable an app that has a high bounce or spam-complaint rate, so this is the right tool when the user asks about their sending or account health, whether they are at risk of being flagged, blocked, or disabled, or their standing with OneSignal. This is app-wide (all sending domains combined), not per-domain or per-provider. For per-domain or per-provider deliverability and reputation (e.g. how a domain is doing at Gmail, Apple, or Outlook), use get_provider_metrics instead, and do not combine the two; their numbers will not reconcile. Each rate is computed only over mail sent in its own window and the response has no counts, so the 24-hour rate can rest on a handful of sends on a quiet day and you cannot see how many. Say its volume is unknown, give the 7- and 30-day rates with it, and do not set the 24-hour figure beside per-provider counts. If the user quotes a rate these figures do not show, say they do not match and do not guess why (a spike that settled, a stale screen). Abuse prevention judges the trailing 30 days (or the time since email was last disabled, if shorter), not the 24-hour or 7-day windows. It warns at a complaint rate of 0.03% to 0.08% or a bounce rate of 2% to 5%, and disables email sending above 0.08% complaints or 5% bounces, but only with at least 10 complaints or 250 bounces, which this response cannot show. These are far stricter than the per-provider bands in get_provider_metrics, so a complaint rate those bands call Okay can still draw a warning. These thresholds apply only to the app-wide rates here; never measure a per-provider or per-domain rate against them. This is a summary, not a diagnosis: it tells you the rates are bad, never why. When the user wants the cause — mail going to spam, blocks, throttling, bounces, complaints, a drop in delivery — load the email_deliverability skill before going further. It owns choosing the scope, and the domain warmup check that decides whether suppressed volume is a ramp working or a real delivery problem.
Inputs
app_idstringrequired- OneSignal App ID.
onesignalmcp_get_journeyGet the complete public Journey graph and current concurrency key for an app and Journey.Read-onlyGet Journey
Get the complete public Journey graph and current concurrency key for an app and Journey.
Inputs
app_idstringrequired- OneSignal app ID (UUID).
journey_idstringrequired- Journey ID (UUID).
onesignalmcp_get_journey_schemaGet the JSON Schema for creating, duplicating, or updating a Journey or node.Read-onlyGet Journey Schema
Get the JSON Schema for creating, duplicating, or updating a Journey or node. Use the returned schema before the corresponding operation, or reuse the relevant schema already in context. For update_node, document=merged_node describes the node after applying the patch, not the patch itself. Additional REST API references: create (https://documentation.onesignal.com/reference/create-journey), duplicate (https://documentation.onesignal.com/reference/duplicate-journey).
Inputs
app_idstringrequired- App context for the authoring task. The schema is app-independent.
operationstringrequired- No description.one of
createduplicateupdateupdate_node
onesignalmcp_get_journey_statsGet public Journey and ID-keyed node, branch, and message statistics for an app and Journey.Read-onlyGet Journey Stats
Get public Journey and ID-keyed node, branch, and message statistics for an app and Journey.
Inputs
app_idstringrequired- OneSignal app ID (UUID).
journey_idstringrequired- Journey ID (UUID).
onesignalmcp_get_provider_metricsGet per-inbox-provider email deliverability metrics for a sender domain over a time window, broken down by provider (Gmail, Apple, Outlook, Yahoo, etc.).Read-onlyGet Provider Metrics
Get per-inbox-provider email deliverability metrics for a sender domain over a time window, broken down by provider (Gmail, Apple, Outlook, Yahoo, etc.). Returns raw counts per provider: sent, delivered, opened, clicked, unique_opened, unique_clicked, failed, bounced, complained. This is the source of truth for per-domain deliverability. It is scoped to a single sender domain (the required domain param): one app may send from several domains, and one domain may be shared across apps, so these numbers cover only the requested domain, not the whole app. Prefer it over get_email_reputation and get_email_stats (both app-wide) and do not blend them; their numbers will not reconcile — in particular, these are TOTAL counts while get_email_stats reports app-wide UNIQUE counts. If the user asks about email delivery or deliverability without naming a domain, ask which sending domain they mean (get_email_domains lists the app's domains) or make clear your answer covers one specific domain; do not present per-domain data as if it were app-wide. An empty providers array means no reportable data for this domain and window. It can also mean the domain was not found or is not active for sending; it is not proof that nothing was sent or that the domain has no sending history. Compute rates from the counts and state the numerator and denominator. Denominators are irregular: open rate = opened / delivered; complaint rate = complained / delivered; bounce rate = bounced / sent; failed rate = failed / sent. Use total opened, not unique_opened. Before assigning any band, check the provider's sent volume. If it is below 1,000, do not compute bands or give a reputation judgment for that provider. Say the sample is too small (only N sent) to assess reliably. This takes precedence over the bands below. Also check whether a domain warmup ramp was running over the requested window before you band anything. A ramp holds sending volume down deliberately, so it both starves providers of the sample the rule above needs and makes the window unrepresentative of how the domain normally sends. Call get_active_warm_up_schedules to find out; do not infer a ramp from the shape of the volume, and do not conclude there is none because the counts look ordinary. When one overlaps the window, report the counts, say the volume is suppressed by an active warmup rather than by an inbox provider, and do not band the affected providers. When the user is asking why deliverability is bad rather than what the numbers are, load the email_deliverability skill, which owns the full warmup check and the order to work the causes in. Judge each rate with these reputation bands. Open rate: Good >= 30%, Okay 20% to <30%, At risk 15% to <20%, Poor < 15%. Complaint rate: Good 0%, Okay >0% to <=0.1%, At risk >0.1% to <=0.3%, Poor > 0.3%. Bounce rate: Good < 1%, Okay 1% to <=5%, At risk >5% to <=10%, Poor > 10%. Failed rate: Good < 5%, Okay 5% to <=10%, At risk >10% to <=15%, Poor > 15%. Caveats. Apple never reports complaint data, so treat Apple's complaint rate as unavailable, not 0%, and never flag Apple on complaints. Gmail complaint counts here are Mailgun-sourced and unreliable (real Gmail complaint data lives in Gmail Postmaster Tools), so do not present a Gmail complaint rate from this data. Report the band as plain text (Good, Okay, At risk, Poor). Do not add emojis or icons. Use when the user asks how a domain is performing at inbox providers, wants to compare providers, or asks about sender reputation, bounces, or spam complaints.
Inputs
app_idstringrequired- OneSignal App ID.
domainstringrequired- The sender domain to report on.
endstringrequired- End of the reporting window, ISO 8601 timestamp.
startstringrequired- Start of the reporting window, ISO 8601 timestamp.
onesignalmcp_get_provider_metrics_timeseriesGet a time series of email deliverability metrics for a sender domain, totaled across the requested inbox providers (all providers when none are given).Read-onlyGet Provider Metrics Timeseries
Get a time series of email deliverability metrics for a sender domain, totaled across the requested inbox providers (all providers when none are given). Returns raw counts per time bucket: sent, delivered, opened, clicked, unique_opened, unique_clicked, failed, bounced, complained. Use when the user asks how a domain's deliverability is trending over time, or wants a chart. For a rate line, divide each bucket's numerator by its denominator using the same rules as get_provider_metrics (open and complaint over delivered; bounce and failed over sent). Render the series as a :::chart block. For a single reputation judgment over a whole window (for example 'how is my Apple failure rate' or 'has it improved since last week'), prefer get_provider_metrics over one or two windows rather than banding individual buckets; per-bucket rates are too noisy to band. A rising or stepped volume line is the expected shape of a domain warmup ramp, not a recovery or a problem. Before reading a trend as either, check whether a ramp covers the window: get_active_warm_up_schedules for one in flight, or kind and email_warm_up on get_notification for a specific campaign. Say when a ramp explains the shape rather than attributing it to inbox providers. An empty events array means no reportable data for this domain and window. It can also mean the domain was not found or is not active for sending; it is not proof that nothing was sent or that the domain has no sending history. Report any bands as plain text (Good, Okay, At risk, Poor). Do not add emojis or icons. This is the source of truth for per-domain deliverability trends. It is scoped to a single sender domain (the required domain param); one app may use several domains and one domain may be shared across apps, so it covers only the requested domain, not the whole app. These are TOTAL counts, whereas the app-wide get_email_stats reports UNIQUE counts — prefer this tool for per-domain trends, do not blend the two, and their numbers will not reconcile. If the user asks about email delivery trends without naming a domain, ask which sending domain they mean (get_email_domains lists the app's domains) or make clear the chart covers one specific domain, not the whole app.
Inputs
app_idstringrequired- OneSignal App ID.
domainstringrequired- The sender domain to report on.
endstringrequired- End of the reporting window, ISO 8601 timestamp.
startstringrequired- Start of the reporting window, ISO 8601 timestamp.
granularitystring- Time bucket granularity. Defaults to daily.one of
hourlydailymonthly providersarray- Exact API provider identifiers. For Outlook include outlook_365, outlook_eu and outlook_us; for Yahoo include yahoo_eu and yahoo_us. Gmail is gmail and Apple is apple. Generic outlook and yahoo are not valid. Omit to total across all providers. Multiple providers are summed into one series; call separately for each provider family when comparing trends. Use the identifiers returned by get_provider_metrics when available.
onesignalmcp_get_segmentRetrieve a single audience segment by ID.Read-onlyGet Segment
Retrieve a single audience segment by ID. By default, includes full segment metadata and filters (`payload` object with `id`, `name`, `created_at`, `source`, and `filters`). Set `include_segment_detail` to `false` to return only the subscriber count. Note: the API returns 400 for user-based segments (those using custom_event or message_event filters).
Inputs
app_idstringrequired- OneSignal app ID.
segment_idstringrequired- Segment ID to retrieve.
include_segment_detailboolean- If `true` (default), includes segment metadata and filters in the response (`payload` object with `id`, `name`, `created_at`, `source`, and `filters`). Set to `false` to return only the subscriber count.
onesignalmcp_get_templateRetrieve a single notification template by ID.Read-onlyGet Template
Retrieve a single notification template by ID.
Inputs
app_idstringrequired- OneSignal app ID.
template_idstringrequired- Template ID to retrieve.
onesignalmcp_get_user_identityRetrieve all identity aliases associated with a user.Read-onlyGet User Identity
Retrieve all identity aliases associated with a user. Identify the user by `alias_label` (typically "external_id") and `alias_id`.
Inputs
alias_idstringrequired- Alias ID value.
alias_labelstringrequired- Alias label used to look up the user. Typically `"external_id"`.
app_idstringrequired- OneSignal app ID.
onesignalmcp_get_user_identity_by_subscriptionRetrieve the identity aliases for the user who owns a given subscription.Read-onlyGet User Identity by Subscription
Retrieve the identity aliases for the user who owns a given subscription.
Inputs
app_idstringrequired- OneSignal app ID.
subscription_idstringrequired- Subscription ID.
onesignalmcp_list_appsList OneSignal apps accessible to the authenticated user.Read-onlyList Apps
List OneSignal apps accessible to the authenticated user. Returns app names, IDs, and organization info. Supports pagination via limit and offset parameters.
Inputs
limitinteger- Maximum number of apps to return. Defaults to 50; maximum allowed is 300.
offsetinteger- Pagination offset.
onesignalmcp_list_journeysList Journeys for an app using cursor pagination.Read-onlyList Journeys
List Journeys for an app using cursor pagination. Use next_cursor to request the next page.
Inputs
app_idstringrequired- OneSignal app ID (UUID).
cursorstring- Opaque cursor from the previous page.
limitinteger- Maximum number of Journeys, from 1 to 50.
onesignalmcp_list_messagesList push notifications for a OneSignal app.Read-onlyList Messages
List push notifications for a OneSignal app. Use `limit` (default 50, max ~250) and `offset` for pagination. Avoid large offsets — this endpoint has known performance degradation at high page numbers.
Inputs
app_idstringrequired- OneSignal app ID.
kindinteger- Filter by how the notification was created: `0` = Dashboard, `1` = API, `3` = Automated.
limitinteger- Maximum number of notifications to return. Defaults to 50. Max ~250.default
50 offsetinteger- Pagination offset.default
0 template_idstring- Filter by template ID (UUID v4).
time_offsetstring- ISO 8601 timestamp or Base64 integer token for cursor-based pagination (from previous response).
onesignalmcp_list_segmentsList audience segments for a OneSignal app.Read-onlyList Segments
List audience segments for a OneSignal app. Maximum 300 segments per page.
Inputs
app_idstringrequired- OneSignal app ID.
limitinteger- Maximum number of segments to return per page. Maximum 300.
offsetinteger- Pagination offset. Maximum 300 segments per page.
onesignalmcp_list_templatesList notification templates for a OneSignal app.Read-onlyList Templates
List notification templates for a OneSignal app. Maximum 50 per page.
Inputs
app_idstringrequired- OneSignal app ID.
channelstring- Filter by delivery channel (e.g. `"push"`, `"email"`, `"sms"`).
limitinteger- Maximum number of templates to return. Max 50 per page.
offsetinteger- Pagination offset.
onesignalmcp_onesignal_configReturn the current OneSignal MCP server configuration and connected app details.Read-onlyOneSignal Config
Return the current OneSignal MCP server configuration and connected app details.
Inputs
This tool takes no inputs.
onesignalmcp_onesignal_healthCheck the health status of the OneSignal MCP server.Read-onlyOneSignal Health
Check the health status of the OneSignal MCP server.
Inputs
This tool takes no inputs.
onesignalmcp_onesignal_reference_overviewReturn an overview of the OneSignal REST API reference, including available endpoints and rate limits.Read-onlyOneSignal Reference Overview
Return an overview of the OneSignal REST API reference, including available endpoints and rate limits.
Inputs
This tool takes no inputs.
onesignalmcp_read_skillsLoad OneSignal workflow guidance by name.Read-onlyRead Skills
Load OneSignal workflow guidance by name. Call this when a tool description or the user's request refers to a skill, before attempting the workflow. Available skills: - brand_kit: Apply the app's saved Brand Kit (colors, fonts, logos, tone) when generating or editing branded email or in-app message HTML. - brand_kit_profile: Apply the app's saved Brand Kit voice profile (tone, audience, language to avoid) when writing push or SMS copy. Plain-text channels only — no colors, fonts, or logos. - email_deliverability: Load before diagnosing an email deliverability problem the user is already having — mail landing in spam, blocked or throttled by an inbox provider, bounces, spam complaints, failed or suppressed recipients, a drop in delivery or opens, or poor sender reputation at Gmail, Apple, Outlook or Yahoo. Covers choosing the right scope, judging the rates, and working out whether domain warmup explains what they are seeing. - email_html: Brand-agnostic rules every generated or edited HTML email must follow — the unsubscribe-link token and mobile responsiveness — regardless of Brand Kit status, editor (create vs. edit), or prompt type. - email_warmup: Load before creating or sending an email campaign, to size the audience and decide whether the send needs domain or IP warmup. Covers large or first sends on a new or cold sending domain, the deliverability and sender-reputation risk of sending one un-ramped, ISP throttling and blocking, staged ramp schedules, and creating a draft with a warmup ramp on it or adding one to an existing draft. For a delivery problem that has already happened, load email_deliverability instead. - localize_messages: Load when the user wants a push, SMS, or email in more than one language: "translate this", "add Spanish and Turkish", "localize this email", "replace June with July in all languages". Covers a pasted draft, a template, or a sent message. Push and SMS variants are saved as a full language map only after the user confirms. An email asks how it will be sent, which languages, and what else to include. A Journey, or four languages or fewer, becomes one Liquid template. Five or more on an API or dashboard send becomes Dynamic Content.
Inputs
namesarrayrequired- Skill names to load.
onesignalmcp_recommended_warm_up_scheduleGet a recommended staged warmup schedule for an email send: when each stage starts and ends, and how many recipients it covers.Read-onlyRecommended Warm Up Schedule
Get a recommended staged warmup schedule for an email send: when each stage starts and ends, and how many recipients it covers. Nothing is saved. Email only. This is a step in the email drafting flow rather than something users ask for directly. Call it after check_send_volume returns advice of recommended or required, to answer what the warmup actually looks like. Returns items, an ordered list of stages with start, end, and quota (the number of recipients that stage sends to). Summarize the ramp and the date the full audience is reached rather than reciting every stage. The schedule starts at 9:00 AM in the time zone of user_time, tomorrow if it is already past 9:00 AM there, and is pushed later if an existing warmup campaign is already running, so the stages can begin after the date the user asked for. When they do, get_active_warm_up_schedules names the campaign holding that slot. Pass a later user_time only when the user has asked to start on a specific date. The baseline here is the app's own maximum daily delivered volume over the last three weeks, which is not the domain-wide 30-day peak that check_send_volume reports, so the two can differ. Do not present this schedule as domain-scoped.
Inputs
app_idstringrequired- OneSignal App ID.
total_recipientsintegerrequired- Total recipients the warmup has to ramp up to, the same count passed to check_send_volume. Required.
user_timestringrequired- The desired start time as an ISO 8601 timestamp including the user's UTC offset, for example 2026-08-04T09:00:00-07:00. Both the date and the offset are significant, because the schedule is built around 9:00 AM in that zone. Send the user's current local time unless they asked to start on a specific date. Required.
onesignalmcp_view_messageRetrieve a single notification by ID.Read-onlyView Message
Retrieve a single notification by ID.
Inputs
app_idstringrequired- OneSignal app ID.
notification_idstringrequired- Notification ID to retrieve.
outcome_attributionstring- Attribution type for the outcomes. Valid values: - `"direct"` - `"influenced"` - `"unattributed"` - `"total"`
outcome_namesarray- Outcome names to retrieve for this message, with aggregation type. Examples: - `"os__click.count"` for click counts - `"os__confirmed_delivery.count"` for confirmed deliveries - `"os__session_duration.sum"` for total session duration If you omit the `.count` / `.sum` suffix, `.count` will be appended automatically.
outcome_platformsstring- Platforms to include in the outcome data, represented as a comma-separated list of `device_type` integers (e.g. `"0,1,2,5,8,11,14,17"`).
outcome_time_rangestring- Time range for the returned outcome data. Valid values: 1h, 1d, and 1mo.
onesignalmcp_view_outcomesRetrieve outcome statistics for a OneSignal app (e.g.Read-onlyView Outcomes
Retrieve outcome statistics for a OneSignal app (e.g. click counts, session duration). Note: data retention is approximately 30 days.
Inputs
app_idstringrequired- OneSignal app ID.
outcome_namesstringrequired- Comma-separated outcome names to retrieve (e.g. `"os__session_duration.count,os__click.count"`). If any name contains a comma, pass each name separately in `outcome_names_array` instead.
outcome_attributionstring- Attribution type: `"direct"` or `"influenced"` or `"unattributed"`.
outcome_platformsstring- Comma-separated platform IDs to filter by (e.g. `"0,7"` for iOS + macOS).
outcome_time_rangestring- Time range for the returned data. Values: `"1h"`, `"1d"`, `"1mo"`. Defaults to `"1h"`.
onesignalmcp_view_userRetrieve a user and their properties by alias.Read-onlyView User
Retrieve a user and their properties by alias. Use `alias_label` "external_id" with the user's external ID, or another alias label you have configured.
Inputs
alias_idstringrequired- Alias ID value.
alias_labelstringrequired- Alias label used to look up the user. Typically `"external_id"`.
app_idstringrequired- OneSignal app ID.
onesignalmcp_create_custom_eventsRecord custom events for OneSignal users, such as purchases, content views, or milestones.WriteCreate Custom Events
Record custom events for OneSignal users, such as purchases, content views, or milestones. Use these to enter users into Journeys or trigger Wait Until nodes. Each event must set at least one of `external_id` or `onesignal_id`.
Inputs
app_idstringrequired- OneSignal app ID.
eventsarrayrequired- Array of event objects to record. Each event must have `name` and either `external_id` or `onesignal_id` set.
onesignalmcp_create_journey_draftCreate a Journey draft from the public writable create document.WriteCreate Journey Draft
Create a Journey draft from the public writable create document. Use client_node_id for local node references, not sending_node_id or server-assigned IDs. Before authoring, fetch get_journey_schema with operation=create, or reuse the relevant schema already in context. Pass draft fields inside the body object alongside app_id as native JSON, not JSON-encoded strings. Supplying a schedule does not activate the draft. For on_notification_action references, set the same client_node_id on the sending node and the condition.
Inputs
app_idstringrequired- OneSignal App ID.
bodyobjectrequired- Journey draft fields as native JSON values. Use the schema returned by get_journey_schema with operation=create.
onesignalmcp_create_segmentCreate a new audience segment with filter conditions.WriteCreate Segment
Create a new audience segment with filter conditions. Maximum 200 filter entries.
Inputs
app_idstringrequired- OneSignal app ID.
filtersarrayrequired- Segment filter conditions. Maximum 200 entries.
namestringrequired- Segment name.
onesignalmcp_create_subscriptionCreate a new subscription and attach it to a user.WriteCreate Subscription
Create a new subscription and attach it to a user. Set `type` to the channel ("Email", "SMS", "iOSPush", "AndroidPush", etc.) and `token` to the email address, E.164 phone number, or push token.
Inputs
alias_idstringrequired- Alias ID value.
alias_labelstringrequired- Alias label used to identify the user (e.g. `"external_id"`).
app_idstringrequired- OneSignal app ID.
subscriptionobjectrequired- Subscription to create.
onesignalmcp_create_templateCreate a new notification template for a OneSignal app.WriteCreate Template
Create a new notification template for a OneSignal app. If the user did not already say whether the template is push, SMS, or email, ask which channel they want and wait for the answer before calling this tool. Do not guess. A missing channel flag saves a push template. Push: set `contents`. SMS: set `contents` and `extra` to `{"isSMS": true}`. Email: set `email_subject` and `email_body`.
Inputs
app_idstringrequired- OneSignal app ID.
dynamic_contentobjectrequired- Dynamic Content object stored on the template. A sibling of `email_subject` and `email_body` on the create-template API. Do not wrap it in `extra`.
extraobjectrequired- Additional notification fields. Common keys: `big_picture`, `chrome_web_image`, `ios_sound`, `android_sound`, `ios_badge_type`, `ios_badge_count`, `data` (custom key-value payload), `url`, `web_url`, `app_url`, `buttons`, `web_buttons`, `ios_category`, `android_channel_id`, `isSMS` (`true` saves an SMS template; without it the template is push).
namestringrequired- Template name.
contentsobject- Notification content map (language code → message). E.g. `{"en": "Hello!"}`.
email_bodystring- HTML body for email templates. When provided, the template is automatically marked as an email template (`isEmail: true`).
email_subjectstring- Subject line for email templates. When provided, the template is automatically marked as an email template (`isEmail: true`).
headingsobject- Notification heading map (language code → heading).
onesignalmcp_create_userCreate a new user in a OneSignal app.WriteCreate User
Create a new user in a OneSignal app. Provide an `identity` (e.g. {"external_id": "user-123"}) so the user can be referenced later by alias. Optionally attach `properties` (tags, language, country) and `subscriptions` (email, SMS, or push channels). The `identity` field is required to prevent orphaned users.
Inputs
app_idstringrequired- OneSignal app ID.
identityobjectrequired- User identity aliases (e.g. `{"external_id": "user-123"}`). Required — without an identity the user cannot be referenced later by alias, resulting in orphaned records.
propertiesobjectrequired- User profile properties (tags, language, country, location, etc.).
subscriptionsarray- Subscriptions to attach to this user (push, email, or SMS channels).
onesignalmcp_duplicate_journeyCreates a draft copy of a Journey.WriteDuplicate Journey
Creates a draft copy of a Journey. Goals and A/B tests are not copied. Tell the user about this limitation before calling this tool. Optional overrides use the public writable create fields; use client_node_id for local node references, not sending_node_id or server-assigned IDs. Before calling, even without overrides, fetch get_journey_schema with operation=duplicate, or reuse the relevant schema already in context. The draft copy has fresh Journey, node, and branch IDs. The source schedule is not copied. A schedule override does not activate the draft. Without a name override, the source name gets a " (Copy)" suffix, with the source portion truncated to fit. Overrides use JSON Merge Patch: objects merge, arrays replace in full, and null removes a field. A nodes override replaces the entire graph. Within overrides.nodes, on_notification_action conditions must use the same client_node_id as their sending nodes.
Inputs
app_idstringrequired- OneSignal App ID.
source_journey_idstringrequired- Journey to copy within the app.
overridesobject- Overrides
onesignalmcp_export_audience_activity_csvExport audience activity for a notification to CSV.WriteExport Audience Activity CSV
Export audience activity for a notification to CSV. WARNING: Only 1 concurrent export is allowed per account — if a 409 or 429 is returned, a previous export is still running.
Inputs
app_idstringrequired- OneSignal app ID.
eventsstringrequired- Type of events to retrieve. `"sent"` — users the notification was sent to; `"clicked"` — users who clicked the notification.
notification_idstringrequired- Notification ID to export audience activity for.
emailstring- Email address to deliver the report to. Optional.
onesignalmcp_export_subscriptions_csvExport all subscriptions for a OneSignal app to CSV.WriteExport Subscriptions CSV
Export all subscriptions for a OneSignal app to CSV. WARNING: Only 1 concurrent export is allowed per account — if a 409 or 429 is returned, a previous export is still running.
Inputs
app_idstringrequired- OneSignal app ID.
extra_fieldsarray- Optional list of extra fields to include in the export.
last_active_sincestring- Unix timestamp (seconds). Only include subscriptions active since this time.
segment_namestring- Optional segment name to filter subscriptions by.
onesignalmcp_provision_app_credentialsTurn on push delivery for a platform during OneSignal SDK setup by uploading its credentials — an APNs `.p8` auth key, a Firebase FCM v1 service-account JSON, or a web push site origin.WriteProvision App Credentials
Turn on push delivery for a platform during OneSignal SDK setup by uploading its credentials — an APNs `.p8` auth key, a Firebase FCM v1 service-account JSON, or a web push site origin. This is a first-time onboarding step aimed at getting a developer's app sending: credentials write once per platform, and a platform that already has them returns 409 (replacing existing credentials stays in the dashboard). For APNs and FCM, read the credential file locally and pass its base64-encoded contents — this server is remote and cannot read local paths. Provide the complete field set for exactly one platform per call: APNs requires `apns_p8` (base64 of the `.p8`) plus `apns_key_id`, `apns_team_id`, and `apns_bundle_id`; FCM requires `fcm_v1_service_account_json` (base64 of the JSON); web push requires `chrome_web_origin` (the site's `https://` origin) with `chrome_web_default_notification_icon` (an icon URL) optional. Only `.p8` is accepted for APNs (not `.p12`). The raw API response is passed through unchanged so its status and body can be acted on.
Inputs
app_idstringrequired- The OneSignal app to provision credentials for (UUID).
apns_bundle_idstring- iOS app bundle identifier (e.g. `com.example.app`).
apns_key_idstring- APNs Key ID for the `.p8` auth key.
apns_p8string- APNs auth key (`.p8`) contents, base64-encoded. Requires `apns_key_id`, `apns_team_id`, and `apns_bundle_id`.
apns_team_idstring- Apple Developer Team ID.
chrome_web_default_notification_iconstring- URL of the default web push notification icon. Optional; valid only together with `chrome_web_origin`.
chrome_web_originstring- Web push site origin: an `https://` URL that exactly matches the site's origin (e.g. `https://example.com`).
fcm_v1_service_account_jsonstring- Firebase FCM v1 service-account JSON, base64-encoded.
onesignalmcp_create_alias_by_subscriptionCreate or update identity aliases for the user who owns a given subscription.DestructiveCreate Alias by Subscription
Create or update identity aliases for the user who owns a given subscription. The `onesignal_id` alias is read-only and must not be included.
Inputs
aliasesobjectrequired- New aliases to set on the user. Do not include `onesignal_id` (read-only).
app_idstringrequired- OneSignal app ID.
subscription_idstringrequired- Subscription ID to look up the user by.
onesignalmcp_create_or_update_aliasCreate or update identity aliases for a user identified by alias.DestructiveCreate or Update Alias
Create or update identity aliases for a user identified by alias. The `onesignal_id` alias is read-only and must not be included.
Inputs
alias_idstringrequired- Alias ID value.
alias_labelstringrequired- Alias label used to identify the user (e.g. `"external_id"`).
aliasesobjectrequired- New aliases to set on the user. Do not include `onesignal_id` (read-only).
app_idstringrequired- OneSignal app ID.
onesignalmcp_delete_journeyPermanently delete a Journey.DestructiveDelete Journey
Permanently delete a Journey. This action is destructive and does not require archival first.
Inputs
app_idstringrequired- OneSignal app ID (UUID).
journey_idstringrequired- Journey ID (UUID).
onesignalmcp_send_messageSend a push notification, email, or SMS via the OneSignal API.DestructiveSend Message
Send a push notification, email, or SMS via the OneSignal API. TIER 3 — HIGH IMPACT: confirmation is required before sending. Rate limited to 10 requests per minute. The `filters` array is limited to 200 entries; max 20,000 users per call. For push: set `contents`. For email: set `email_subject` + `email_body` (or use `template_id`). For SMS: set `contents` + `target_channel = "sms"`.
Inputs
app_idstringrequired- OneSignal app ID.
custom_dataobjectrequired- Custom data payload for push notifications, or personalization data for templates. Max size: 2KB (push/SMS), 10KB (email).
dataobjectrequired- Custom data payload passed through to the app (key-value map). Push only.
extraobjectrequired- Additional less-common notification fields (e.g. `big_picture`, `ios_sound`, `buttons`, `web_buttons`, `android_channel_id`, `ios_category`, `collapse_id`).
contentsobject- Notification content map (language code → message). E.g. `{"en": "Hello!"}`. Required for push and SMS. Not required for email (use `email_body` instead).
delayed_optionstring- Controls per-user delivery timing. Options: `"timezone"`, `"last-active"`.
delivery_time_of_daystring- Use with `delayed_option: "timezone"` to set local delivery time. Formats: `"9:00AM"`, `"21:45"`, `"09:45:30"`.
disable_email_click_trackingboolean- If `true`, disables click tracking on URLs in the email body.
email_bccarray- BCC recipients to copy on the email. Supplemental to the primary recipients (`email_to`, segments, aliases) — does not target on its own.
email_bodystring- HTML body for email messages. Required for email unless using `template_id`.
email_from_addressstring- The "From" email address (e.g. `"news@example.com"`). Defaults to your Dashboard setting.
email_from_namestring- The sender display name for the email. Defaults to your Dashboard "Sender Name".
email_preheaderstring- Preview text displayed after the email subject line in the inbox.
email_reply_to_addressstring- The "Reply-To" email address. Defaults to your Dashboard setting.
email_sender_domainstring- The authenticated sending domain for email delivery. Must be verified in DNS.
email_subjectstring- Subject line for email messages. Required for email unless using `template_id`.
email_toarray- Send email to specific addresses (up to 20,000). Creates new subscriptions if needed. Mutually exclusive with `filters`, `included_segments`, `include_aliases`.
excluded_segmentsarray- Exclude segments by name. Use with `included_segments`.
filtersarray- Audience filters. Maximum 200 entries. Mutually exclusive with `included_segments`.
headingsobject- Notification heading map (language code → heading). Push only.
idempotency_keystring- Idempotency key (UUID) to prevent duplicate messages. Valid for 30 days.
include_aliasesobject- Target users by alias (e.g. `{"external_id": ["user_1"]}`). Up to 20,000 aliases. Requires `target_channel` to be set. Mutually exclusive with `filters`, `included_segments`.
include_phone_numbersarray- Send SMS to specific phone numbers in E.164 format (up to 20,000). Creates new subscriptions if needed. Mutually exclusive with other targeting.
include_subscription_idsarray- Specific subscription IDs to target (up to 20,000). IMPORTANT: You must also set `target_channel` to `"email"` or `"sms"` when targeting email or SMS subscriptions, otherwise the API will reject them as invalid push IDs.
include_unsubscribedboolean- If `true`, sends email to unsubscribed addresses. Use for transactional/account emails only.
included_segmentsarray- Target segments by name. Mutually exclusive with `filters` and `include_aliases`.
namestring- An internal name to help organize messages. Not shown to recipients. Max 128 chars.
send_afterstring- Schedule delivery for a future UTC date/time in ISO 8601 format. Example: `"2025-09-24T14:00:00-07:00"`.
sms_fromstring- The phone number or messaging service used to send SMS/MMS. Defaults to your SMS Setup.
sms_media_urlsarray- URLs of media files to send as MMS. Requires MMS-capable `sms_from` number.
target_channelstring- The delivery channel when using `include_aliases` or segments for SMS. Accepts `"push"`, `"email"`, or `"sms"`.
template_idstring- Template ID (UUID v4) to use for message content.
ttlinteger- Time-to-live in seconds. Notification expires if not delivered within this window. Push only.
urlstring- URL to open when the push notification is clicked.
onesignalmcp_start_live_activityStart an iOS Live Activity and deliver it to a specific device subscription.DestructiveStart Live Activity
Start an iOS Live Activity and deliver it to a specific device subscription.
Inputs
activity_idstringrequired- An identifier you set when starting the Live Activity to uniquely identify it on the device.
activity_typestringrequired- Activity type identifier used in the URL path (e.g. `"sports-score"`).
app_idstringrequired- OneSignal app ID.
contentsobjectrequired- Push message body with language-specific values. E.g. `{"en": "Game started!"}`.
eventstringrequired- The action to perform. Must be `"start"` for this endpoint.
event_attributesobjectrequired- Static data to initialize the Live Activity (matches your ActivityAttributes struct).
event_updatesobjectrequired- Initial dynamic content state for the Live Activity.
headingsobjectrequired- Push title with language-specific values. E.g. `{"en": "Live Score"}`.
include_aliasesobjectrequired- Target users by alias map (e.g. `{"external_id": ["user1", "user2"]}`). Max 20,000.
namestringrequired- An internal name to help organize and track messages.
excluded_segmentsarray- Exclude users in these segments.
filtersarray- Dynamic audience filters.
idempotency_keystring- Idempotency key to prevent duplicate messages.
include_subscription_idsarray- Target specific subscription IDs.
included_segmentsarray- Target predefined segments by name.
ios_relevance_scorenumber- Relevance score between `0` and `1` for sorting Live Activities (iOS).
priorityinteger- Notification priority. `10` = high, `5` = normal.
stale_dateinteger- Unix timestamp (seconds) after which the Live Activity is considered stale.
onesignalmcp_transfer_subscriptionTransfer a subscription to a different user within the same app.DestructiveTransfer Subscription
Transfer a subscription to a different user within the same app. Cross-app transfers are not supported. Rate limited to 1 request per second per subscription.
Inputs
app_idstringrequired- OneSignal app ID.
identityobjectrequired- Identity of the user to transfer the subscription to.
subscription_idstringrequired- Subscription ID to transfer.
onesignalmcp_unsubscribe_emailUnsubscribe an email address using the token from an email unsubscribe link.DestructiveUnsubscribe Email
Unsubscribe an email address using the token from an email unsubscribe link. This endpoint uses token-based auth (no REST API key required).
Inputs
app_idstringrequired- OneSignal app ID.
notification_idstringrequired- Notification ID from the unsubscribe link.
tokenstringrequired- Unsubscribe token from the email link.
onesignalmcp_update_journeyUpdate fields on an existing Journey.DestructiveUpdate Journey
Update fields on an existing Journey. Send only the fields you want to change in `patch`. Arrays replace the entire existing array. For state changes, set `patch.state` to `draft`, `scheduled`, `active`, or `archived`. Send state changes in a separate patch without other fields. Every state change requires high-impact access. Activation can begin customer messaging. OneSignal decides whether the transition is permitted. Other field edits support draft and scheduled Journeys, plus active Journeys when high-impact changes are enabled. Archived and processing Journeys cannot receive other field edits. Changes to an active Journey can affect customers currently in the flow. Returns a compact receipt with the new concurrency key, without the full Journey graph. If the key is stale, read the Journey again and reassess your changes before another update. If the write outcome is unknown, read the Journey to check whether the change took effect before submitting another update. Before authoring, fetch get_journey_schema with operation=update, or reuse the relevant schema already in context. Objects merge and null removes a field. Existing node kinds cannot change. Top-level Journey IDs, timestamps, and created_source are ignored. To preserve existing node and branch identities, resend their id values in replacement arrays. A node without id is new. Omitting the original node removes it. Unknown node or branch IDs are rejected. A branch ID cannot move to another node. Active Journeys cannot add or remove branches. Removed steps retain routing for users already on them in active Journeys. For on_notification_action references to existing sending nodes, use sending_node_id. Set it to the sending node's id from get_journey. For references from on_notification_action to new sending nodes, set the same client_node_id on the node and condition. MCP does not retry writes.
Inputs
app_idstringrequired- OneSignal app ID (UUID).
concurrency_keystringrequired- Caller-supplied Journey concurrency key.
journey_idstringrequired- Journey ID (UUID).
patchobjectrequired- Fields to update on the Journey. To change state, send only `state` with `draft`, `scheduled`, `active`, or `archived`.
onesignalmcp_update_journey_nodeUpdate fields on one node in an existing Journey.DestructiveUpdate Journey Node
Update fields on one node in an existing Journey. Pass the node’s ID in `node_id` and only the fields you want to change in `patch`. Arrays, including branch arrays, replace the entire existing array. Supports draft and scheduled Journeys, plus active Journeys when high-impact changes are enabled. Archived and processing Journeys cannot be updated. Changes to a node in an active Journey can affect customers currently in the flow. Returns a compact receipt with the new Journey concurrency key, without the full Journey graph. If the key is stale, read the Journey again and reassess your changes before another update. If the write outcome is unknown, read the Journey to check whether the change took effect before submitting another update. Before authoring, fetch get_journey_schema with operation=update_node, or reuse the relevant schema already in context. The document=merged_node schema describes the node after applying the patch, so omit unchanged fields from patch. Objects merge and null removes a field. Existing node kinds cannot change. The route selects the node, and a supplied patch id is ignored. Within replacement arrays, preserve existing child-node and branch id values. A child node without id is new. Omitting the original child node removes it. Unknown child-node or branch IDs are rejected. A branch ID cannot move to another node. Active Journeys cannot add or remove branches. Removed steps retain routing for users already on them in active Journeys. For on_notification_action references to existing sending nodes, use sending_node_id. Set it to the sending node's id from get_journey. For references from on_notification_action to new sending nodes, set the same client_node_id on the node and condition. MCP does not retry writes.
Inputs
app_idstringrequired- OneSignal app ID (UUID).
concurrency_keystringrequired- Caller-supplied Journey concurrency key.
journey_idstringrequired- Journey ID (UUID).
node_idstringrequired- Opaque node ID from the Journey graph.
patchobjectrequired- Fields to update on the node.
onesignalmcp_update_live_activityUpdate or end an active iOS Live Activity.DestructiveUpdate Live Activity
Update or end an active iOS Live Activity.
Inputs
activity_idstringrequired- Live Activity ID to update.
app_idstringrequired- OneSignal app ID.
eventstringrequired- The action to perform on the Live Activity. `"update"` or `"end"`.
event_updatesobjectrequired- Updated dynamic content state for the Live Activity.
namestringrequired- An internal name to help organize and track messages.
contentsobject- Optional push message body shown alongside the Live Activity update.
dismissal_dateinteger- Unix timestamp (seconds) indicating when the Live Activity should be dismissed.
ios_relevance_scorenumber- Relevance score between `0` and `1` for sorting Live Activities (iOS).
priorityinteger- Notification priority. `10` = high, `5` = normal.
stale_dateinteger- Unix timestamp (seconds) after which the Live Activity is considered stale.
onesignalmcp_update_segmentUpdate an existing audience segment's name and/or filter conditions.DestructiveUpdate Segment
Update an existing audience segment's name and/or filter conditions. `name` is always required even if not changing it (max 128 characters). When `filters` is provided it replaces all existing filters; omit to keep existing filters intact. Maximum 200 filter entries.
Inputs
app_idstringrequired- OneSignal app ID.
namestringrequired- Segment name. Required — must be provided even if not changing it. Maximum 128 characters.
segment_idstringrequired- Segment ID to update.
filtersarray- Updated filter conditions. Maximum 200 entries. When provided, replaces all existing filters. Omit to keep existing filters intact.
onesignalmcp_update_subscriptionUpdate an existing subscription (token, enabled status, or test type).DestructiveUpdate Subscription
Update an existing subscription (token, enabled status, or test type).
Inputs
app_idstringrequired- OneSignal app ID.
subscriptionobjectrequired- Subscription fields to update.
subscription_idstringrequired- Subscription ID to update.
onesignalmcp_update_subscription_by_tokenUpdate a subscription identified by its channel type and token.DestructiveUpdate Subscription by Token
Update a subscription identified by its channel type and token. Provide `subscription_type` and `token` to identify the subscription, then pass the fields to update in `subscription`.
Inputs
app_idstringrequired- OneSignal app ID.
subscriptionobjectrequired- Subscription fields to update.
subscription_typestringrequired- Subscription type segment in the URL path. Must match the subscription channel type exactly (e.g. `"Email"`, `"SMS"`, `"AndroidPush"`, `"iOSPush"`).
tokenstringrequired- Push token identifying the subscription.
onesignalmcp_update_templateUpdate an existing notification template.DestructiveUpdate Template
Update an existing notification template. The `name` field is required even if you are not changing it. `contents` and `headings` replace the stored maps rather than merging into them, so a map that omits a language deletes that language. Send every language you want to keep. For multi-language work, read the `localize_messages` skill first.
Inputs
app_idstringrequired- OneSignal app ID.
dynamic_contentobjectrequired- Dynamic Content object stored on the template. A sibling of `email_subject` and `email_body` on the update-template API. Do not wrap it in `extra`.
extraobjectrequired- Additional notification fields to update. Common keys: `big_picture`, `chrome_web_image`, `ios_sound`, `android_sound`, `ios_badge_type`, `ios_badge_count`, `data` (custom key-value payload), `url`, `web_url`, `app_url`, `buttons`, `web_buttons`, `ios_category`, `android_channel_id`, `isSMS` (`true` marks the template as SMS).
namestringrequired- Template name. Required even if unchanged.
template_idstringrequired- Template ID to update.
contentsobject- Notification content map (language code → message).
email_bodystring- HTML body for email templates. When provided, the template is automatically marked as an email template (`isEmail: true`).
email_subjectstring- Subject line for email templates. When provided, the template is automatically marked as an email template (`isEmail: true`).
headingsobject- Notification heading map (language code → heading).
onesignalmcp_update_userUpdate an existing user identified by alias.DestructiveUpdate User
Update an existing user identified by alias. Use `properties` to set tags, language, or country. Use `deltas` to increment session counts or append purchase records (these add to existing values rather than overwriting). Returns 202 — the update is processed asynchronously.
Inputs
alias_idstringrequired- Alias ID value.
alias_labelstringrequired- Alias label used to identify the user (e.g. `"external_id"`).
app_idstringrequired- OneSignal app ID.
deltasobjectrequired- Incremental deltas to apply to session/purchase stats. Supported keys: `session_count` (integer), `session_time` (integer seconds), `purchases` (array of purchase objects with `sku`, `iso`, `amount`).
propertiesobjectrequired- User profile properties to update (tags, language, country, location, etc.).
refresh_device_metadataboolean- If `true`, refreshes device metadata (timezone, locale, etc.) from the subscription.
No tools match.