notify-human-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTIFY_HUMAN_WEBHOOK_URL | Yes | Your Discord webhook URL. Each machine/user gets its own. | |
| NOTIFY_HUMAN_INSTRUCTIONS_URL | No | Hosted instructions URL (secondary; fetched at startup). | |
| NOTIFY_HUMAN_INSTRUCTIONS_FILE | No | Local instructions file (primary source). |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sendA | Send one notification to the human's Discord whenever their attention is needed: you are blocked, need a decision or missing info, have a question or warning about the current task, something important happened mid-task, you finished, or the user asked to be pinged. One message per event — do not spam the user. Keep it under 1000 characters: status line first, short bullets, the ask last. Messages over 2000 characters (plain) or 4096 (embed) are rejected, not truncated — shorten before sending. Set embed=True for a rich card instead of plain markdown. |
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 1 tool
There is only one tool, so there is no possibility of confusion or misselection between tools. Its purpose (send a notification to the human) is stated unambiguously.
A single tool named 'send' is a clear, conventional verb. With only one tool there is no inconsistent pattern to violate.
For a narrowly scoped server whose sole job is pinging a human, one tool is the right shape rather than a thin surface. It is minimal but not under-built for the stated purpose.
The send tool fully covers the core lifecycle of a fire-and-forget notification (status, ask, formatting, length limits), and no create/update/delete cycle is needed. Minor gaps exist, such as no channel configuration or acknowledgement/read-status retrieval.