SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Onesignal rest api MCP with Claude Agent SDK

Connect Claude Agent SDK 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

This guide walks you through connecting Onesignal rest api to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Onesignal rest api agent that can send push notifications, create message templates, manage users and devices, view segments, and start live activities through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Onesignal rest api account through Composio's Onesignal rest api MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Onesignal rest api with

Claude CodeClaude CoworkOpenAI Agents SDKCodexOpenClawHermesAtomic AgentGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Onesignal rest api
  • Configure an AI agent that can use Onesignal rest api as a tool
  • Run a live chat session where you can ask the agent to perform Onesignal rest api operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

What is the Onesignal rest api MCP server, 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.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Onesignal rest api account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Onesignal rest api functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Onesignal rest api
  const session = await composio.create(USER_ID, {
    toolkits: ['onesignal_rest_api'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Onesignal rest api
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Onesignal rest api tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Onesignal rest api
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Onesignal rest api and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['onesignal_rest_api']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Onesignal rest api tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Onesignal rest api through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
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

Create a OneSignal user with optional subscriptions and aliases, or modify subscriptions associated with an existing user.

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

List segments associated with a OneSignal app, using limit and offset to page through results.

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

Claude Cowork logo

Claude Cowork

Use Onesignal rest api MCP with Claude Cowork

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Onesignal rest api MCP with OpenAI Agents 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 Agent SDK 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