communication
OneSignal MCP Integration for Codex
Connect OneSignal to Codex through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.
Connect OneSignal to Codex
Use KosmoKrator as a local MCP proxy for Codex so coding sessions can reach selected integrations with explicit write policy.
Register kosmo mcp:serve as a local stdio server and choose the integration allowlist. The gateway is local, scoped to this integration, and starts with
--write=deny so Codex can inspect read-capable tools without receiving write access by default.
OneSignal MCP Config for Codex
Keep write access denied or ask-based unless the workspace is trusted.
{
"mcpServers": {
"kosmokrator-one-signal": {
"type": "stdio",
"command": "kosmo",
"args": [
"mcp:serve",
"--integration=one-signal",
"--write=deny"
]
}
}
} Run the Gateway Manually
kosmokrator mcp:serve --integration=one-signal --write=deny Why Use KosmoKrator Here
Expose only OneSignal instead of a broad multi-service tool list.
Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.
Start read-only, then opt into ask or allow for trusted workspaces.
OneSignal Tools Visible to Codex
Codex sees stable MCP tool names generated from the OneSignal integration catalog.
| MCP tool | Source function | Type | Description |
|---|---|---|---|
integration__one_signal__onesignal_list_notifications | one-signal.onesignal_list_notifications | Read | List push notifications sent through OneSignal. Returns notification details including delivery stats, click counts, and outcomes. Use limit and offset for pagination. |
integration__one_signal__onesignal_get_notification | one-signal.onesignal_get_notification | Read | Get details of a specific OneSignal push notification by its ID. Returns full notification data including content, delivery stats, and targeting. |
integration__one_signal__onesignal_create_notification | one-signal.onesignal_create_notification | Write | Send a new push notification via OneSignal. Specify message contents (per language), optional headings, target segments, a click URL, and a custom data payload. |
integration__one_signal__onesignal_list_devices | one-signal.onesignal_list_devices | Read | List devices (players) registered in a OneSignal app. Returns device identifiers, platform, session counts, and tags. Use limit and offset for pagination. |
integration__one_signal__onesignal_get_device | one-signal.onesignal_get_device | Read | Get details of a specific OneSignal device (player) by its ID. Returns push token, platform, session data, tags, and more. |
integration__one_signal__onesignal_list_apps | one-signal.onesignal_list_apps | Read | List all OneSignal apps accessible with the configured REST API key. Returns app names, IDs, player counts, and configuration. |
integration__one_signal__onesignal_get_current_app | one-signal.onesignal_get_current_app | Read | Get details of a specific OneSignal app by its ID. Returns app configuration, player counts, and platform settings. |