X (Twitter)LinkedInGitHubDiscordYouTube

How to connect Onesignal user auth to Claude

Connect Claude Web, Desktop and Cowork 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.

Get started for freeGet a demo
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

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 user auth account to Claude via Composio Connect, enabling it to update device tags for a specific user, list all segments in your app, fetch tags assigned to player ID 123, 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 user auth with

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

Connecting Onesignal user auth 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 user auth account

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

For example, ask Claude to:

  • "Update device tags for a specific user"
  • "List all segments in your app"
  • "Fetch tags assigned to player ID 123"

It will prompt you to authenticate and authorize access.

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

What is the Onesignal user auth Claude Connector, 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.

Troubleshooting

1. Why does Claude not use the Composio connector for Onesignal user auth?

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

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

2. Why does Claude show an MCP server error before Onesignal user auth connects?

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

  • 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 user auth.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Onesignal user auth authorization link not work?

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

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

4. Why do Onesignal user auth actions fail after they worked before?

The Onesignal user auth connection can expire or lose permission.

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

5. How do I switch to a different Onesignal user auth account?

Claude can manage the Onesignal user auth connection for you.

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

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

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

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If Onesignal user auth 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 user auth.
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.

FRAMEWORKS

How to build Onesignal user auth MCP Agent with another framework

Claude Code logo

Claude Code

Use Onesignal user auth MCP with Claude Code

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Onesignal user auth MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Onesignal user auth MCP with Claude Agent SDK

Codex logo

Codex

Use Onesignal user auth MCP with Codex

OpenClaw logo

OpenClaw

Use Onesignal user auth MCP with OpenClaw

Hermes logo

Hermes

Use Onesignal user auth MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Onesignal user auth MCP with Atomic Agent

Google ADK logo

Google ADK

Use Onesignal user auth MCP with Google ADK

LangChain logo

LangChain

Use Onesignal user auth MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Onesignal user auth MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Onesignal user auth MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Onesignal user auth MCP with LlamaIndex

CrewAI logo

CrewAI

Use Onesignal user auth MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Onesignal user auth MCP with Pydantic AI

AutoGen logo

AutoGen

Use Onesignal user auth MCP with AutoGen

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