OneSignal MCP server

What the model can do

OneSignal messaging for one app: sent push, email and SMS messages with delivery, click and error counts, one message's figures by platform, segments and templates; can send a push, email or SMS to segments or named users, cancel a scheduled send, create and delete segments and templates, broadcast to the in-app inbox, record custom events, delete a user and copy a journey as a draft.

Reads

• onesignal_messagesMessages the OneSignal app has sent or scheduled, newest first: name, heading and text, when it was queued, started and finished…
• onesignal_messageOne OneSignal message by id with its full figures, including delivery, clicks and errors per platform.
• onesignal_segmentsAudience segments in the OneSignal app, oldest first: name, description, whether active or read-only, and dates.
• onesignal_templatesMessage templates in the OneSignal app: name and dates.

Acts, when you ask

These change something in OneSignal. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• onesignal_send_pushSends a push notification from the OneSignal app to every subscribed device in the chosen segments, or to the named users (external ids).
• onesignal_send_emailSends an email from the OneSignal app to the chosen segments, named users (external ids) or email addresses.
• onesignal_send_smsSends an SMS from the OneSignal app to the chosen segments, named users (external ids) or phone numbers.
• onesignal_cancel_messageStops a OneSignal message that is scheduled or still sending; recipients not yet reached do not get it.
• onesignal_create_segmentCreates a segment in the OneSignal app from filters (tags, sessions, language, app version, country and the like…
• onesignal_delete_segmentDeletes a segment from the OneSignal app.
• onesignal_create_templateCreates a reusable push, email or SMS template in the OneSignal app.
• onesignal_update_templateEdits a OneSignal template's name and content.
• onesignal_delete_templatePermanently deletes a OneSignal template.
• onesignal_create_inbox_broadcastBroadcasts a message to the in-app inbox of every user of the OneSignal app.
• onesignal_create_custom_eventRecords custom events against named users in the OneSignal app (for example "trial_started").
• onesignal_delete_userPermanently deletes one user from the OneSignal app with their properties, tags and every subscription (push, email, SMS)…
• onesignal_duplicate_journeyCopies a OneSignal journey as a new draft, optionally renamed.

Connect it

First connect OneSignal on Dashboard → Connections, then add Memtro to your client once. The OneSignal tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared OneSignal connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › How did last week's push do?
• › Which messages had the most errors this month?
• › Break down yesterday's sale push by platform
• › Which of our segments are read-only?
• › Schedule a push to the Lapsed users segment for 9am Saturday saying the sale ends Sunday

Questions

Is this an official OneSignal MCP server?

No. It is Memtro's MCP server with Memtro's OneSignal connector behind it: the connector reads OneSignal through its API with the credentials you connect on Dashboard → Connections, and OneSignal publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in OneSignal?

Only when you ask, and only what it has been granted: send a push notification to segments or named users (notifies them); send an email to segments, named users or addresses (notifies them); send an SMS to segments, named users or phone numbers (notifies them, spends SMS credits); cancel a scheduled or sending message; create a segment from filters; delete a segment; create a push, email or SMS template; edit a template (changes anything sending from it); delete a template (permanent); broadcast a message to every user's in-app inbox; record custom events against users (may trigger journeys); delete a user with their properties and subscriptions (permanent); copy a journey as a new draft. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Email, calendar and chat

• AgentMail MCP server
• Gmail MCP server
• Google Calendar MCP server
• Slack MCP server
• Outlook Mail MCP server
• Outlook Calendar MCP server