Bring Onesignal
to Claude Desktop
Learn how to connect OneSignal to Claude Desktop and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the OneSignal MCP Server?
Connect your OneSignal account to any AI agent and take full control of your customer engagement and notification orchestration through natural conversation. OneSignal is the market leader for omnichannel delivery, and this integration allows you to dispatch real-time push notifications, manage audience segments, and monitor delivery analytics directly from your chat interface.
What you can do
- Omnichannel Dispatch Orchestration — Send push notifications, emails, and SMS programmatically using advanced targeting and personalized content to ensure your message always lands.
- Audience & User Intelligence — Manage user profiles (players), update custom tags, and retrieve detailed device metadata directly from the AI interface to maintain a high-fidelity CRM.
- Segment & Targeting Control — Access and monitor your audience segments and apply dynamic targeting criteria via natural language to drive better engagement.
- Performance & Outcome Oversight — Retrieve granular delivery analytics, track successful/failed counts, and monitor custom outcomes using simple AI commands.
- Operational Monitoring — Track system responses and manage multiple applications to ensure your notification pipeline is always optimized.
How it works
1. Subscribe to this server
2. Enter your OneSignal App ID and REST API Key from your dashboard
3. Start managing your omnichannel delivery from Claude, Cursor, or any MCP-compatible client
No more manual logging to check open rates or send emergency alerts. Your AI acts as a dedicated engagement coordinator or growth operations manager.
Who is this for?
- Growth Marketers — quickly send promotional alerts and monitor campaign reach without switching apps.
- Product Managers — automate the delivery of transactional notifications and track user re-engagement via natural conversation.
- Operations Teams — streamline the retrieval of player metadata and monitor system alerts directly within the chat.
Built-in capabilities (12)
Stop notification
Check connection
Get application info
Check delivery metrics
Get user profile
Get campaign outcomes
List subscribed devices
List target groups
Requires User Auth Key. List your applications
List past alerts
Delete device record
Send proactive alert
Why Claude Desktop?
Claude Desktop is the definitive way to connect OneSignal to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
OneSignal in Claude Desktop
OneSignal and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect OneSignal to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for OneSignal in Claude Desktop
The OneSignal MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
OneSignal for Claude Desktop
Every tool call from Claude Desktop to the OneSignal MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my AI automatically find the Player ID for a specific user to send a test push?
Yes! Use the list_users tool. Your agent will respond with complete metadata for registered devices, including unique Player IDs and tags, allowing you to trigger targeted pushes instantly.
How do I find my OneSignal App ID and REST API Key?
Log in to OneSignal, select your app, navigate to Settings > Keys & IDs, and you will find your unique App ID and secret REST API key there.
Can I use the AI to cancel a scheduled notification?
Absolutely. Use the cancel_notification tool with the Notification ID. The agent will instruct OneSignal to stop the broadcast immediately, provided it hasn't been fully delivered yet.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.