Onesignal rest api MCP server for AI agents and assistants

Securely connect your AI agents and chatbots (Claude, ChatGPT, Cursor, etc) with Onesignal rest api MCP or direct API to send push notifications, manage user segments, trigger emails, and automate subscription workflows through natural language.

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

Try Onesignal rest api now

Type what you want done — sign in and watch it run live in the Tool Router playground.

TOOL ROUTER PLAYGROUND
Onesignal rest api
Try asking
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.

SETUP GUIDE

Connect Onesignal rest api MCP Tool with your Agent

1

Install Composio

typescript
npm install @composio/core ai @ai-sdk/mcp @ai-sdk/openai
Install the Composio SDK and your agent framework
2

Create a session with MCP enabled

typescript
import { Composio } from "@composio/core";

const composio = new Composio();
const { mcp } = await composio.create("your-user-id", {
  toolkits: ["onesignal_rest_api"],
  mcp: true,
});
Create a session scoped to Onesignal rest api and read its MCP URL and headers
3

Connect your agent to the MCP server

typescript
import { createMCPClient } from "@ai-sdk/mcp";
import { openai } from "@ai-sdk/openai";
import { generateText, stepCountIs } from "ai";

const client = await createMCPClient({
  transport: { type: "http", url: mcp.url, headers: mcp.headers },
});

const { text } = await generateText({
  model: openai("gpt-5.6-sol"),
  tools: await client.tools(),
  prompt: "Send a push notification to all users announcing today's feature release.",
  stopWhen: stepCountIs(10),
});

console.log(text);
await client.close();
Pass the session's MCP URL and headers to your agent and run a Onesignal rest api request
SETUP GUIDE

Connect Onesignal rest api API Tool with your Agent

1

Install Composio

typescript
npm install @composio/core @composio/openai openai
Install the Composio SDK, the OpenAI provider, and the OpenAI SDK
2

Create a Composio session

typescript
import OpenAI from "openai";
import { Composio } from "@composio/core";
import { OpenAIResponsesProvider } from "@composio/openai";

const composio = new Composio({ provider: new OpenAIResponsesProvider() });
const client = new OpenAI();

const session = await composio.create("your-user-id", { toolkits: ["onesignal_rest_api"] });
const tools = await session.tools();
Initialize Composio with the OpenAI Responses provider and create a session scoped to Onesignal rest api
3

Run Onesignal rest api tools with your agent

typescript
let response = await client.responses.create({
  model: "gpt-5.6-sol",
  tools,
  input: [{ role: "user", content: "Send a push notification to all users announcing today's feature release." }],
});

while (response.output.some((o) => o.type === "function_call")) {
  const outputs = await composio.provider.handleToolCalls(session, response.output);
  response = await client.responses.create({
    model: "gpt-5.6-sol",
    tools,
    previous_response_id: response.id,
    input: outputs,
  });
}

console.log(response.output_text);
Send a request, execute the Onesignal rest api tool calls through the session, and print the final answer

Why Use Composio?

AI Native Onesignal rest api Integration

  • Supports both Onesignal rest api MCP and direct API based integrations
  • Structured, LLM-friendly schemas for reliable tool execution
  • Rich coverage for reading, writing, and querying your Onesignal rest api data

Managed Auth

  • Built-in OAuth handling with automatic token refresh and rotation
  • Central place to manage, scope, and revoke Onesignal rest api access
  • Per user and per environment credentials instead of hard-coded keys

Agent Optimized Design

  • Tools are tuned using real error and success rates to improve reliability over time
  • Comprehensive execution logs so you always know what ran, when, and on whose behalf

Enterprise Grade Security

  • Fine-grained RBAC so you control which agents and users can access Onesignal rest api
  • Scoped, least privilege access to Onesignal rest api resources
  • Full audit trail of agent actions to support review and compliance

Rolling this out across your team?

Give your team centralized access control across every framework with Composio’s MCP Gateway.

EXPLORE MCP GATEWAY
FAQ

Frequently asked questions

Yes, Onesignal rest api requires you to configure your own API key credentials. Once set up, Composio handles secure credential storage and API request handling for you.

Yes! Composio's Tool Router enables agents to use multiple toolkits. Learn more.

Yes. Composio is SOC 2 Type II compliant and is built to keep your Onesignal rest api connection and credentials secure. OAuth tokens and API keys are encrypted, and sensitive customer data is protected at rest and in transit.

Composio also undergoes independent security testing and continuously monitors its systems for security threats. You can review the latest reports and policies in the Composio Trust Center.

Composio maintains and updates all toolkit integrations automatically, so your agents always work with the latest API versions.

Create the key in your Onesignal rest api account settings, then paste it once on Composio's connection page. Composio stores it encrypted and uses it only for the Onesignal rest api actions your agent runs. Nobody else in your workspace can read it, and you can revoke it inside Onesignal rest api at any time.

When you connect a Onesignal rest api account through Composio, every action runs under that account, so anything the agent creates, sends, or changes shows up in Onesignal rest api as done by you. Keep an approval step in your prompt for actions with side effects, such as sending or deleting, and have the agent draft first.

Whatever the credentials you connect allow inside Onesignal rest api. If Onesignal rest api lets you scope a key to specific permissions, create a scoped one so the agent can only do what you intend. You can revoke the key inside Onesignal rest api at any time.

Yes. Composio supports multiple connected accounts for the same app, and that works in Claude, ChatGPT, or any other assistant you connect through Composio. Give each Onesignal rest api connection a name such as work or personal, and the assistant uses the one you mention in the request. Each account keeps its own credentials and nothing is merged.

The connection stops working the moment Onesignal rest api rejects the old key. Create a new key in Onesignal rest api and reconnect the account from the Composio dashboard or by asking your agent to reconnect Onesignal rest api. Nothing else changes.

Composio's free Hobby plan includes 100,000 tool calls per month with no credit card, which covers most personal Onesignal rest api use. Paid plans add higher limits and team features. Your Onesignal rest api plan and its API limits still apply as usual.

Built-in connectors usually give one AI access to a limited set of apps. Many people use Composio because it lets their AI connect to more apps than it normally supports, or connect to multiple accounts for the same app (e.g. connect Claude to multiple Onesignal rest api accounts).

With Composio, you connect Onesignal rest api once and then use it across different AI assistants without setting it up separately in each one. Connect your apps to Composio once, then connect Composio to whichever AI you use, whether that's Claude, ChatGPT, Hermes, or your own custom assistant.

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