How to integrate Onesignal rest api MCP with Hermes

Hermes is a 24/7 autonomous agent that lives on your computer or server — it remembers what it learns and evolves as your usage grows. This guide explains the easiest and most robust way to connect your Onesignal rest api account to Hermes. You can do this through either Composio Connect CLI or Composio Connect MCP. For personal use we recommend the CLI, but you won't go wrong with MCP either.

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

Hermes is a 24/7 autonomous agent that lives on your computer or server — it remembers what it learns and evolves as your usage grows.

This guide explains the easiest and most robust way to connect your Onesignal rest api account to Hermes. You can do this through either Composio Connect CLI or Composio Connect MCP. For personal use we recommend the CLI, but you won't go wrong with MCP either.

Also integrate Onesignal rest api with

What is Composio Connect?

Composio Connect is a consumer offering that lets anyone plug 1,000+ applications directly into their agent harness — including Hermes. It can:

  • Search and load tools from relevant toolkits on-demand, reducing context usage.
  • Chain multiple tools to accomplish complex workflows via a remote workbench, without excessive back-and-forth with the LLM.
  • Manage app authentication end-to-end with zero manual overhead.

Integrating Onesignal rest api with Hermes

Using Composio Connect CLI

1. Install the Composio CLI

Run the install script directly, or paste https://composio.dev/hermes into your Hermes chat box to have it installed for you.

bash
curl -fsSL https://composio.dev/install | bash
Hermes authenticating with Composio

2. Authenticate

Once the CLI is installed, ask Hermes to authenticate with Composio.

3. Connect to Onesignal rest api

Ask your agent to connect to Onesignal rest api, or simply request any Onesignal rest api-related task. Hermes will prompt you to authenticate and authorize access.

4. Done. You're all set with a new Onesignal rest api connection.


Using Composio Connect MCP

1. Get your MCP URL and API Key

Go to dashboard.composio.dev and copy your Connect MCP URL and API key.

Copy MCP URL and API key from Composio dashboard

2. Open the Hermes config file

bash
nano ~/.hermes/config.yaml

3. Add the Composio Connect MCP server

bash
mcp_servers:
  composio:
    url: "https://connect.composio.dev/mcp"
    headers:
      x-consumer-api-key: "YOUR_COMPOSIO_API_KEY"
    connect_timeout: 60
    timeout: 180

Save with Ctrl + O, Enter, then exit with Ctrl + X.

4. Restart your Hermes agent

Once restarted, ask your agent to connect to Onesignal rest api or request any Onesignal rest api-related task. It will prompt you to authenticate and authorize access.

5. Done!

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.

Way Forward

With Onesignal rest api connected, Hermes can now act on your behalf whenever it detects a relevant task or you ask it to.

From here, you can extend Hermes further:

  • Connect more apps: Calendar, Slack, Notion, Linear, and hundreds of others are available through the same Composio Connect setup. Each new integration compounds what Hermes can do for you.
  • Build workflows across tools: Once multiple apps are connected, Hermes can chain actions together — turn an email into a calendar invite, a Slack message into a Linear ticket, or a meeting note into a follow-up draft.
  • Let it learn your patterns: The more you use Hermes, the better it gets at anticipating how you'd handle recurring tasks. Give it feedback on drafts and decisions, and it will adapt.

If you run into trouble or want to share what you've built, join the community or check out the Docs for deeper configuration options.

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.

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. Hermes 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