Skip to main content
Glama
slchenchn

notify-mcp

by slchenchn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

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)

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_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

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.5/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusion between tools. The purpose is clearly distinct by default.

Naming Consistency5/5

With a single tool, naming is trivially consistent. The name 'send_notification' follows a clear verb_noun pattern.

Tool Count3/5

One tool is borderline appropriate. The server's scope is limited to sending notifications, which could justify a single tool, but it feels thin compared to typical MCP servers that offer multiple operations.

Completeness2/5

The tool only sends notifications; there are no operations for managing recipients, viewing history, or configuring channels. While the core action is covered, significant gaps exist for a complete notification system.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources