Notifications MCP Server

Native macOS notifications for MCP

Local serverstdioTypeScript

What is the Notifications MCP server?

Connect Notifications to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Native macOS notifications for MCP. The notifications mcp server is what makes that connection.

What the server does

An MCP server that enables AI assistants like Claude to send native macOS notifications to your computer.

  • Alerting you when a long-running task completes
  • Reminding you of important information
  • Notifying you when the AI needs your attention
  • Sending updates about ongoing processes

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • sound — System notification sound (Basso, Blow, Bottle, Frog, Funk, Glass, Hero, Morse, Ping, Pop, Purr, Sosumi, Submarine, Tink, default, or none)
  • wait — Whether to wait for user interaction
  • timeout — How long to display the notification (seconds)
  • reply — Enable reply functionality
  • actions — Action buttons (max 2)
  • icon — Path to custom icon
  • contentImage — Image to display in notification
  • closeLabel — Custom close button label
  • Scripts — The Scripts tool exposed by this server

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Notifications's toolset — sound, wait, timeout and 6 more — is a fair guide to whether it matches your workflow. It is maintained by ohqay; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Notifications's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Notifications.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
soundSystem notification sound (Basso, Blow, Bottle, Frog, Funk, Glass, Hero, Morse, Ping, Pop, Purr, Sosumi, Submarine, Tink, default, or none)
waitWhether to wait for user interaction
timeoutHow long to display the notification (seconds)
replyEnable reply functionality
actionsAction buttons (max 2)
iconPath to custom icon
contentImageImage to display in notification
closeLabelCustom close button label
ScriptsThe Scripts tool exposed by this server.

Example prompts to try

  • Use Notifications to sound.
  • Use Notifications to wait.
  • Use Notifications to timeout.

Frequently asked questions

It connects Notifications to MCP-compatible AI assistants such as Claude and Cursor, exposing 9 tools (sound, wait, timeout, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Notifications directly.