OneSignal User Auth
OneSignal is a customer engagement platform offering push notifications, email, SMS, and in-app messaging services.
Verdict
Common use cases
- Triage device opt-out issues from support chat
- Update user tags after account upgrades
- Audit segment definitions before campaign launch
- Pull device details during onboarding calls
- Verify tag accuracy after bulk imports
Integration
- Vendor
- OneSignal User Auth
- Category
- other
- Auth
- API_KEY
- Tools
- 7
- Composio slug
onesignal_user_auth
Tools
- Add or Update Device Tags
Tool to assign or update tags on a onesignal device. use when you need to apply or change custom tags for a player for segmentation.
- Edit OneSignal Device
Tool to update an existing onesignal device (player) record. use when you have the player id and need to modify device attributes.
- View App
Tool to retrieve details for a specific onesignal app. use after authenticating to inspect app settings.
- View OneSignal Device
Tool to retrieve details for a specific device/player. use when you have a player id and optional app id.
- View OneSignal Device Tags
Tool to get tags assigned to a device. use when you need to fetch key/value tags for a specific onesignal player.
- View OneSignal Segment
Tool to retrieve details for a specific onesignal segment. use when you need to inspect segment definition.
- View Segments
Tool to list all segments for an app. use after obtaining the app id to retrieve a paginated list of segments.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to Integrations. 2. Find OneSignal User Auth in the list and click Connect. 3. You'll be prompted to paste a OneSignal REST API key—generate one in your OneSignal dashboard under Settings > Keys & IDs. 4. Grant the key read and write permissions for devices, tags, and segments (the integration won't request notification send permissions). 5. Paste the key into Switchy and click Authorize. 6. Open any Space and type '@OneSignal view app' followed by your app ID to confirm the connection works. 7. If the app details appear, you're ready—@mention OneSignal in any message to invoke device lookups, tag updates, or segment queries.
What teammates see: by default, memories from OneSignal User Auth are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Inspect Device Record
@OneSignal view the device with player ID abc123-def456 and show me all attributes including tags and subscription status.Open in a Space →
Tag Premium Users
@OneSignal add the tag 'plan:premium' to device xyz789 so we can target them in the next campaign.Open in a Space →
List Active Segments
@OneSignal show me all segments for app ID app_12345 and include the filter definitions for each.Open in a Space →
Audit Device Tags
@OneSignal get all tags for player ID player_67890 and tell me if any look outdated or incorrect.Open in a Space →
Check Segment Details
@OneSignal view segment seg_abc123 and explain the filter criteria in plain language.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@OneSignal User Auth show me all segments for app ID abc123 and explain which ones target active users
Retrieved 5 segments from your OneSignal app. Three segments target active users: 'Engaged Last 7 Days' (12,400 devices, filters for session_count >= 3 in past week), 'Daily Active Users' (8,200 devices, last_session < 24h), and 'Power Users' (1,850 devices, session_count >= 20 all-time). The other two segments ('Churned Users' and 'New Installs') focus on re-engagement and onboarding. The 'Engaged Last 7 Days' segment is your largest active cohort and would be a strong candidate for feature announcements.
This example demonstrates segment inspection and AI synthesis. Requires valid app_id from your OneSignal dashboard. The MCP returns raw segment definitions; the AI interprets filters and device counts to answer your strategic question. Useful for campaign planning before sending notifications.
@OneSignal User Auth add tags 'premium_tier: gold' and 'renewal_date: 2025-06-15' to player xyz789
Successfully updated tags for player xyz789. Applied 'premium_tier' with value 'gold' and 'renewal_date' with value '2025-06-15'. These tags are now available for segmentation rules in your OneSignal dashboard. You can target this user in campaigns filtered by premium_tier=gold or send renewal reminders based on the renewal_date tag. Changes take effect immediately for future notification sends.
This example shows device tagging for user segmentation. Requires a valid player_id (OneSignal's device identifier). Tags are key-value pairs you define; OneSignal imposes no schema. Be cautious: typos in tag keys create duplicate segments. This is a write operation—verify the player_id before running to avoid tagging the wrong device.
@OneSignal User Auth fetch device details for player xyz789 and check if push notifications are enabled
Retrieved device record for player xyz789. This is an iOS device (iPhone 14, iOS 17.2) with push notifications currently enabled. Last active session was 3 hours ago. The device has 4 tags assigned: 'premium_tier: gold', 'renewal_date: 2025-06-15', 'language: en', 'timezone: America/New_York'. Notification permission status is 'authorized', meaning this user will receive push notifications you send to segments including this player.
This example demonstrates device inspection and permission checking. Requires a valid player_id; optionally accepts app_id if you manage multiple apps. The MCP returns device metadata (OS, model, session history, tags, notification state). Useful for debugging why a user isn't receiving notifications or verifying tag application after updates.
Use-case deep-dives
When OneSignal MCP beats the dashboard for ticket resolution
A 6-person support team fields 40-60 tickets daily about push notification delivery. The OneSignal MCP wins here because agents can pull device tags, check segment membership, and update player attributes without leaving their AI workspace. The View OneSignal Device and View OneSignal Device Tags tools surface the exact state that caused a delivery failure—timezone mismatch, opt-out tag, wrong segment—in one query instead of three dashboard clicks. The trade-off: if your team already has a custom support panel that embeds OneSignal data, the MCP adds little. But if agents toggle between Zendesk and the OneSignal dashboard today, this MCP cuts resolution time by 30-40% on notification-related tickets. Worth the API key setup for any team handling more than 20 push issues per week.
Segment inspection at planning scale, not ops scale
A solo PM or 2-person growth team planning a feature launch needs to audit which user cohorts will see the announcement push. The OneSignal MCP's View Segments and View OneSignal Segment tools let you list all segments and inspect definitions in conversational queries—no SQL, no dashboard export. This works when you have 10-50 segments and you're spot-checking logic before a campaign. It breaks down past 100 segments or if you need bulk edits; the MCP has no batch-update tool, so you're back in the dashboard for anything beyond read-only inspection. The buying call: if your planning ritual is 'check segment definitions before launch,' and you do it 2-4 times per sprint, the MCP saves 15 minutes each time. Below that frequency, bookmark the dashboard.
When device tagging belongs in your AI workflow
A 3-person eng team building a mobile onboarding flow needs to tag users as they complete steps—'completed_tutorial', 'selected_plan', 'invited_teammate'. The Add or Update Device Tags tool wins if your team already uses an AI workspace to prototype backend logic or script user-state transitions. You can test tag assignment in the same context where you're drafting the onboarding sequence, without switching to Postman or the OneSignal dashboard. The threshold: this only makes sense if tagging is part of a larger workflow you're already prototyping in Switchy. If you're just implementing a one-off tag update in production code, write it directly in your app's push client. The MCP shines when tagging is a planning artifact, not a deployment task.
Frequently asked
What does the OneSignal MCP do in Switchy?
It lets your team read and update OneSignal device records, tags, and segments without leaving the chat. You can inspect player attributes, assign segmentation tags, fetch app settings, and list audience segments. It's useful for support teams checking device state or marketers auditing segment definitions during campaign planning.
Do I need admin access to connect OneSignal?
You need a OneSignal API key with read and write permissions for devices, tags, and segments. OneSignal uses API key auth, not OAuth, so whoever connects it must have access to generate or retrieve a key from the OneSignal dashboard. Standard user keys work; you don't need owner-level access.
Can the OneSignal MCP send push notifications?
No. This MCP reads device data and updates tags or attributes, but it doesn't create or send notifications. If you need to trigger pushes from Switchy, you'll need to use OneSignal's REST API directly or wait for a separate notification-focused MCP.
How is this different from using OneSignal's dashboard?
The dashboard is faster for bulk operations and visual segment builders. The MCP is better when you're already in a Switchy thread debugging a user issue and need to check their device tags or update a single player record without context-switching. It's about convenience, not replacement.
Who on the team should connect this MCP?
Whoever handles customer support escalations or manages audience segmentation. They'll need the API key and enough OneSignal knowledge to interpret player IDs and tag schemas. The MCP doesn't count against Switchy seat limits, but the API key grants write access, so treat it like a credential.