broadcast_notification
Broadcast notification to all available messaging platforms
LABSCO SUMMARY
A notifier that also carries the answer back, so you can leave the desk mid-task.
The outbound half is ordinary — titled messages with a priority, to Telegram or a webhook. The inbound half is what makes it worth wiring up: request_interaction_sync posts a confirmation, prompt or button menu and holds the agent until you answer or the timeout expires, and there is a queue underneath so several questions can be outstanding at once.
What it is
A notification and interaction server for Telegram and HTTP webhooks. It pushes status messages out of a running agent, and it can post a question and block until you reply.
What you get
- Notifications with a title, body, priority and arbitrary metadata, sent to one service or broadcast to every configured channel at once
- Interaction requests in three shapes — confirmation, free-text prompt, and a selection menu with buttons
- Both a synchronous request that waits for your reply with a timeout, and an asynchronous one that returns immediately and is answered later
- A pending-request queue you can list, respond to, or cancel by request ID
- Telegram-side prompts you started from the chat: fetch them, process one by ID, read the statistics, and clean up the processed ones
- Service health — list what is configured, test every connection, and check one service on its own
Requirements
A Telegram bot of your own. Create it through @BotFather to get TELEGRAM_BOT_TOKEN, then message the bot and read TELEGRAM_CHAT_ID from https://api.telegram.org/bot<TOKEN>/getUpdates. Both are required. Run it with npx -y notify-me-maybe-mcp from the npm package notify-me-maybe-mcp over stdio. Optional settings: TELEGRAM_PROMPT_ENABLED, TELEGRAM_INTERACTION_ENABLED, DEFAULT_NOTIFICATION_SERVICE and LANGUAGE.
Setup effort
One command plus a key — npx -y notify-me-maybe-mcp, then supply credentials
USE CASES
01
Being told the overnight run finished, and how it went
Push a titled message with the results and a priority that matches the outcome.
02
Approving a destructive step from your phone
The agent posts a confirmation to Telegram and waits — nothing is deleted until you tap yes.
03
Choosing between deployment strategies mid-run
Send the options as a button menu, and the choice comes back into the same task.
04
Kicking off work by messaging the bot rather than opening the editor
Pull the prompts waiting in Telegram, act on one by ID, and clear the processed ones when done.
05
Checking the alert path still works before you rely on it
List the configured services and test every connection in one call.
15 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
cancel_interaction
Cancel a specific interaction request
cleanup_telegram_prompts
Clean up processed Telegram prompts
get_interaction_status
Get interaction feature status and statistics
get_service_status
Get status of specified service
get_telegram_prompt_stats
Get Telegram prompt statistics
get_telegram_prompts
Get all prompt requests from Telegram
list_pending_interactions
List all pending interaction requests
list_services
List all available notification services
process_telegram_prompt
Process the specified Telegram prompt
request_interaction
Request user interaction (e.g., new prompt input or confirmation) (Asynchronous - returns immediately)
request_interaction_sync
Synchronously request user interaction and wait for response (Synchronous - waits for user response)
respond_to_interaction
Respond to a pending interaction request
send_notification
Send notification to specified messaging platform
test_services
Test connection status of all notification services
BEFORE YOU INSTALL
What to know first
Tools you get
15 tools when we connected. The documentation names only six; the nine undocumented tools, such as request_interaction and list_pending_interactions, cover asynchronous interactions and service status.
Requires
- npx on PATH
- TELEGRAM_BOT_TOKEN in your environment
- TELEGRAM_CHAT_ID in your environment
Where it runs
Both documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 15 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y notify-me-maybe-mcpMCP Clients
Claude Desktop, Cursor
JSON
{
"mcpServers": {
"notify-me-maybe": {
"command": "npx",
"args": [
"-y",
"notify-me-maybe-mcp"
],
"env": {
"TELEGRAM_BOT_TOKEN": "<YOUR_TELEGRAM_BOT_TOKEN>",
"TELEGRAM_CHAT_ID": "<YOUR_TELEGRAM_CHAT_ID>",
"TELEGRAM_PROMPT_ENABLED": "true",
"TELEGRAM_INTERACTION_ENABLED": "true",
"DEFAULT_NOTIFICATION_SERVICE": "telegram",
"LANGUAGE": "en"
}
}
}
}
