An astronaut overseeing a futuristic data hub

Connect OneSignal to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Manage your entire engagement workflow through a single chat interface.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 10 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 10 available through OneSignal.

  1. 01

    Delete player

    This capability removes a registered device from your OneSignal records.

  2. 02

    Get app

    This capability retrieves specific configuration details for a OneSignal app using your User Auth Key.

  3. 03

    Get notification

    This capability pulls the current status and details for a specific notification.

  4. 04

    Get outcomes

    This capability fetches engagement outcome data for your application.

Capability set02 / 03

05-07

3 capabilities in this set.

Part of 10 available through OneSignal.

  1. 05

    Get player

    This capability retrieves detailed information about a specific registered player.

  2. 06

    Cancel notification

    This capability stops a notification that has been scheduled but not yet sent.

  3. 07

    List apps

    This capability returns a list of all your OneSignal applications using your User Auth Key.

Capability set03 / 03

08-10

3 capabilities in this set.

Part of 10 available through OneSignal.

  1. 08

    List players

    This capability generates a list of all registered devices within your application.

  2. 09

    Create notification

    This capability sends a new push notification to your target audience.

  3. 10

    List notifications

    This capability provides a list of all notifications sent through the app.

Real work

What teams actually run

01

Instant Campaign Execution

A marketer tells their agent to send a limited-time discount code to all active users.

02

Troubleshooting Delivery

A support agent asks the AI to check why a specific user didn't receive a critical update notification.

03

Automated Device Audits

A developer asks the agent to list the most recent device registrations to verify app integration.

04

Performance Monitoring

A growth lead asks for the outcome data of a recent push campaign to evaluate engagement.

Automate a task

Put OneSignal to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

OneSignal works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put OneSignal to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

987ms average. Fast in production.

OneSignal is checked daily against the live service.

Daily averagePeak 1179ms
Oct 3Today
Fastest day
821ms
Slowest day
1179ms
14-day trend
Slowing+11%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 10 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of OneSignal, so you can see the experience inside your AI.

It does not authenticate your account with OneSignal. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

OneSignal Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_BURKE5PMzSnmSC2KP6Ci4WVL1WqWtaYVOiP1cMAO/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — OneSignal capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "onesignal-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_BURKE5PMzSnmSC2KP6Ci4WVL1WqWtaYVOiP1cMAO/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up OneSignal in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work OneSignal owners hand off.

This MCP is built for teams that need to bridge the gap between customer engagement and their technical workflows.

  • 01

    Marketing Managers

    They use the agent to trigger campaign alerts or schedule announcements without logging into the OneSignal dashboard.

  • 02

    Support Teams

    They use the agent to verify if a specific user received a notification by checking player ID metadata.

  • 03

    Developers

    They use the agent to test notification payloads and check device registrations directly from their IDE.

FAQ

Questions OneSignal owners ask.

  • 01

    What do I need to connect this MCP?

    You will need your OneSignal REST API Key and your App ID. If you want to perform account-level tasks like listing all your apps, you will also need your User Auth Key.

  • 02

    Which AI clients can I use with this?

    You can use this MCP with any compatible client, including Claude, Cursor, and Windsurf.

  • 03

    Can I cancel a notification I already scheduled?

    Yes, you can use the cancel_notification capability to stop a scheduled notification before it is sent.

  • 04

    How do I see if my push notification was successful?

    You can ask your agent to get the notification status or get the outcomes for the app to see delivery metrics.

  • 05

    Is my OneSignal data secure?

    Vinkius hosts the MCP and manages your credentials securely, so you don't have to manage local environment variables for your API keys.

  • 06

    Can I target specific users instead of sending to everyone?

    Yes! Use the create_notification capability and provide a list of include_player_ids. This ensures the notification is only delivered to the specific devices you've identified.

  • 07

    How can I check if a scheduled notification was actually sent?

    You can use the get_notification capability with the Notification ID. It will return real-time delivery metrics, including the number of successful deliveries and current status.

  • 08

    Is it possible to manage multiple OneSignal apps?

    Yes. While the core operations use the primary App ID provided in credentials, you can use list_apps (requires User Auth Key) to see all your applications and their respective IDs.

Connect OneSignal to Claude, Cursor, ChatGPT & more