Skip to main content
Glama
expremiental

telegram-mcp

by expremiental

Related Servers

Alternatives to telegram-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server for personal Telegram accounts, exposing chat folders, chats, and recent messages via MTProto.
      -
    • A
      license
      A
      quality
      A
      maintenance
      Gives MCP clients controlled access to a Telegram user account, letting them search and read messages, inspect chats, and fetch media, with sending or editing messages available only after explicit opt-in. It runs self-hosted over FastMCP and Telethon with strict read-only defaults, OAuth or bearer authentication, and an outbound-only Cloudflare Tunnel.
      11
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Read-only MCP server for Telegram that enables reading messages and transcribing voice, audio, and video notes via the Telegram API for use with Codex and Claude Code.
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that connects to Telegram as your real user account and exposes read-only tools to read and search messages, list chats and folders, inspect group info, and download media.
      16 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A read-only server that lets any MCP client or model list, search, and read your own Telegram chats, including chat details, forum topics, message history, and surrounding context. It never sends, edits, or deletes anything, and stores your Telegram credentials encrypted at rest.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets any MCP client list, read, and search chats in the user's own Telegram account through a read-only server, without sending, editing, or deleting messages.
      52 npm
      1
      MIT

    TDQS

    A3.7/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a specific Telegram resource and action: account info, unread digest, media download, chat search, message history, chat list, participants, pinned messages, entity resolution, and in-chat search. Potential overlaps (e.g., find_chat vs resolve_chat) are differentiated by search vs exact match, and get_history vs search_in_chat by unfiltered retrieval vs text query.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (get_me, digest_unread, download_media, find_chat, get_history, list_chats, get_participants, get_pinned, resolve_chat, search_in_chat). The verbs are varied but appropriate to each action, and there are no style mixes or camelCase deviations.

    Tool Count5/5

    With 10 tools, the set is well-scoped for a Telegram read-only/digest MCP server. Each tool covers a distinct need without unnecessary redundancy, and the count is within the ideal 3-15 range.

    Completeness4/5

    The server covers the core read-only workflow: account info, listing chats, unread digests, history, search, media download, participants, pinned messages, and entity resolution. Minor gaps exist, such as no direct tool for getting a single message by ID or detailed user/chat profiles, but these are easily worked around with existing tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues