Skip to main content
Glama
elad12390

notification-mcp

by elad12390

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LOG_LEVELNoLog level: debug, info, warn, error, silentinfo
SAY_VOICENomacOS say voice nameSamantha
F5TTS_SPEEDNoF5-TTS speech speed multiplier1.0
KOKORO_SPEEDNoKokoro speech speed multiplier1.0
KOKORO_VOICENoDefault Kokoro voice (alias or full name)af_heart
F5TTS_REF_TEXTNoTranscript of the reference audio
F5TTS_REF_AUDIONoPath to reference audio file for voice cloning
MCP_METRICS_ENABLEDNoEnable/disable usage metricstrue
NOTIFICATION_METHODNoTTS engine: kokoro, f5tts, or saykokoro

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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:

  • Use punctuation naturally: "Hello!" sounds excited, "Hello..." sounds thoughtful

  • Use commas for pauses: "Well, I think so" has a natural pause

  • Use ellipsis for longer pauses: "Wait... what?"

  • Exclamation marks add energy: "Great job!" vs "Great job."

  • Question marks affect intonation: "Really?" sounds curious

  • Break long messages into sentences for natural rhythm

  • The model reads punctuation expressively, so write like you'd want it spoken!

Example good messages:

  • "Hey! Your task is complete. Everything went smoothly."

  • "Hmm... I found something interesting. Check this out!"

  • "Done! The build succeeded, and all tests passed."

CUSTOM PRONUNCIATION (IPA): For words that need specific pronunciation, use: [word](/IPA phonemes/) Common IPA symbols:

  • χ = Hebrew ח (chet), guttural "kh" sound

  • ʃ = "sh" sound

  • ð = "th" in "the"

  • θ = "th" in "think"

  • ŋ = "ng" sound

  • ɹ = American "r"

Examples:

  • "Chaim" - Hebrew name with guttural ח

  • "Elad" - Pronounce as "eh-lahd"

  • "Hello world!" - Custom pronunciation for "world"

TTS ENGINE OPTIONS (set via NOTIFICATION_METHOD env var):

  • "kokoro" (default): Fast (~3-5s), built-in voices, IPA pronunciation support

  • "f5tts": Higher quality (flow matching), slower (~10-15s), voice cloning capable

  • "say": macOS built-in, fastest but robotic

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 2 tools

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count3/5

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.

Completeness4/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues