This release adds 2 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
+4 more
Summary
AI summarysend-message now returns the message ID enabling edit workflows.
Full changelog
What's new
Rate Limiting & Automatic Retry
Built-in rate limiting and retry logic for Telegram API calls. No configuration needed — works automatically.
How it works:
- FLOOD_WAIT — waits the exact time Telegram requires, then retries (up to 3 attempts)
- Network errors (TIMEOUT, ECONNREFUSED, etc.) — exponential backoff: 1s → 2s → 4s
- Server errors (500/502/503) — same exponential backoff
- Auth errors — fail immediately (non-retryable)
- Rate limiting — 20 requests/second default, automatic throttling
Protected methods: sendMessage, sendFile, editMessage, deleteMessages
send-message returns messageId (closes #16)
telegram-send-message now returns the message ID in the response:
Message sent to @username [#12345]
This enables send → edit workflows — previously impossible because edit-message requires messageId which wasn't returned.
Tests
7 new unit tests for the rate limiter covering: basic execution, rate limiting enforcement, FLOOD_WAIT retry, network error backoff, non-retryable error handling, and FLOOD_WAIT seconds parsing.
Total: 24 tests (17 shared + 7 rate limiter), all passing.
Full Changelog: https://github.com/overpod/mcp-telegram/compare/v1.19.0...v1.20.0
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About overpod/mcp-telegram
Telegram MCP server via MTProto/GramJS — 20 tools for reading chats, searching messages, downloading media, managing contacts. QR code login, npx zero-install. Hosted version at mcp-telegram.com.
Related context
Beta — feedback welcome: [email protected]