Skip to main content
Glama
nkyy

Claude Code Notification Hooks

by nkyy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Claude Code Notification Hooks

No user-submitted related servers found.

    Related Servers

    • notify-mcp

      ShikeChen01
      A
      license
      Not graded
      quality
      D
      maintenance
      Sends native Windows desktop notifications with repeating sound alerts for Claude Code, supporting states like finished, needs_help, and pending_review.
      25 npm
      MIT

    • Sound Effects MCP

      sawa-zen
      A
      license
      B
      quality
      D
      maintenance
      Plays sound effects (completion, newtype, and error sounds) in response to various situations like task completion, insights, or errors. Integrates with Claude Desktop to provide audio feedback for improved workflow efficiency and entertainment.
      2
      6 npm
      6
      MIT

    • AI Notify MCP

      zhiyingzzhou
      F
      license
      C
      quality
      D
      maintenance
      Sends system notifications when AI completes responses in MCP-compatible code editors, with cross-platform support for macOS, Windows, and Linux including customizable titles, messages, icons, and sound effects.
      2
      -

    • mcp-windows-notify

      timtoday
      A
      license
      B
      quality
      D
      maintenance
      Enables AI development tools on Windows to send native system notifications for task completion, errors, and reminders, with customizable icons and sounds.
      7
      10 npm
      7
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 4 tools

    Disambiguation3/5

    The tools have overlapping purposes despite different names, as all are notification tools with specific triggers. The descriptions help differentiate contexts (errors, task completion, user actions, general auto-notification), but the boundaries are somewhat fuzzy, especially between auto_notify_if_appropriate and the more specific tools. An agent might struggle to choose between them in ambiguous situations.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern (e.g., send_error_notification, send_task_complete_notification), with all tools using snake_case. The only deviation is auto_notify_if_appropriate, which uses a slightly different verb style ('auto_notify' vs. 'send'), but overall, the naming is predictable and readable.

    Tool Count5/5

    With 4 tools, the count is well-scoped for a notification server. Each tool serves a distinct notification type (errors, task completion, user actions, general auto-notification), and there are no unnecessary redundancies. This number allows for focused coverage without being overwhelming or too sparse.

    Completeness5/5

    The tool set comprehensively covers the notification domain for code-related contexts. It includes notifications for errors, task completions, user actions, and general auto-notification, ensuring no gaps in common scenarios like failures, successes, or required interactions. This provides a complete lifecycle of notification needs without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources