Skip to main content
Glama
slchenchn

notify-mcp

by slchenchn

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NOTIFY_TOKEN_FILENofile holding the bearer token./.token next to the script
NOTIFY_GATEWAY_URLNogateway endpoint — set this to your gateway's host:porthttp://localhost:27319/notify
NOTIFY_GATEWAY_TOKENNobearer token (overrides the file)

Capabilities

Features and capabilities supported by this server

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

Tools

Functions exposed to the LLM to take actions

NameDescription
send_notificationA

Push a short notification to the user's phone (Telegram) via the local gateway.

Use this to proactively reach the user when they may be away from the terminal:
a long-running task finished, a build/training run succeeded or failed, or you
have hit something that needs their decision before you can continue. Do NOT use
it for routine progress chatter or to echo an answer they are clearly watching.

Args:
    message: The notification body. Keep it one line and lead with what they'd
        act on (e.g. "train run failed: OOM at step 1200").
    title: Optional short bold title (e.g. the node or job name).
    tag: Which configured recipient group to send to (default "default").

Returns "ok" on success, or an error string describing why it failed.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/slchenchn/notify-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server