How to integrate Onesignal user auth MCP with Atomic Agent

Connect Atomic Agent to Onesignal user auth MCP. Update device tags for a specific user, list all segments in your app, and more using natural language, with authentication handled for you.

Onesignal user auth logoOnesignal user auth
Api Key

OneSignal is a customer engagement platform for push notifications, email, SMS, and in-app messaging. It streamlines how businesses reach, engage, and retain their users across channels.

12 Tools

Introduction

Atomic Agent is an open-source AI agent that runs on your machine and supports local models through llama.cpp. Connect it to 1,500+ apps through Composio, including Onesignal user auth.

This guide uses Atomic Agent's built-in Composio integration. You need Atomic Agent v0.5.6 or later, your own Composio API key, and a Onesignal user auth account. See the Atomic Agent documentation for installation instructions.

Also integrate Onesignal user auth with

How Atomic Agent connects to Onesignal user auth

Atomic Agent connects to Composio's Tool Router over Streamable HTTP MCP. It discovers the tools needed for your request, and Composio handles account authentication.

Execution and account-connection tools follow Atomic Agent's configured approval policy. Review any approval prompt before allowing an action on your connected account.

Connect Onesignal user auth to Atomic Agent

  1. Sign up or sign in to the Composio dashboard. Copy your API key.
  2. In Atomic Agent, open the Integrations tab and select Composio. Select API key, press e, paste the key, and press Enter. The tools become available immediately, without a restart.
  3. Ask Atomic Agent to do something in Onesignal user auth. It searches Composio for the right tool.
  4. On first use, open the sign-in link returned in the chat. Connect your Onesignal user auth account, then return to Atomic Agent to continue.

Headless setup

Add the following line to ~/.atomic-agent/.env, replacing YOUR_COMPOSIO_API_KEY with your key. Start Atomic Agent after saving the file.

bash
COMPOSIO_API_KEY=YOUR_COMPOSIO_API_KEY

What is the Onesignal user auth MCP server, and what's possible with it?

The Onesignal user auth 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 user auth account. It provides structured and secure access to your Onesignal workspace, so your agent can perform actions like managing device tags, updating player records, inspecting app segments, and retrieving device information on your behalf.

  • Device tag management: Assign or update custom tags on OneSignal devices to enable powerful audience segmentation and personalized messaging.
  • Edit device/player attributes: Update details or attributes for any registered device (player) in your OneSignal app using your agent.
  • Segment inspection and listing: Retrieve details for specific segments or list all segments in your app to optimize and analyze your audience targeting strategies.
  • Device and app information retrieval: Look up detailed information about individual devices or your entire OneSignal app configuration as needed.
  • View device tags and metadata: Fetch all key/value tags assigned to a particular player for deeper insight into user attributes and behaviors.

Use Onesignal user auth from Atomic Agent

With your account connected, ask Atomic Agent to work with Onesignal user auth in natural language. You can connect more apps through the same Composio integration as you need them.

Visit the Atomic Agent website or inspect the Atomic Agent source code.

Troubleshooting

Why is my API key rejected?

Copy the key directly from the Composio dashboard. Atomic Agent requires ASCII characters because it sends the key in an HTTP header. Remove any extra characters introduced when copying.

Why are Composio tools unavailable after saving a key?

Check that you use Atomic Agent v0.5.6 or later and that Composio is enabled in your configuration. A "composio": { "enabled": false } setting disables the integration while keeping the saved key on disk.

Does Composio have a free plan?

The Hobby plan includes 100,000 tool calls per month. Composio-managed OAuth apps have a lower included allowance. See Composio pricing for the current limits that apply to your connection.

TOOLS

Supported Tools

Every Onesignal user auth action and event your agent gets out of the box.

Create or Update OneSignal User

Tool to create a new user or modify the subscriptions associated with an existing user.

Delete User Alias

Tool to remove an alias from a OneSignal user.

Edit OneSignal Device

Tool to update an existing OneSignal device (player) record.

View OneSignal Segment

Tool to retrieve the subscriber count for a specific OneSignal segment.

Update Subscription By Token

Tool to update properties on an existing subscription using its token.

View App

Tool to retrieve details for a specific OneSignal app.

View Broadcasts

Tool to view inbox broadcasts for a OneSignal app.

View OneSignal Device

Tool to retrieve details for a specific device/player.

View Outcomes

Tool to view all outcomes associated with a OneSignal app.

View Segments

Tool to list all segments for an app.

View OneSignal User

Tool to retrieve user details by alias label and ID.

View User Unread Message Count

Tool to retrieve the unread message count for a specific user.

FAQ

Frequently asked questions

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

Yes, you can. Atomic Agent 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 user auth tools.

Yes, absolutely. You can configure which Onesignal user auth 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 user auth data and credentials are handled as safely as possible.

Start with Onesignal user auth.It takes 30 seconds.

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

Start building