Bring Push Notifications
to CrewAI
Learn how to connect iZooto to CrewAI and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the iZooto MCP Server?
Connect your iZooto account to any AI agent and take full control of your push notification orchestration and audience efficiency through natural conversation. iZooto provides a powerful platform for web and mobile push engagement, and this integration allows you to retrieve audience metadata, dispatch automated notification campaigns, and monitor real-time performance statistics directly from your chat interface.
What you can do
- Campaign & Push Orchestration — Send push notifications to all subscribers or specific segments programmatically to ensure your marketing reach is always synchronized.
- Audience & Segment Intelligence — Access and monitor your defined audience segments and retrieve detailed reach metadata directly from the AI interface to track growth trends.
- Engagement & Performance Oversight — Retrieve granular details for campaign clicks, impressions, and CTR using simple AI commands to maintain high-visibility marketing transparency.
- UTM & Asset Control — Configure UTM parameters and manage notification content via natural language to drive better conversion tracking and asset consistency.
- Operational Monitoring — Track system responses and manage push schedules to ensure your customer engagement workflows are always optimized.
How it works
1. Subscribe to this server
2. Enter your iZooto API Token from your general settings
3. Start managing your push notifications from Claude, Cursor, or any MCP-compatible client
No more manual logging into the dashboard for basic campaign checks. Your AI acts as a dedicated marketing coordinator or push notification analyst assistant.
Who is this for?
- Marketing Managers — quickly retrieve campaign summaries and monitor audience growth without switching apps.
- Content Creators — automate the dispatch of new post notifications and track engagement via natural conversation.
- E-commerce Owners — streamline the retrieval of promotional campaign stats and monitor customer reach directly within the chat.
Built-in capabilities (10)
Verify iZooto API connectivity
Create an audience segment
Get notification details
Get push analytics
Get total subscriber count
List audience overview
List sent notifications
List all segments
Send a push notification
Send push to a segment
Why CrewAI?
When paired with CrewAI, iZooto becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call iZooto 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
iZooto in CrewAI
iZooto and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect iZooto 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 iZooto in CrewAI
The iZooto 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 10 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
iZooto for CrewAI
Every tool call from CrewAI to the iZooto MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I send a push notification via AI?
Use the send_push tool with a title, message body, and optional landing URL. Your notification is delivered instantly to all subscribers.
Can I target specific audience segments?
Yes. Use send_segment_push to target a specific segment, or create new segments with create_segment using custom targeting rules.
How do I check notification performance?
Use get_stats for aggregate analytics or get_notification with an ID to see impressions, clicks, and CTR for a specific notification.
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.