
Onesignal Mcp
io.github.mrfentmenv1.0.0Updated Oct 1, 2026
Query the OneSignal API (free tier; use a current v2 Organization API key for ONESIGNAL_USER_KEY.
Overview
AI-generated overview
Lets an assistant query the OneSignal API using an organization API key supplied through the ONESIGNAL_USER_KEY environment variable.
- What it does
- This MCP server exposes the OneSignal API to an assistant so it can run queries against a OneSignal account. It runs locally over stdio as the npm package onesignal-mcp. The registry description mentions using a current v2 Organization API key for ONESIGNAL_USER_KEY, and notes the free tier. No individual tools are listed in the manifest.
- When to use it
- Consider it when you want an assistant to read or query OneSignal data, such as messaging or notification information, from your own machine. It is a narrow, single-service integration, so it is only useful if you already use OneSignal.
- Requirements
- A local Node.js runtime to run the npm package onesignal-mcp over stdio. A OneSignal account and a current v2 Organization API key provided as the ONESIGNAL_USER_KEY environment variable. Network access to the OneSignal API. Desktop only; no web executable.
Before you install
The server needs a OneSignal Organization API key in ONESIGNAL_USER_KEY, which is a broad credential; treat it as a secret and avoid exposing it in logs or shared configuration. The description says the free tier is used, but it does not state whether any tool can send messages or change account data, so verify the actual tool set before relying on it.
Installation
In SourceWeft
- Open Onesignal Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.0.0LatestOct 1, 2026
