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.
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.
- 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
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.
One command plus a key — npx -y notify-me-maybe-mcp, then supply credentials