Skip to main content
Glama
zurdi15

telegram-notify-mcp

by zurdi15
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TELEGRAM_CHAT_IDNoChat ID to send notifications to. If not set, the server will look for it in the file specified by TELEGRAM_NOTIFY_ENV, ~/.config/telegram-notify/notify.env, or ~/.config/claude-telegram/notify.env.
TELEGRAM_BOT_TOKENNoBot token from @BotFather. If not set, the server will look for it in the file specified by TELEGRAM_NOTIFY_ENV, ~/.config/telegram-notify/notify.env, or ~/.config/claude-telegram/notify.env.
TELEGRAM_NOTIFY_ENVNoPath to a .env file containing TELEGRAM_BOT_TOKEN and TELEGRAM_CHAT_ID. Used when the direct environment variables are not set.

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
notifyA

Envía un aviso por Telegram al usuario (una tarea terminada o bloqueada).

title: titular corto proyecto versión verbo (p. ej. "turtletrips 1.7.0 desplegado"), sin icono: lo pone status. body: qué se hizo (con imagen/tag/commit), cómo se verificó y, en releases, "Novedades X.Y.Z:" con una línea "- " por cambio. Texto plano en español, sin Markdown ni secretos. status: ok ✅ | fail ❌ | warn ⚠️ | info ℹ️ | ask ❓. project: nombre del proyecto para la línea de contexto (por defecto, el repo git del cwd). host: host de la línea de contexto (por defecto esta máquina; pasa el destino del despliegue si es lo relevante). dry_run: devuelve el mensaje compuesto sin enviarlo.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A4.2/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusion between tools. The single tool clearly defines its purpose of sending a Telegram notification.

Naming Consistency5/5

With only one tool, naming is trivially consistent. The verb 'notify' clearly indicates the action, fitting the expected verb_noun pattern.

Tool Count1/5

A single tool for a server is extremely thin, even if the purpose is narrow. This feels more like a helper function than a full MCP server; agents would expect additional tools for managing notifications or checking status.

Completeness2/5

The tool covers sending notifications, but there is no way to list, get, or delete sent notifications, nor any configuration management. The domain is so minimal that completeness is hard to assess, but it leaves obvious gaps for any non-trivial use.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources