# How to integrate Onesignal rest api MCP with CrewAI ```json { "title": "How to integrate Onesignal rest api MCP with CrewAI", "toolkit": "Onesignal rest api", "toolkit_slug": "onesignal_rest_api", "framework": "CrewAI", "framework_slug": "crew-ai", "url": "https://composio.dev/toolkits/onesignal_rest_api/framework/crew-ai", "markdown_url": "https://composio.dev/toolkits/onesignal_rest_api/framework/crew-ai.md", "updated_at": "2026-05-12T10:20:40.184Z" } ``` ## Introduction This guide walks you through connecting Onesignal rest api to CrewAI using the Composio tool router. By the end, you'll have a working Onesignal rest api agent that can send push notification to all active users, list all devices registered for your app, view details of last 10 notifications through natural language commands. This guide will help you understand how to give your CrewAI 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 - [OpenAI Agents SDK](https://composio.dev/toolkits/onesignal_rest_api/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/onesignal_rest_api/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/onesignal_rest_api/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/onesignal_rest_api/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/onesignal_rest_api/framework/codex) - [OpenClaw](https://composio.dev/toolkits/onesignal_rest_api/framework/openclaw) - [Hermes](https://composio.dev/toolkits/onesignal_rest_api/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/onesignal_rest_api/framework/cli) - [Google ADK](https://composio.dev/toolkits/onesignal_rest_api/framework/google-adk) - [LangChain](https://composio.dev/toolkits/onesignal_rest_api/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/onesignal_rest_api/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/onesignal_rest_api/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/onesignal_rest_api/framework/llama-index) ## TL;DR Here's what you'll learn: - Get a Composio API key and configure your Onesignal rest api connection - Set up CrewAI with an MCP enabled agent - Create a Tool Router session or standalone MCP server for Onesignal rest api - Build a conversational loop where your agent can execute Onesignal rest api operations ## What is CrewAI? CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews. Key features include: - Agent Roles: Define specialized agents with specific goals and backstories - Task Management: Create tasks with clear descriptions and expected outputs - Crew Orchestration: Combine agents and tasks into collaborative workflows - MCP Integration: Connect to external tools through Model Context Protocol ## 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. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `ONESIGNAL_REST_API_BEGIN_LIVE_ACTIVITY` | Begin Live Activity | Tool to start a Live Activity on OneSignal. Use when you need to initiate a Live Activity session with a push token and subscription ID. | | `ONESIGNAL_REST_API_CREATE_NOTIFICATION` | Create Notification | Tool to create and send a OneSignal push notification. Use when you have your message and target audience ready to dispatch notifications. | | `ONESIGNAL_REST_API_CREATE_TEMPLATE` | Create Template | Tool to create reusable message templates for push, email, and SMS channels. Use when you need to create a template that can be accessed through both the dashboard and API using a template_id. | | `ONESIGNAL_REST_API_CREATE_USER` | Create User | Tool to create a OneSignal user with optional subscriptions and aliases. Aliases provided in the payload will be used to look up an existing user. | | `ONESIGNAL_REST_API_DELETE_ALIAS` | Delete Alias | Tool to delete an alias by alias label from a OneSignal user. Use when you need to remove a specific alias identity from a user's profile. | | `ONESIGNAL_REST_API_DELETE_DEVICE` | Delete Device | Tool to delete a device (player) from a OneSignal app. Use when you need to remove a specific device by its player ID. | | `ONESIGNAL_REST_API_FETCH_USER_IDENTITY` | Fetch User Identity | Tool to retrieve all aliases for a user identified by a specific alias. Use when you need to fetch the complete identity mapping for a OneSignal user. | | `ONESIGNAL_REST_API_GET_ELIGIBLE_IAMS` | Get Eligible In-App Messages | Tool to retrieve the manifest of In-App Messages that a subscription is eligible to display. Use when you need to fetch eligible IAMs for a specific subscription. | | `ONESIGNAL_REST_API_UPDATE_DEVICE` | Update Device | Tool to update properties of an existing device. Use when you need to modify device attributes after registration. | | `ONESIGNAL_REST_API_UPDATE_SUBSCRIPTION` | Update Subscription | Tool to update an existing subscription's properties. Use when you need to modify subscription attributes like token, enabled status, or device information. | | `ONESIGNAL_REST_API_VIEW_AN_APP` | View OneSignal App | Tool to retrieve metadata for a single OneSignal app. Use when you need to fetch app details by its ID. | | `ONESIGNAL_REST_API_VIEW_DEVICE` | View Device | Tool to retrieve details of a specific device (player). Use when you have a OneSignal player_id and need current device info. | | `ONESIGNAL_REST_API_VIEW_DEVICES` | View Devices | Tool to retrieve a paginated list of devices (players) for a OneSignal app. Use when you need to list or audit all registered devices for a given app. | | `ONESIGNAL_REST_API_VIEW_NOTIFICATIONS` | View Notifications | Tool to retrieve details of multiple notifications. Use when you need to list notifications for a specific app. | | `ONESIGNAL_REST_API_VIEW_SEGMENTS` | View Segments | Tool to view segments for a OneSignal app. Use when you need to list all segments associated with an app. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Onesignal rest api MCP server is an implementation of the Model Context Protocol that connects your AI agent to Onesignal rest api. It provides structured and secure access so your agent can perform Onesignal rest api operations on your behalf through a secure, permission-based interface. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites Before starting, make sure you have: - Python 3.9 or higher - A Composio account and API key - A Onesignal rest api connection authorized in Composio - An OpenAI API key for the CrewAI LLM - Basic familiarity with Python ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models, or you can connect to another model provider. - Keep the API key safe. Composio API Key - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Navigate to your API settings and generate a new API key. - Store this key securely as you'll need it for authentication. ### 2. Install dependencies **What's happening:** - composio connects your agent to Onesignal rest api via MCP - crewai provides Agent, Task, Crew, and LLM primitives - crewai-tools[mcp] includes MCP helpers - python-dotenv loads environment variables from .env ```bash pip install composio crewai crewai-tools[mcp] python-dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's happening: - COMPOSIO_API_KEY authenticates with Composio - USER_ID scopes the session to your account - OPENAI_API_KEY lets CrewAI use your chosen OpenAI model ```bash COMPOSIO_API_KEY=your_composio_api_key_here USER_ID=your_user_id_here OPENAI_API_KEY=your_openai_api_key_here ``` ### 4. Import dependencies **What's happening:** - CrewAI classes define agents and tasks, and run the workflow - MCPServerHTTP connects the agent to an MCP endpoint - Composio will give you a short lived Onesignal rest api MCP URL ```python import os from composio import Composio from crewai import Agent, Task, Crew from crewai_tools import MCPServerAdapter import dotenv dotenv.load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID") if not COMPOSIO_API_KEY: raise ValueError("COMPOSIO_API_KEY is not set") if not COMPOSIO_USER_ID: raise ValueError("COMPOSIO_USER_ID is not set") ``` ### 5. Create a Composio Tool Router session for Onesignal rest api **What's happening:** - You create a Onesignal rest api only session through Composio - Composio returns an MCP HTTP URL that exposes Onesignal rest api tools ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["onesignal_rest_api"]) url = session.mcp.url ``` ### 6. Initialize the MCP Server **What's Happening:** - Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication. - MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format. - Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools. - Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops. - Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries. ```python server_params = { "url": url, "transport": "streamable-http", "headers": {"x-api-key": COMPOSIO_API_KEY}, } with MCPServerAdapter(server_params) as tools: agent = Agent( role="Search Assistant", goal="Help users search the internet effectively", backstory="You are a helpful assistant with access to search tools.", tools=tools, verbose=False, max_iter=10, ) ``` ### 7. Create a CLI Chatloop and define the Crew **What's Happening:** - Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable. - Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean. - Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses. - Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context. - Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response. - Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity. ```python print("Chat started! Type 'exit' or 'quit' to end.\n") conversation_context = "" while True: user_input = input("You: ").strip() if user_input.lower() in ["exit", "quit", "bye"]: print("\nGoodbye!") break if not user_input: continue conversation_context += f"\nUser: {user_input}\n" print("\nAgent is thinking...\n") task = Task( description=( f"Conversation history:\n{conversation_context}\n\n" f"Current request: {user_input}" ), expected_output="A helpful response addressing the user's request", agent=agent, ) crew = Crew(agents=[agent], tasks=[task], verbose=False) result = crew.kickoff() response = str(result) conversation_context += f"Agent: {response}\n" print(f"Agent: {response}\n") ``` ## Complete Code ```python from crewai import Agent, Task, Crew, LLM from crewai_tools import MCPServerAdapter from composio import Composio from dotenv import load_dotenv import os load_dotenv() GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY") COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID") if not GOOGLE_API_KEY: raise ValueError("GOOGLE_API_KEY is not set in the environment.") if not COMPOSIO_API_KEY: raise ValueError("COMPOSIO_API_KEY is not set in the environment.") if not COMPOSIO_USER_ID: raise ValueError("COMPOSIO_USER_ID is not set in the environment.") # Initialize Composio and create a session composio = Composio(api_key=COMPOSIO_API_KEY) session = composio.create( user_id=COMPOSIO_USER_ID, toolkits=["onesignal_rest_api"], ) url = session.mcp.url # Configure LLM llm = LLM( model="gpt-5", api_key=os.getenv("OPENAI_API_KEY"), ) server_params = { "url": url, "transport": "streamable-http", "headers": {"x-api-key": COMPOSIO_API_KEY}, } with MCPServerAdapter(server_params) as tools: agent = Agent( role="Search Assistant", goal="Help users with internet searches", backstory="You are an expert assistant with access to Composio Search tools.", tools=tools, llm=llm, verbose=False, max_iter=10, ) print("Chat started! Type 'exit' or 'quit' to end.\n") conversation_context = "" while True: user_input = input("You: ").strip() if user_input.lower() in ["exit", "quit", "bye"]: print("\nGoodbye!") break if not user_input: continue conversation_context += f"\nUser: {user_input}\n" print("\nAgent is thinking...\n") task = Task( description=( f"Conversation history:\n{conversation_context}\n\n" f"Current request: {user_input}" ), expected_output="A helpful response addressing the user's request", agent=agent, ) crew = Crew(agents=[agent], tasks=[task], verbose=False) result = crew.kickoff() response = str(result) conversation_context += f"Agent: {response}\n" print(f"Agent: {response}\n") ``` ## Conclusion You now have a CrewAI agent connected to Onesignal rest api through Composio's Tool Router. The agent can perform Onesignal rest api operations through natural language commands. Next steps: - Add role-specific instructions to customize agent behavior - Plug in more toolkits for multi-app workflows - Chain tasks for complex multi-step operations ## How to build Onesignal rest api MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/onesignal_rest_api/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/onesignal_rest_api/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/onesignal_rest_api/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/onesignal_rest_api/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/onesignal_rest_api/framework/codex) - [OpenClaw](https://composio.dev/toolkits/onesignal_rest_api/framework/openclaw) - [Hermes](https://composio.dev/toolkits/onesignal_rest_api/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/onesignal_rest_api/framework/cli) - [Google ADK](https://composio.dev/toolkits/onesignal_rest_api/framework/google-adk) - [LangChain](https://composio.dev/toolkits/onesignal_rest_api/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/onesignal_rest_api/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/onesignal_rest_api/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/onesignal_rest_api/framework/llama-index) ## Related Toolkits - [Reddit](https://composio.dev/toolkits/reddit) - Reddit is a social news platform with thriving user-driven communities (subreddits). It's the go-to place for discussion, content sharing, and viral marketing. - [Facebook](https://composio.dev/toolkits/facebook) - Facebook is a social media and advertising platform for businesses and creators. It helps you connect, share, and manage content across your public Facebook Pages. - [Linkedin](https://composio.dev/toolkits/linkedin) - LinkedIn is a professional networking platform for connecting, sharing content, and engaging with business opportunities. It's the go-to place for building your professional brand and unlocking new career connections. - [Active campaign](https://composio.dev/toolkits/active_campaign) - ActiveCampaign is a marketing automation and CRM platform for managing email campaigns, sales pipelines, and customer segmentation. It helps businesses engage customers and drive growth through smart automation and targeted outreach. - [ActiveTrail](https://composio.dev/toolkits/active_trail) - ActiveTrail is a user-friendly email marketing and automation platform. It helps you reach subscribers and automate campaigns with ease. - [Ahrefs](https://composio.dev/toolkits/ahrefs) - Ahrefs is an SEO and marketing platform for site audits, keyword research, and competitor insights. It helps you improve search rankings and drive organic traffic. - [Amcards](https://composio.dev/toolkits/amcards) - AMCards lets you create and mail personalized greeting cards online. Build stronger customer relationships with easy, automated card campaigns. - [Beamer](https://composio.dev/toolkits/beamer) - Beamer is a news and changelog platform for in-app announcements and feature updates. It helps companies boost user engagement by sharing news where users are most active. - [Benchmark email](https://composio.dev/toolkits/benchmark_email) - Benchmark Email is a platform for creating, sending, and tracking email campaigns. It's built to help you engage audiences and analyze results—all in one place. - [Bigmailer](https://composio.dev/toolkits/bigmailer) - BigMailer is an email marketing platform for managing multiple brands with white-labeling and automation. It helps teams streamline campaigns and simplify integration with Amazon SES. - [Brandfetch](https://composio.dev/toolkits/brandfetch) - Brandfetch is an API that delivers company logos, colors, and visual branding assets. It helps marketers and developers keep brand visuals consistent everywhere. - [Brevo](https://composio.dev/toolkits/brevo) - Brevo is an all-in-one email and SMS marketing platform for transactional messaging, automation, and CRM. It helps businesses engage customers and streamline communications through powerful campaign tools. - [Campayn](https://composio.dev/toolkits/campayn) - Campayn is an email marketing platform for creating, sending, and managing campaigns. It helps businesses engage contacts and grow audiences with easy-to-use tools. - [Cardly](https://composio.dev/toolkits/cardly) - Cardly is a platform for creating and sending personalized direct mail to customers. It helps businesses break through the digital clutter by getting real engagement via physical mailboxes. - [ClickSend](https://composio.dev/toolkits/clicksend) - ClickSend is a cloud-based SMS and email marketing platform for businesses. It streamlines communication by enabling quick message delivery and contact management. - [Crustdata](https://composio.dev/toolkits/crustdata) - CrustData is an AI-powered data intelligence platform for real-time company and people data. It helps B2B sales teams, AI SDRs, and investors react to live business signals. - [Curated](https://composio.dev/toolkits/curated) - Curated is a platform for collecting, curating, and publishing newsletters. It streamlines content aggregation and distribution for creators and teams. - [Customerio](https://composio.dev/toolkits/customerio) - Customer.io is a customer engagement platform for targeted messaging across email, SMS, and push. Easily automate, segment, and track communications with your audience. - [Cutt ly](https://composio.dev/toolkits/cutt_ly) - Cutt.ly is a URL shortening service for managing and analyzing links. Streamline your workflows with quick, trackable, and branded short URLs. - [Demio](https://composio.dev/toolkits/demio) - Demio is webinar software built for marketers, offering both live and automated sessions with interactive features. It helps teams engage audiences and optimize lead generation through detailed analytics. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Onesignal rest api MCP? 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. ### Can I use Tool Router MCP with CrewAI? Yes, you can. CrewAI 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. ### Can I manage the permissions and scopes for Onesignal rest api while using Tool Router? 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. ### How safe is my data with Composio Tool Router? 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. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)