Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-notify Notify me when the deployment finishes with a summary of the result."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Minimal MCP server that plays a notification sound and shows a system banner on your computer whenever your AI agent finishes a task or needs your attention.
Works with any MCP client: Claude Desktop, Claude Code, Cursor, VS Code, opencode, Cline, and more. One 3-line config, no API keys, no network calls — it only touches your local audio and notification facilities.
Add to your client's MCP config (Claude Desktop claude_desktop_config.json, Cursor / VS Code mcp.json, or opencode config):
{
"mcpServers": {
"mcp-notify": {
"command": "npx",
"args": ["-y", "@mrfqcentic/mcp-notify"]
}
}
}(opencode users: same shape under the mcp key with "type": "local" and "command": ["npx", "-y", "@mrfqcentic/mcp-notify"].)
Requires Node.js >= 20.
Related MCP server: Notifications MCP Server
Add one line to your AGENTS.md / CLAUDE.md / system prompt:
When a task is done or the user should be alerted, call the `notify` tool with a short title and a 1–2 sentence description of the result.notifyPlays the sound and shows a banner. The agent always supplies title (max 50 chars) and message (max 200 chars).
Param | Required | Description |
| yes | Short banner title, e.g. "Build finished" |
| yes | 1–2 sentence description, e.g. "All 142 tests passed" |
| no | Absolute path to any audio/video file with audio (mp4, m4a, mp3, wav, aiff) |
list_soundsLists available sounds and the currently selected default.
Resolution order:
NOTIFY_SOUND env var — absolute path, explicit and deterministic
A file in the sounds/ folder whose name starts with default (your pin)
First audio file in the sounds/ folder (alphabetical — notify-me.mp3 ships here as the bundled default)
The generated chime in assets/
The system sound (macOS Glass.aiff, Linux bell.oga)
Tip: rename or copy your favorite sound to sounds/default.mp3 (or set NOTIFY_SOUND) to make it stick.
The bundled sounds/notify-me.mp3 was generated with ElevenLabs under a commercial license.
{
"mcpServers": {
"mcp-notify": {
"command": "npx",
"args": ["-y", "@mrfqcentic/mcp-notify"],
"env": { "NOTIFY_SOUND": "/absolute/path/to/your-sound.mp3" }
}
}
}Tip: MP4 files with an audio track work too (macOS afplay reads the audio stream).
OS | Sound | Banner |
macOS |
|
|
Linux |
|
|
Windows | PowerShell | PowerShell |
Any CI env value makes sound and banner playback no-ops (set automatically in CI workflows) so the test suite can run on machines without audio.
npm install
npm run typecheck
npm test # builds, then runs the e2e suite (sound + banner fire locally)MIT — see LICENSE.
List audio files available to the notify tool and the currently selected default sound. Resolution order: NOTIFY_SOUND env var, sounds/default* file, first file in sounds/, bundled chime, system sound.
Inputs: no named parameters.
Play a notification sound on the user's computer and show a system banner. Call this whenever a task is done, something needs the user's attention, or the user asks to be notified. Always write a concise, human-friendly title and message describing what just happened or needs attention (e.g. title: 'Build finished', message: 'All 142 tests passed, no errors.'). Default sound resolution: NOTIFY_SOUND env var, then a sounds/default* file, then the first file in this server's sounds/ folder, then the bundled chime, then the system sound. You can pass an absolute path to any audio/video file with audio (mp4, m4a, mp3, wav, aiff) in sound.
Inputs: title (required), message (required), sound.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 2 tools
The two tools serve entirely different functions: notify triggers the notification while list_sounds enumerates available sounds and the default. There is no overlap or ambiguity between them.
Both tools use imperative verbs ('notify', 'list_sounds'), but 'notify' lacks a noun object unlike 'list_sounds' which follows verb_noun. Still, they are clear and predictable with no style mixing.
With only 2 tools, the server is minimal but appropriately scoped for a simple notification utility. It does not feel under- or over-populated for its purpose.
The tool surface covers the core functionality (sending notifications and inspecting available sounds). Minor gaps like muting or configuration could exist, but for a focused utility it is reasonably complete.
Push notifications for AI agents - send instant iPhone notifications from any MCP client.
An MCP connector that lets your AI agents ask you questions, request permission approvals, and send alerts as push notifications to your phone and mac notch, so you can unblock and approve your agents from anywhere.
Give your AI agent a memory and body on your iPhone: set alarms, ring your phone, over MCP.
Push notifications with personalized sounds - manage and trigger your vybits via MCP
