Skip to main content
Glama
Notifications MCP Server

Notifications MCP Server

Related Servers

Alternatives to Notifications MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Enables Claude and other MCP clients to display native macOS notifications with customizable titles, messages, icons, and sounds through the macOS Notification Center.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for macOS native notifications with 67 AI brand icons and system sound support, enabling AI agents to send desktop notifications via one-line tool calls.
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI agents send desktop notifications during tasks, ask for attention, and report completion. Supports macOS, Linux, and Windows, with optional webhook delivery.
      835
      -
    • A
      license
      B
      quality
      D
      maintenance
      An MCP server that enables AI assistants like Claude to send native macOS notifications with tmux integration, allowing notifications to focus specific tmux sessions when clicked.
      3
      24 npm
      14
      MIT

    TDQS

    B3.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool on the server, so there is no possibility of selecting the wrong tool. The tool's dual role (start and end notifications) is handled by a single surface, but that is a completeness issue rather than an ambiguity across tools.

    Naming Consistency4/5

    With a single tool there is no cross-tool inconsistency to penalize, and 'task_status' is a readable snake_case identifier. It is a noun phrase rather than the more typical verb_noun pattern, which keeps it slightly short of ideal.

    Tool Count3/5

    Notification is a narrow purpose where one tool can suffice, but a single tool conflating start-of-response and end-of-conversation signalling is borderline thin. A parameterized stage or separate start/complete operations would make the scope feel better earned.

    Completeness2/5

    The surface offers no way to specify notification stage, type (sound vs visual), or opt-out, so an agent cannot express the distinct events the description promises. For a notification domain, the lack of any start/complete distinction or configuration options is a significant gap.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data