This release adds 2 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
+4 more
Affected surfaces
Summary
AI summaryNew telegram-get-my-role command and enhanced telegram-get-chat-members now display user roles.
Full changelog
User Roles in Chat Members (#8)
Enhanced: telegram-get-chat-members
Now shows user roles alongside names. Uses raw channels.GetParticipants API for supergroups/channels.
Output example:
Alex (@overpod) (123456) [creator]
Bot Manager (@mgr) (789012) [admin]
John Doe (345678)
Spammer (901234) [banned]
Roles shown: [creator], [admin], [banned], [left]. Regular members have no tag.
Note: Basic groups (non-supergroups) don't expose role info via Telegram API — all members show as regular.
New: telegram-get-my-role
Check the current user's role in any chat. Useful for AI agents that need permission-aware behavior.
Parameters:
chatId— chat ID, @username, or display name
Output:
Role: admin
Chat: AI Team (-1001234567890)
Returns: creator, admin, member for groups/channels; user for private chats.
Use Case
AI agents (e.g. Mastra-based) that poll Telegram for unread messages can now filter by role — only respond in chats where the agent account is admin or creator, without hardcoding chat ID whitelists.
Full Changelog: https://github.com/overpod/mcp-telegram/compare/v1.17.0...v1.18.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]