Skip to main content
Glama
Artemeey

mcp-notifications

by Artemeey

mcp-notifications

npm version

๐Ÿš€ Ship faster. Miss nothing.

mcp-notifications lets your MCP agent send desktop notifications for completed tasks, failures, and important updates.

This is especially useful for console AI agents, because they usually have no built-in notifications by default.

No more checking chats every minute.
No more silent agent responses.
Just visible, reliable feedback on your desktop. ๐Ÿ””

Common problem this solves

You give tasks to several AI agents, then wait and keep checking who already replied.

With mcp-notifications, this gets simpler: the agent can notify you on desktop when it needs your input or when work is done.

Related MCP server: Desktop Notification MCP Server

Why teams install this

  • โšก Immediate feedback from your MCP workflows.

  • ๐Ÿง  Better focus: let the agent work while you stay on your main task.

  • ๐Ÿ–ฅ๏ธ Native OS notifications via node-notifier.

  • ๐Ÿงต Non-blocking behavior: notification sending is queued in background.

Install globally

Requirements:

  • Node.js >=20

  • npm >=10

npm i -g @topvisor/mcp-notifications

Executable name (use this in MCP config):

mcp-notifications

mcp-notifications is an MCP server entrypoint (stdio), not a one-shot notification command.

Setup: Codex

Add this to ~/.codex/config.toml:

[mcp_servers.notifications]
enabled = true
command = "mcp-notifications"
args = []

Restart Codex after config update.

Setup: Claude Agent

Add MCP server config to your Claude client config file:

{
  "mcpServers": {
    "notifications": {
      "command": "mcp-notifications",
      "args": []
    }
  }
}

Then restart Claude client.

AI Agent Notification Instructions

There are two approaches to notifications: manual and automatic.

Choose the one that works better for your workflow.

Manual

In a task where you want to be notified, explicitly ask the agent. Example:

Count files in the project; after the task is fully complete, notify me with sound.

You can also define sound, topic, and frequency rules inside a specific chat. Example:

Notify me about your replies without sound, include the reply text, and use title: "Large Refactoring"

Automatic

Automatic notifications can be configured globally or per project.

Example instruction to enable automatic notifications for agent replies:

Send `send_notification` after your replies (actual task time >5 seconds or many steps); `play_sound: false`; `app_id: '{put your chat name here}'`

Time is a rough threshold and depends on model behavior, so adjust this instruction to your own preferences.

In Skills

You can also enable notifications in specific skills. Example for a Review skill:

After the review, run `send_notification` with a short summary; `play_sound: true`; `app_id: 'Reviewer {put task id here}'`

Tool

send_notification

Input:

  • title string (required)

  • message string (required)

  • play_sound boolean (optional, default: false)

  • icon string (optional, absolute or relative path to image file)

  • app_id string (optional, Windows App User Model ID for toast source)

Example:

{
  "title": "Codex",
  "message": "Deployment completed successfully",
  "play_sound": true,
  "icon": "/opt/mcp-notifications/icons/custom.png",
  "app_id": "Topvisor.Codex"
}

app_id (Windows)

  • app_id controls the source shown in Windows toast notifications.

  • If app_id is not set, Windows may show SnoreToast as the source.

  • You can pass app_id in each tool call, or set MCP_NOTIFICATIONS_APP_ID as an environment variable for the server.

Backend selection

You can select notification transport via env MCP_NOTIFICATIONS_BACKEND:

  • auto (default): uses powershell in WSL if available, otherwise node-notifier

  • powershell: force powershell.exe Windows toast transport (recommended for WSL)

  • node-notifier: force node-notifier package

Chat Prompts To Test In Codex

Use these messages directly in chat:

Check send_notification
Send a notification without sound: title "Test", message "Check"
Send a notification with sound: title "Test", message "Check"
Send a notification with app_id "Topvisor.Codex": title "Test", message "Check"
Send 3 test notifications in a row without sound

Expected tool result in logs/response:

Notification queued

Behavior

  • โœ… Uses standard system notification channels.

  • ๐Ÿ”Š Uses the standard system notification sound when play_sound: true.

  • ๐Ÿค– Uses bundled Topvisor robot image as default notification icon.

  • ๐Ÿงฐ Returns quickly while notifications are delivered in background queue.

Example

The AI agent is waiting for you:

example.png

Available Tools

1 tool
send_notificationD
ParametersJSON Schema
NameRequiredDescriptionDefault
titleYes
messageYes
play_soundNo
iconNo
app_idNo

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.5
    • First observedsend_notification

TDQS

D1.7/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion between tools. The single tool's purpose is clear even without description.

Naming Consistency5/5

A single tool allows perfect naming consistency; 'send_notification' follows a clear verb_noun pattern in snake_case.

Tool Count2/5

A single tool for a notification server seems too minimal; typical systems need at least send, list, and delete capabilities, making the count insufficient for the domain.

Completeness1/5

The tool surface is severely incomplete. Only a send operation is provided, with no ability to retrieve, manage, or delete notifications, and the lack of tool description worsens the situation.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • A
    license
    A
    quality
    C
    maintenance
    ไธ€ไธช่ฝป้‡็บง็š„ๆกŒ้ข้€š็Ÿฅๅทฅๅ…ท๏ผŒๆ”ฏๆŒ MCP ๅ่ฎฎ้›†ๆˆๅ’Œๅ‘ฝไปค่กŒ็›ดๆŽฅ่ฐƒ็”จ๏ผŒ่ฎฉ Agent ่ƒฝๅคŸๆ™บ่ƒฝๅ‘้€็ณป็ปŸ้€š็Ÿฅใ€‚
    1
    19
    4
    MIT
  • A
    license
    B
    quality
    C
    maintenance
    An MCP server that lets LLM agents dispatch native OS notifications when a task finishes. It supports cross-platform desktop notifications, task tokens for updates, mobile bridges, and quiet hours.
    2
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Artemeey/mcp-notifications'

If you have feedback or need assistance with the MCP directory API, please join our Discord server