PushNotif MCP Server
Related Servers
Alternatives to PushNotif MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage OneSignal push notifications, email, SMS, and user management through natural language. Supports multi-channel messaging, segmentation, templates, analytics, and iOS Live Activities with 50+ tools for complete OneSignal API coverage.1-
- AlicenseNot gradedqualityCmaintenanceEnables sending and managing self-hosted push notifications plus applications, clients, users, plugins, and authentication operations through a REST API, with configurable toolsets and confirmation safeguards for writes.550 npmMIT
- AlicenseAqualityCmaintenanceLets AI agents send notifications, manage templates and read delivery status.128 npmMIT

ChatPush MCP Serverofficial
AlicenseAqualityCmaintenanceEnables AI agents to send WhatsApp, Telegram, SMS, VK/OK, and MAX messages, files, and bulk mailings, and to manage delivery status, webhooks, and sub-accounts.19MIT- AlicenseAqualityDmaintenanceEnables AI assistants to send push notifications and interactive alerts to iPhone and Mac devices via the BotBell app. It allows AI to receive user replies and manage notification bots for tasks like alerts, reminders, and remote approvals.26 npm1MIT
- FlicenseNot gradedqualityCmaintenanceLets AI assistants manage subscribers, trigger workflows, inspect notification events, and tune preferences across any MCP-compatible client.-
TDQS
Scored across 16 tools
Each tool targets a distinct resource+action and the descriptions include explicit 'do not use X, use Y instead' cross-references, making boundaries unusually clear. The only friction is that a few tools are multi-modal (schedule_push_notification creates, edits, and cancels campaigns; configure_rss_autopush and configure_payment_webhook take dispatch_now/simulate_test flags), so an agent must parse parameters to know which operation it is invoking.
All 16 tools are snake_case and begin with a clear action verb followed by the resource (list_apps, create_app, update_app_branding, send_push_notification, check_billing_and_qris_status). The get_/list_ split reflects genuine read-shape differences rather than convention drift, and nothing mixes casing or verb style.
16 tools is at the upper-but-reasonable end for a server spanning auth, app CRUD, push delivery, scheduling, in-app banners, RSS, payment webhooks, subscribers, analytics, and billing. Each tool maps to a real workflow step, though compressing the three schedule modes (create/edit/cancel) into one tool hints the surface could be tightened further.
Coverage is strong: full app lifecycle (list/create/update branding/delete), subscriber read+tag+unsubscribe, push send/schedule/analytics, and billing invoice+status. Minor gaps remain—there is no way to rename an app or change its site_url outside branding, no per-campaign detail fetch, and no API-key rotation or logout operation.