Skip to main content
Glama
Telegram MCP

Telegram MCP

Related Servers

Alternatives to Telegram MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to search and retrieve from your local macOS iMessage history using hybrid retrieval with context expansion, all processed locally without sending data off-device.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables local, read-only access to the signed-in user's own Telegram account from macOS, including finding dialogs, reading date-range messages, searching within chats, listing folders, downloading attachments, and exporting selected messages without sending, deleting, joining, or marking messages read.
      7
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables reading Telegram chats and searching messages through natural language, connecting to MCP clients like Claude Code, Codex, and Cursor.
      17 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables searching Telegram messages and chats, retrieving recent messages, and extracting text from attached documents (PDF, TXT, MD, CSV) using your personal Telegram account.
      4
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables local, read-only keyword search across past Claude Code, Codex, Gemini CLI, and ChatGPT conversations plus markdown notes, with exact source citations and context retrieval.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants on macOS to browse, search, and read local iMessage conversations and group chats using real contact names, including unread messages and attachments, with explicit message sending when needed.
      MIT

    TDQS

    A3.9/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools target clearly distinct resources (single message, context window, thread, raw history, scheduled messages, drafts, media preview vs. file download). The main soft spots are the search trio (telegram_search_messages vs. telegram_search_chat_messages vs. telegram_search_public_posts) and the pin pair (telegram_get_pin_info vs. telegram_get_pin_status vs. telegram_get_group_upgrade_status), which rely on lengthy descriptions rather than an obvious name-level split. The descriptions do enough hand-holding (explicit 'use X for Y, not Z') to keep misselection unlikely.

    Naming Consistency5/5

    Every tool follows the same telegram_<verb>_<noun> snake_case convention: get_message, get_context, list_chats, list_voice_messages, search_messages, download_file, transcribe_voice. Verb usage is predictable (get/list/search/transcribe/download), with no camelCase or style mixing anywhere in the set.

    Tool Count4/5

    19 tools is on the heavy side for what is essentially a read/inspect surface, but nearly every entry maps to a genuinely different read path (per-chat vs. cross-chat vs. public search, thread vs. context, preview vs. full download). A couple of entries, notably telegram_get_pin_status and telegram_get_group_upgrade_status, exist only to poll async operation results that no tool in this set initiates.

    Completeness2/5

    The surface is almost entirely read-only: there is no send, reply, forward, edit, delete, mark-read, join, pin/unpin, or schedule-cancel tool, which are the core actions of the Telegram domain. The reconciliation tools (pin status, group upgrade status, draft read with 'before preparing a replacement') openly reference write paths that are absent, creating dead ends where an agent can read state but never act on it.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues