Bring Push Notifications
to CrewAI
Learn how to connect ntfy (Push Notifications) to CrewAI and start using 2 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the ntfy (Push Notifications) MCP Server?
Connect your ntfy instance to any AI agent and manage real-time alerts and notifications through natural conversation. ntfy is an HTTP-based pub-sub service that allows you to send notifications to your phone or desktop via scripts or APIs.
What you can do
- Instant Publishing — Send messages to any ntfy topic with custom titles, priorities, and tags (emojis).
- Message Polling — Retrieve cached messages from a topic to stay updated on previous alerts or system logs.
- Rich Notifications — Attach clickable URLs, custom icons, and even files to your push notifications.
- Scheduled Alerts — Use the delay parameter to schedule notifications for the future.
- Advanced Formatting — Send notifications with Markdown support for better readability on supported clients.
How it works
- Subscribe to this server
- Enter your ntfy instance URL (e.g.,
https://ntfy.sh) and an optional access token - Start sending alerts from Claude, Cursor, or any MCP-compatible client
Who is this for?
- DevOps Engineers — Automate deployment alerts and system monitoring notifications directly from the terminal or IDE.
- Developers — Send debugging info or long-running task completions to your phone.
- Power Users — Create custom workflows that bridge AI agents with mobile push notifications without complex setups.
Built-in capabilities (2)
Poll cached messages from a ntfy topic
Topics are created on the fly. Publish a push notification to a ntfy topic
Why CrewAI?
When paired with CrewAI, ntfy (Push Notifications) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call ntfy (Push Notifications) 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
ntfy (Push Notifications) in CrewAI
ntfy (Push Notifications) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect ntfy (Push Notifications) 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 | 4,000+ 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 ntfy (Push Notifications) in CrewAI
The ntfy (Push Notifications) 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 2 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
ntfy (Push Notifications) for CrewAI
Every tool call from CrewAI to the ntfy (Push Notifications) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I send emojis in my notifications?
Yes! Use the tags parameter in the publish_message tool. You can provide a comma-separated list of emojis or tags like 'warning,skull' to display them in the notification.
How do I check for messages that were sent while I was away?
You can use the poll_messages tool. By specifying the topic and optionally the since parameter, you can retrieve the history of cached messages from that topic.
Does this support self-hosted ntfy instances?
Absolutely. During setup, you can provide your custom NTFY_URL. If your instance requires authentication, you can also provide your NTFY_TOKEN.
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.
Explore More MCP Servers
View all →
DCL Logistics
10 toolsEquip your AI agent to manage order fulfillment, track shipments, and monitor warehouse inventory via the DCL Logistics API.
EPA AirNow
3 toolsMonitor localized air quality indices and critical environmental forecasts directly from the Environmental Protection Agency.
Eventbrite
12 toolsCreate events, sell tickets, and manage attendees with the world largest self-service ticketing platform for any occasion.
ButterCMS
10 toolsOperate Headless publishing via ButterCMS — search your blog posts, extract custom categories, and map collections with any AI agent.