notification-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level: debug, info, warn, error, silent | info |
| SAY_VOICE | No | macOS say voice name | Samantha |
| F5TTS_SPEED | No | F5-TTS speech speed multiplier | 1.0 |
| KOKORO_SPEED | No | Kokoro speech speed multiplier | 1.0 |
| KOKORO_VOICE | No | Default Kokoro voice (alias or full name) | af_heart |
| F5TTS_REF_TEXT | No | Transcript of the reference audio | |
| F5TTS_REF_AUDIO | No | Path to reference audio file for voice cloning | |
| MCP_METRICS_ENABLED | No | Enable/disable usage metrics | true |
| NOTIFICATION_METHOD | No | TTS engine: kokoro, f5tts, or say | kokoro |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| report_issueA | Report a bug, feature request, or other issue with the MCP server. Issues are saved locally for the server maintainer to review. |
| notifyA | Sends a notification to the user. Use this when you complete a task and want to alert the user. IMPORTANT - Writing expressive messages:
Example good messages:
CUSTOM PRONUNCIATION (IPA): For words that need specific pronunciation, use: [word](/IPA phonemes/) Common IPA symbols:
Examples:
TTS ENGINE OPTIONS (set via NOTIFICATION_METHOD env var):
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
report_issue and notify serve clearly different purposes: one reports bugs/features about the MCP server, the other sends user-facing notifications. An agent can easily choose the correct tool based on task context.
Both names use lowercase snake_case and start with a verb, but report_issue follows a verb_noun pattern while notify is a lone verb. This is a minor inconsistency, not confusing.
With only two tools, the set is thin for a dedicated server, though both tools are distinct and useful. It falls into the borderline 1-2 tool range noted in the rubric.
The server covers the core notification action and provides a feedback path via report_issue. Minor gaps exist around notification management or delivery status, but these are not essential for basic use.