# OneSignal Cursor Plugin

OneSignal workflows for Cursor. This plugin packages:

- The hosted OneSignal MCP server.
- A setup skill for Cursor/MCP authentication.
- Safety rules for sends, writes, production apps, and secrets.
- Commands for setup, test notification planning, and delivery debugging.

## Requirements

- Cursor with plugin support.
- A OneSignal account.

This plugin uses OAuth through the hosted OneSignal MCP server.

## Configure Authentication

The plugin MCP config points Cursor at the OneSignal OAuth MCP endpoint:

```text
https://api.onesignal.com/mcp/oauth
```

When Cursor starts the MCP connection, follow the OAuth prompt to connect your OneSignal account. Do not paste OAuth tokens, API keys, or other secrets into chat or source files.

## Local Install for Testing

Symlink this repo into Cursor's local plugin folder:

```bash
mkdir -p ~/.cursor/plugins/local
ln -s /path/to/onesignal-cursor-plugin ~/.cursor/plugins/local/onesignal
```

Then restart Cursor or run `Developer: Reload Window`.

Verify:

1. Cursor sees the OneSignal plugin.
2. Cursor lists the OneSignal MCP server under MCP settings.
3. Read-only tools such as `onesignal_health`, `onesignal_config`, or `onesignal_reference_overview` work.
4. The OneSignal setup skill appears and triggers for plugin setup and MCP authentication questions.

## Included Skills

- `onesignal-setup`

## Included Commands

- `setup-onesignal`
- `send-onesignal-test-notification`
- `debug-onesignal-delivery`

## Safety Model

The plugin includes an always-on OneSignal safety rule:

- Prefer read-only checks before writes.
- Require explicit approval before sends, mutations, deletes, exports, transfers, or production actions.
- Ask for extra confirmation before large-audience or production blasts.
- Show channel, audience, content, schedule, and expected effect before any send.

Cursor may also show MCP tool approval prompts. Do not bypass them.