This release adds 3 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
+4 more
Affected surfaces
Summary
AI summaryAdded logOut() to fully terminate Telegram sessions and enhanced several API methods.
Full changelog
What's New
logOut() — Complete Telegram Session Termination
New method TelegramService.logOut() that calls Api.auth.LogOut() to fully terminate the session on Telegram servers.
What it does:
- Terminates the MTProto session on Telegram's side
- Session disappears from the user's "Active Sessions" in Telegram settings
- Session string becomes invalid after logout
- Graceful fallback: if remote logout fails, disconnects locally
Use case: Cloud/hosted MCP services that need to clean up Telegram sessions when a user disconnects their connector (e.g. via OAuth token revocation).
const telegram = new TelegramService(apiId, apiHash);
await telegram.connect();
// ... use the service ...
// Full logout (removes from Telegram "Active Sessions")
const success = await telegram.logOut();
// vs. soft disconnect (session remains valid for reconnect)
await telegram.disconnect();
Other improvements
getChatInfonow returnsmembersCountanddescriptionusingGetFullChannel/GetFullChatAPI callsdownloadMediaAsBuffer— new method for serverless media download (returns Buffer instead of writing to disk)- MIME type detection — uses magic bytes (JPEG/PNG/GIF/WebP) instead of unreliable Telegram metadata
Full Changelog: https://github.com/overpod/mcp-telegram/compare/v1.2.0...v1.3.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]