@overpod/mcp-telegram 1.39.0 → 1.39.1

package/CHANGELOG.md

@@ -5,6 +5,13 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.39.1](https://github.com/mcp-telegram/mcp-telegram/compare/v1.39.0...v1.39.1) (2026-06-21)
+
+
+### Fixed
+
+* **resolve:** recover bare numeric peer IDs that lack access_hash ([#62](https://github.com/mcp-telegram/mcp-telegram/issues/62)) ([678077a](https://github.com/mcp-telegram/mcp-telegram/commit/678077a78ce3a5852e07d5d831f664c3e08a81e3))
+
 ## [1.39.0](https://github.com/mcp-telegram/mcp-telegram/compare/v1.38.2...v1.39.0) (2026-06-21)
 
 

package/dist/telegram-client.d.ts

@@ -276,6 +276,13 @@ export declare class TelegramService {
      * Handles display names by searching dialogs.
      */
     private resolvePeer;
+    /**
+     * Resolve a bare numeric ID to a cached/dialog entity so GramJS can build a
+     * valid InputPeer. Falls back to the raw ID string if no dialog matches —
+     * GramJS may still resolve it (e.g. a contact or a peer it has messaged),
+     * and we must not regress that path.
+     */
+    private resolveNumericPeer;
     getChatInfo(chatId: string): Promise<{
         id: string;
         name: string;

package/dist/telegram-client.js

@@ -1191,12 +1191,78 @@ export class TelegramService {
         // Normalize '@me' — GramJS only intercepts the plain 'me' string as InputPeerSelf
         if (chatId === "@me")
             return "me";
-        // Numeric IDs and @usernames work directly
-        if (/^-?\d+$/.test(chatId) || chatId.startsWith("@"))
+        // @usernames resolve directly via contacts.ResolveUsername
+        if (chatId.startsWith("@"))
             return chatId;
-        // Everything else — resolve via dialogs
+        // Bare numeric IDs need an entity with access_hash. GramJS can build an
+        // InputPeer from a raw number only if it's already cached or the account
+        // is a contact / has messaged us — otherwise getInputEntity throws
+        // "Could not find the input entity". A bare positive number is also
+        // ambiguous (GramJS assumes PeerUser, so channel IDs fail outright).
+        // Recover by looking the ID up among dialogs, which yields a full entity
+        // (with access_hash) for both users and channels.
+        if (/^-?\d+$/.test(chatId))
+            return this.resolveNumericPeer(chatId);
+        // Everything else — resolve display name via dialogs
         return this.resolveChat(chatId);
     }
+    /**
+     * Resolve a bare numeric ID to a cached/dialog entity so GramJS can build a
+     * valid InputPeer. Falls back to the raw ID string if no dialog matches —
+     * GramJS may still resolve it (e.g. a contact or a peer it has messaged),
+     * and we must not regress that path.
+     */
+    async resolveNumericPeer(chatId) {
+        if (!this.client)
+            throw new Error(NOT_CONNECTED_ERROR);
+        const cached = this.entityCache.get(chatId);
+        if (cached)
+            return cached;
+        // Direct resolve first — succeeds when GramJS already knows the peer.
+        try {
+            const entity = await this.client.getEntity(chatId);
+            this.entityCache.set(chatId, entity);
+            return entity;
+        }
+        catch {
+            // Fall through to dialog scan.
+        }
+        // Scan dialogs for a matching entity. IDs reach us in two shapes:
+        //   • bare positive  (e.g. 1004294063929 for a channel, 8959122940 for a
+        //     user) — this is what list-chats/search emit and what GramJS can't
+        //     disambiguate; match it against any entity's bare id.
+        //   • marked         (-100<id> for channels, -<id> for basic groups) — the
+        //     sign/-100 prefix carries the type, so require the entity to match that
+        //     exact marked form, otherwise a group "-123" could wrongly match a user
+        //     with bare id 123.
+        const isMarked = chatId.startsWith("-");
+        try {
+            const dialogs = await this.client.getDialogs({ limit: 100 });
+            const match = dialogs.find((d) => {
+                const entity = d.entity;
+                if (!entity?.id)
+                    return false;
+                const bare = entity.id.toString();
+                if (!isMarked)
+                    return chatId === bare;
+                // Marked input must match the entity's marked form.
+                if (entity instanceof Api.Channel)
+                    return chatId === `-100${bare}`;
+                if (entity instanceof Api.Chat)
+                    return chatId === `-${bare}`;
+                return false;
+            });
+            if (match?.entity) {
+                this.entityCache.set(chatId, match.entity);
+                return match.entity;
+            }
+        }
+        catch {
+            // Dialog fetch failed — fall back to the raw ID below.
+        }
+        // Last resort: hand the raw ID to GramJS and let it try GetUsers/GetChannels.
+        return chatId;
+    }
     async getChatInfo(chatId) {
         if (!this.client || !this.connected)
             throw new Error(NOT_CONNECTED_ERROR);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@overpod/mcp-telegram",
-  "version": "1.39.0",
+  "version": "1.39.1",
   "description": "MCP server for Telegram userbot — messages, media, reactions, polls & more. Built on GramJS/MTProto.",
   "type": "module",
   "main": "dist/index.js",
@@ -72,7 +72,7 @@
   },
   "devDependencies": {
     "@biomejs/biome": "^2.5.0",
-    "@types/node": "^25.9.3",
+    "@types/node": "^26.0.0",
     "@types/qrcode": "^1.5.6",
     "c8": "^11.0.0",
     "tsx": "^4.22.4",