Skip to main content
Glama

Related Servers

Alternatives to PushNotif MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables 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
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      2
      10 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Lets AI assistants manage subscribers, trigger workflows, inspect notification events, and tune preferences across any MCP-compatible client.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables multiple AI coding sessions (Claude Code, Codex, Opencode, scripts and CI bots) to exchange messages in real time, either directly by name or broadcast, with grouping into isolated rooms and queued delivery for offline agents. Supports push notifications into Claude Code conversations, long-poll waiting, HTTP webhooks and WebSocket agents, plus token authentication.
      6
      MIT

    TDQS

    A4.5/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource+action, and descriptions actively cross-reference the nearest confusable sibling (e.g. send vs. schedule vs. configure_inapp_banner vs. configure_rss_autopush, update_profile vs. update_app_branding). The send/schedule/banner/RSS quartet are all notification-adjacent yet cleanly separated by channel and timing. An agent can reliably pick the right tool.

    Naming Consistency5/5

    Consistent snake_case verb_noun pattern throughout (list_apps, create_app, send_push_notification, configure_inapp_banner, check_billing_and_qris_status). Verbs are used with stable meaning (list/get for reads, create/configure/update for writes, check for status). No style mixing.

    Tool Count4/5

    17 tools is slightly above the ideal 3-15 range but each earns its place given the broad domain (auth, apps, notifications, mobile/RSS/in-app channels, billing, analytics, subscribers). No obvious redundancy or filler tools. Marginally heavy but well-scoped for the feature surface.

    Completeness4/5

    Strong lifecycle coverage: registration/login, app creation and branding, multi-channel sending, scheduling/cancel, billing, analytics, subscriber inspection, and integration guides. Minor gaps remain—no delete_app, no subscriber/tag management, and scheduled campaigns can only be canceled, not edited. These are workaround-able, so a small deduction only.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues