Most notification servers only push, which is fine until the agent needs an answer — approve this, which option, is it done — and there is no path back. Reading new messages since the last check turns Telegram into a place a long-running agent can ask something and later see the reply. The fixed chat id is the design trade: simple to configure, and it means one instance talks to one destination, so multiple recipients means multiple instances.
A Telegram bot client with six tools: five send paths covering each media type, and one that polls for new messages to the bot.
- send_message, send_document, send_photo, send_video and send_audio each handle their own type rather than one generic send with a type parameter.
- get_updates returns only messages new since the last check, so polling does not re-read the same conversation.
TELEGRAM_BOT_TOKEN from BotFather and TELEGRAM_CHAT_ID for the destination — the chat is configured rather than chosen per call.
One command plus a key — npx telegram-notifier-mcp, then supply credentials