Bring Onesignal
to CrewAI
Learn how to connect OneSignal to CrewAI and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the OneSignal MCP Server?
Connect your OneSignal account to any AI agent and take full control of your customer engagement and notification orchestration through natural conversation. OneSignal is the market leader for omnichannel delivery, and this integration allows you to dispatch real-time push notifications, manage audience segments, and monitor delivery analytics directly from your chat interface.
What you can do
- Omnichannel Dispatch Orchestration — Send push notifications, emails, and SMS programmatically using advanced targeting and personalized content to ensure your message always lands.
- Audience & User Intelligence — Manage user profiles (players), update custom tags, and retrieve detailed device metadata directly from the AI interface to maintain a high-fidelity CRM.
- Segment & Targeting Control — Access and monitor your audience segments and apply dynamic targeting criteria via natural language to drive better engagement.
- Performance & Outcome Oversight — Retrieve granular delivery analytics, track successful/failed counts, and monitor custom outcomes using simple AI commands.
- Operational Monitoring — Track system responses and manage multiple applications to ensure your notification pipeline is always optimized.
How it works
1. Subscribe to this server
2. Enter your OneSignal App ID and REST API Key from your dashboard
3. Start managing your omnichannel delivery from Claude, Cursor, or any MCP-compatible client
No more manual logging to check open rates or send emergency alerts. Your AI acts as a dedicated engagement coordinator or growth operations manager.
Who is this for?
- Growth Marketers — quickly send promotional alerts and monitor campaign reach without switching apps.
- Product Managers — automate the delivery of transactional notifications and track user re-engagement via natural conversation.
- Operations Teams — streamline the retrieval of player metadata and monitor system alerts directly within the chat.
Built-in capabilities (12)
Stop notification
Check connection
Get application info
Check delivery metrics
Get user profile
Get campaign outcomes
List subscribed devices
List target groups
Requires User Auth Key. List your applications
List past alerts
Delete device record
Send proactive alert
Why CrewAI?
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.
- —
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
mcpsparameter 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 in CrewAI
OneSignal and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect OneSignal to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for OneSignal in CrewAI
The OneSignal 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. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
OneSignal for CrewAI
Every tool call from CrewAI to the OneSignal MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my AI automatically find the Player ID for a specific user to send a test push?
Yes! Use the list_users tool. Your agent will respond with complete metadata for registered devices, including unique Player IDs and tags, allowing you to trigger targeted pushes instantly.
How do I find my OneSignal App ID and REST API Key?
Log in to OneSignal, select your app, navigate to Settings > Keys & IDs, and you will find your unique App ID and secret REST API key there.
Can I use the AI to cancel a scheduled notification?
Absolutely. Use the cancel_notification tool with the Notification ID. The agent will instruct OneSignal to stop the broadcast immediately, provided it hasn't been fully delivered yet.
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.
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.