overpod/mcp-telegram

Chat Resolution by Display Name (#7)

All tools that accept chatId now support display names in addition to numeric IDs and @usernames.

Problem

Previously, groups without usernames could only be found by numeric chat ID (e.g. -5038936120). Passing a display name like "AI team" resulted in:

Error: Cannot find any entity corresponding to "AI team"

Solution

Added resolveChat() — a smart fallback that searches the user's dialog list when direct resolution fails:

1. Direct resolve — numeric ID, @username, phone (instant, as before)
2. Exact match — searches dialogs for an exact title match (case-insensitive)
3. Partial match — if exactly one dialog contains the query, uses it
4. Multiple matches — returns a disambiguation list with IDs:

   Multiple chats match "team". Use the numeric ID instead:
     AI Team (1234567890)
     Dev Team (9876543210)
   

5. No match — suggests using telegram-search-chats to find the chat

Scope

All tools that accept chatId are covered: read-messages, send-message, search-messages, get-chat-info, get-chat-members, edit-group, pin-message, invite-to-group, kick-user, ban-user, set-admin, and all others.

Notes

• Dialog search fetches up to 100 recent dialogs
• For chats not in your recent dialogs, use telegram-search-chats first to get the numeric ID
• Numeric IDs and @usernames still work as before (no performance impact)

Full Changelog: https://github.com/overpod/mcp-telegram/compare/v1.16.0...v1.17.0