overpod/mcp-telegram

v1.35.0 Breaking

This release includes breaking changes for platform teams planning a safe upgrade.

Published 1mo MCP SaaS Integrations

View tool

✓ No known CVEs patched

Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

ai-tools claude gramjs mcp mcp-server model-context-protocol

+4 more

mtproto telegram typescript userbot

Summary

AI summary

RateLimiter now emits structured stderr JSON lines for flood_wait, network_retry, and temporary_retry events.

Full changelog

What's changed

The internal RateLimiter previously logged FLOOD_WAIT and network retries as
human-readable strings via console.error, and the temporary-server-error
branch (5xx, etc.) was silent. All three retry branches now emit a single
structured stderr line per event:

[rate-limiter] event {"event":"flood_wait","context":"list-chats","seconds":30,"attempt":1,"maxRetries":3}

Event types

flood_wait — Telegram FLOOD_WAIT_X triggered, sleeping seconds before retry.
network_retry — connection error (timeout, ECONNREFUSED, etc.), sleeping delayMs before retry.
temporary_retry — transient 5xx / INTERNAL error, sleeping delayMs before retry. Previously silent.

Each event carries:

| Field | Type | Notes |
|---|---|---|
| event | string | Event class (literal, see above) |
| context | string | Caller-supplied operation name (e.g. tool name). Never user input / PII. |
| attempt / maxRetries | number | Current attempt counter |
| seconds | number | Wait duration. flood_wait only. |
| delayMs | number | Backoff delay. network_retry / temporary_retry only. |
| error | string | Original Telegram error message. network_retry / temporary_retry only. |

Why this matters

Downstream log collectors can now aggregate retry rates by event class and
caller without parsing free-form English. mcp-telegram-cloud v1.12.0+ wires
this into SigNoz directly. Self-hosters can grep '\[rate-limiter\] event'
or pipe into any structured log pipeline.

Compatibility

No breaking changes — retry timing, backoff, and error-throwing semantics are identical to 1.34.0.
No new dependencies.
No new environment variables.
Tests: 490/490 pass.

Install

npm install @overpod/[email protected]
# or via npx
npx @overpod/mcp-telegram

Diff

Code: 66c59d8 — feat(rate-limiter): emit structured JSON-line events for retries
Release: e30ad43 — release: v1.35.0

Full Changelog: https://github.com/mcp-telegram/mcp-telegram/compare/v1.34.0...v1.35.0

View diff on GitHub

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

Share on X Share on Bluesky

Track overpod/mcp-telegram

Get notified when new releases ship.

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.

All releases →