Can I target specific users instead of sending to everyone?

Yes! Use the `create_notification` tool and provide a list of `include_player_ids`. This ensures the notification is only delivered to the specific devices you've identified.

How can I check if a scheduled notification was actually sent?

You can use the `get_notification` tool with the Notification ID. It will return real-time delivery metrics, including the number of successful deliveries and current status.

Is it possible to manage multiple OneSignal apps?

Yes. While the core operations use the primary App ID provided in credentials, you can use `list_apps` (requires User Auth Key) to see all your applications and their respective IDs.

OneSignal MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: OneSignal
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to OneSignal through Vinkius, pass the Edge URL in the `mcps` parameter and every OneSignal tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="OneSignal Specialist",
    goal="Help users interact with OneSignal effectively",
    backstory=(
        "You are an expert at leveraging OneSignal tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in OneSignal "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About OneSignal MCP Server

Connect your OneSignal account to any AI agent and take full control of your customer engagement workflows through natural conversation.

When paired with CrewAI, OneSignal becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call OneSignal tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Notifications Management — Send, schedule, and cancel push notifications across mobile and web platforms.
Audience Targeting — Target specific segments or individual player IDs to ensure the right message reaches the right user.
Delivery Analytics — Fetch detailed reports and metrics for any notification to understand your engagement levels.
Device Management — List, inspect, and manage registered devices (players) within your OneSignal applications.
App Overview — List all your OneSignal apps and configurations to maintain a bird's-eye view of your notification infrastructure.

The OneSignal MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect OneSignal to CrewAI via MCP

Follow these steps to integrate the OneSignal MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from OneSignal

Why Use CrewAI with the OneSignal MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with OneSignal through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

OneSignal + CrewAI Use Cases

Practical scenarios where CrewAI combined with the OneSignal MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries OneSignal for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries OneSignal, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain OneSignal tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries OneSignal against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

OneSignal MCP Tools for CrewAI (10)

These 10 tools become available when you connect OneSignal to CrewAI via MCP:

cancel_notification

Cancel a scheduled notification

create_notification

Send a OneSignal notification

delete_player

Delete a registered device

get_app

Requires User Auth Key. Get details for a specific OneSignal app

get_notification

Get specific notification status

get_outcomes

Get outcome data for the app

get_player

Get specific player details

list_apps

Requires User Auth Key. List all OneSignal apps

list_notifications

List notifications sent for the app

list_players

List registered devices (players)

Example Prompts for OneSignal in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with OneSignal immediately.

"Send a push notification to all subscribed users saying 'Flash Sale: 50% off today only!'"

"Check the delivery status of notification 550e8400-e29b-41d4-a716-446655440000."

"List the last 5 registered devices for our app."

Troubleshooting OneSignal MCP Server with CrewAI

Common issues when connecting OneSignal to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

OneSignal + CrewAI FAQ

Common questions about integrating OneSignal MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.