Skip to main content
Glama
thanhdien938

Unofficial Telegram Sales MCP

by thanhdien938
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Unofficial Telegram Sales MCP

No user-submitted related servers found.

    Related Servers

    • Telegram Agent for Codex

      Frejixxx
      A
      license
      Not graded
      quality
      D
      maintenance
      Privacy-first Telegram MCP server enabling maintainers to triage chats, inspect context, search messages, draft replies, and send authorized messages locally without a cloud relay.
      26 npm
      1
      MIT

    • codex-telegram

      briejhxh
      A
      license
      A
      quality
      C
      maintenance
      Enables local, privacy-first control of a personal Telegram account through MCP, using TDLib to read chats, send and reply to messages, search, transfer files, and interact with approved inline buttons.
      20
      MIT

    • Unofficial Telegram MCP

      NickShtefan
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to read and search Telegram chats, fetch media, export messages, inspect channel analytics, build a local index, and prepare confirmed replies, sends, reactions, joins, and callback button presses across multiple accounts through one daemon.
      MIT

    • After-hours Telegram MCP

      deploy103
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables a single owner to run an authenticated Streamable HTTP MCP endpoint backed by their own BotFather token, with tools to check bot status, poll allowlisted updates, inspect and acknowledge pending messages, and optionally send replies when explicitly enabled. It supports safe disconnected startup and avoids private-account sessions, multi-user services, schedulers, or automatic retries.
      MIT

    • Telegram MCP Server

      alexeyleshchenko
      A
      license
      A
      quality
      A
      maintenance
      MCP server that acts as a gateway to Telegram, providing AI-optimized tools for messaging, search, and chat management via MTProto. Supports multi-user authentication with QR login and HTTP/stdio transports.
      8
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools target clearly distinct resources or actions, such as messages_get vs. messages_search vs. public_search vs. file_get. There is some overlap between telegram_chats_list and telegram_inbox, and between telegram_health, telegram_capabilities, and telegram_account, but the descriptions give enough separation to avoid serious misselection.

    Naming Consistency3/5

    All tools share the telegram_ prefix, but the suffix conventions are mixed: some are noun-only (telegram_health, telegram_account, telegram_inbox), while others use resource_action (telegram_chats_list, telegram_chat_get, telegram_messages_search). There is also singular/plural inconsistency between telegram_chats_list and telegram_chat_get. The names remain readable, but the pattern is not fully predictable.

    Tool Count5/5

    Eleven tools is a reasonable size for a Telegram-focused server and stays within the well-scoped 3-15 range. Each tool appears to earn its place by covering a specific read/search/health capability.

    Completeness2/5

    The surface is entirely read-only and lacks core Telegram sales operations such as sending messages, managing chats or contacts, uploading files, or performing account reauthentication actions. While the read/search/health coverage is fairly broad, the absence of write or lifecycle operations is a significant gap for a sales-oriented Telegram MCP.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources