Skip to main content
Glama
ch1y1z1

notification-mcp

by ch1y1z1

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BARK_SERVERNo自建Bark服务器URL,默认为https://api.day.app
PUSHDEER_KEYSNo逗号分隔的PushDeer密钥列表(必需)
PUSHDEER_SERVERNo自建PushDeer服务器URL,默认为https://api2.pushdeer.com
BARK_DEVICE_KEYSNo逗号分隔的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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
send_messageB
向所有配置的 Bark 设备发送消息

Args:
    title: 消息标题
    content: 消息内容

Returns:
    str: 发送结果

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no risk of ambiguity between tools. The single tool has a clear purpose.

Naming Consistency5/5

Only one tool exists, so naming consistency is trivially maintained. The tool name 'send_message' is clear and follows common conventions.

Tool Count2/5

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.

Completeness2/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues