notification-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BARK_SERVER | No | 自建Bark服务器URL,默认为https://api.day.app | |
| PUSHDEER_KEYS | No | 逗号分隔的PushDeer密钥列表(必需) | |
| PUSHDEER_SERVER | No | 自建PushDeer服务器URL,默认为https://api2.pushdeer.com | |
| BARK_DEVICE_KEYS | No | 逗号分隔的Bark设备密钥列表(必需) |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_messageB | |
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
With only one tool, there is no risk of ambiguity between tools. The single tool has a clear purpose.
Only one tool exists, so naming consistency is trivially maintained. The tool name 'send_message' is clear and follows common conventions.
A single tool for a notification server is too few. Even for a minimal server, one would expect at least a few tools for device management or status checks.
The tool surface is very incomplete. There is no way to configure devices, retrieve sending status, or handle errors. The server only supports sending messages without any supporting operations.