Setting up the OneSignal MCP Server

Step-by-step guide to connecting the official hosted OneSignal MCP server via OAuth as well as the alternative installation via Smithery.

Skill Road
Setting up the OneSignal MCP Server

Published on 18.09.2026

This guide walks you through setting up the official OneSignal MCP Server. You will learn how to connect the hosted server to your client via OAuth and how to perform the alternative local configuration using the Smithery CLI.

Step 1: Verify Prerequisites

Before starting, the provider states that you need:
An active OneSignal account (available on all plans, including the free tier).
At least one configured OneSignal App (e.g., for Web Push or mobile push notifications).
A compatible MCP client such as Claude Desktop, Cursor, ChatGPT, or Codex.

Step 2: Hosted Connection via OAuth (Recommended)

The easiest and most secure method is using the official OneSignal Cloud infrastructure. This removes the need to run or maintain a local background server process.
Open the MCP settings in your AI client (e.g., in Cursor under *Settings > Models > MCP*).
Add a new MCP server with the type set to SSE (Server-Sent Events).
Enter the official connection URL:
https://api.onesignal.com/mcp/oauth
Your client will prompt you to authorize the connection. A secure browser window will open, where you log into your OneSignal account and grant the client read and write permissions for your selected apps.

Step 3: Alternative Local Installation via Smithery CLI

If your client does not support hosted SSE endpoints or you prefer to run the server locally on your machine, you can deploy it using Smithery:
Open your terminal.
Run the following command to automatically install and configure the server for Claude Desktop:

npx -y @smithery/cli install onesignal-mcp --client claude

Follow the on-screen instructions. You will be prompted to enter your OneSignal API Key and App ID. These credentials will be stored locally in your client's configuration file.

Step 4: Test Your First Tools

Once the connection is active, you can give your AI assistant its first test tasks. Try prompts like these to verify functionality:
"Show me my active OneSignal applications."
"What was the click-through rate of our last push notification?"
"Create a new test segment called 'Beta Testers'."

Published on 18.09.2026

Frequently asked questions

Do I need a paid OneSignal plan?

No. According to the provider, the official MCP server is available on all tiers, including the Free plan. Costs only apply if you exceed the monthly free limits for push notifications, emails, SMS, or in-app messages.

Are my API keys secure?

Yes. With the recommended OAuth method, the client never needs to store your API keys in plain text. You authorize access once through the secure OneSignal platform. With the local CLI method, the API keys remain locally on your machine.

Are there safeguards against accidental mass messaging?

Yes. The official OneSignal MCP server includes Confirmation Guards. For actions that modify data or send messages to larger audiences, the server requires explicit manual user confirmation in the client before executing the action.