simple-notify-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FAL_KEY | No | FAL API key for TTS. Overrides config file key. | |
| FAL_API_KEY | No | Alternative environment variable for FAL API key. | |
| OPENAI_API_KEY | No | OpenAI API key for TTS. Overrides config file key. |
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 |
|---|---|
| simple_notify_statusA | Read runtime status: setup-web availability and running state, missing config, active provider, async mode, and Telegram cursor state. |
| tts_sayA | Speak a short message using configured provider; async by default and playback is queued (no overlap). Falls back to system TTS when needed. |
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
The two tools serve entirely different purposes: one provides runtime status information, the other performs speech output. There is no overlap or ambiguity in their functionality.
Both tools use underscored names, but one follows a noun-based pattern ('simple_notify_status') while the other uses a verb (‘tts_say’). The prefixes also differ, making the naming pattern inconsistent.
With only 2 tools, the server feels thin for a 'notification' domain. While the tools cover basic status display and text-to-speech, more tools (e.g., configuration, provider management) would be expected.
The tool set covers status checking and speech output, but lacks tools for configuring providers, managing queues, or handling errors. The domain is narrowly scoped, so the gaps are notable but not severe.