X (Twitter)LinkedInGitHubDiscordYouTube

How to connect Onesignal rest api to Claude

Connect Claude Web, Desktop and Cowork to Onesignal rest api MCP. Send push notification to all active users, list all devices registered for your app, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Onesignal rest api logoOnesignal rest api
Api Key

OneSignal is a cross-channel messaging platform offering REST APIs for notifications, user management, and app settings. It lets you reach users via push, email, and SMS from a single, unified interface.

15 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Onesignal rest api account to Claude via Composio Connect, enabling it to send push notification to all active users, list all devices registered for your app, view details of last 10 notifications, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Onesignal rest api with

Claude CodeOpenAI Agents SDKClaude Agent SDKCodexOpenClawHermesAtomic AgentGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

Connecting Onesignal rest api to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Onesignal rest api account

Back in Claude, ask it to connect to Onesignal rest api or give it any Onesignal rest api-related task.

For example, ask Claude to:

  • "Send push notification to all active users"
  • "List all devices registered for your app"
  • "View details of last 10 notifications"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Onesignal rest api account is ready to use.

What is the Onesignal rest api Claude Connector, and what's possible with it?

The Onesignal rest api MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your OneSignal account. It provides structured and secure access to your messaging platform, so your agent can perform actions like sending push notifications, managing devices, viewing app details, and segmenting audiences automatically on your behalf.

  • Automated push notifications and messaging: Instantly have your agent create and send targeted push notifications to your users, keeping them engaged and informed.
  • Device management and updates: Let your agent add, update, or remove registered devices (players) to keep your audience data fresh and accurate.
  • App insights and metadata retrieval: Effortlessly fetch and review detailed app information, notification history, and device lists for better operational visibility.
  • Audience segmentation and targeting: Enable your agent to view and utilize user segments, making it easy to target the right audience for every message.
  • Notification analytics and history: Have your agent retrieve past notifications, track delivery, and analyze engagement trends for continuous improvement.

Troubleshooting

1. Why does Claude not use the Composio connector for Onesignal rest api?

The connector can show as connected, but Claude must use it in each Onesignal rest api conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Onesignal rest api again.

2. Why does Claude show an MCP server error before Onesignal rest api connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Onesignal rest api.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Onesignal rest api.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Onesignal rest api authorization link not work?

The Composio connector is one server. Your Onesignal rest api account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Onesignal rest api connection.
  • Composio creates a fresh Onesignal rest api authorization link.
  • Open that link in your browser and finish the Onesignal rest api sign-in.

4. Why do Onesignal rest api actions fail after they worked before?

The Onesignal rest api connection can expire or lose permission.

  • Ask Claude to inspect the Onesignal rest api connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Onesignal rest api account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Onesignal rest api.
  • If the action still fails with a permission error, check that the connected account has that permission in Onesignal rest api itself.

5. How do I switch to a different Onesignal rest api account?

Claude can manage the Onesignal rest api connection for you.

  • Ask Claude to disconnect or delete the current Onesignal rest api account.
  • Ask Claude to connect Onesignal rest api again.
  • Open the new Composio authorization link for Onesignal rest api.
  • Sign in with the other Onesignal rest api account in the browser.
  • After the account connects, ask Claude to retry the Onesignal rest api task.

6. Why is my Onesignal rest api connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Onesignal rest api connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If Onesignal rest api tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Onesignal rest api.
TOOLS

Supported Tools

Every Onesignal rest api action and event your agent gets out of the box.

Begin Live Activity

Tool to start a Live Activity on OneSignal.

Create Notification

Tool to create and send a OneSignal push notification.

Create Template

Tool to create reusable message templates for push, email, and SMS channels.

Create User

Tool to create a OneSignal user with optional subscriptions and aliases.

Delete Alias

Tool to delete an alias by alias label from a OneSignal user.

Delete Device

Tool to delete a device (player) from a OneSignal app.

Fetch User Identity

Tool to retrieve all aliases for a user identified by a specific alias.

Get Eligible In-App Messages

Tool to retrieve the manifest of In-App Messages that a subscription is eligible to display.

Update Device

Tool to update properties of an existing device.

Update Subscription

Tool to update an existing subscription's properties.

View OneSignal App

Tool to retrieve metadata for a single OneSignal app.

View Device

Tool to retrieve details of a specific device (player).

View Devices

Tool to retrieve a paginated list of devices (players) for a OneSignal app.

View Notifications

Tool to retrieve details of multiple notifications.

View Segments

Tool to view segments for a OneSignal app.

FRAMEWORKS

How to build Onesignal rest api MCP Agent with another framework

Claude Code logo

Claude Code

Use Onesignal rest api MCP with Claude Code

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Onesignal rest api MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Onesignal rest api MCP with Claude Agent SDK

Codex logo

Codex

Use Onesignal rest api MCP with Codex

OpenClaw logo

OpenClaw

Use Onesignal rest api MCP with OpenClaw

Hermes logo

Hermes

Use Onesignal rest api MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Onesignal rest api MCP with Atomic Agent

Google ADK logo

Google ADK

Use Onesignal rest api MCP with Google ADK

LangChain logo

LangChain

Use Onesignal rest api MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Onesignal rest api MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Onesignal rest api MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Onesignal rest api MCP with LlamaIndex

CrewAI logo

CrewAI

Use Onesignal rest api MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Onesignal rest api MCP with Pydantic AI

AutoGen logo

AutoGen

Use Onesignal rest api MCP with AutoGen

FAQ

Frequently asked questions

With a standalone Onesignal rest api MCP server, the agents and LLMs can only access a fixed set of Onesignal rest api tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Onesignal rest api and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Onesignal rest api tools.

Yes, absolutely. You can configure which Onesignal rest api scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Onesignal rest api data and credentials are handled as safely as possible.

Start with Onesignal rest api.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Onesignal rest api tool your agent needs.Free to start.

Start building