Bring Onesignal
to Cursor
Learn how to connect OneSignal to Cursor 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 Cursor?
Cursor's Agent mode turns OneSignal into an in-editor superpower. Ask Cursor to generate code using live data from OneSignal and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
OneSignal in Cursor
OneSignal and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect OneSignal to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.