Skip to main content
Glama
demian-overflow

tgread

by demian-overflow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to tgread

No user-submitted related servers found.

    Related Servers

    • Telegram MCP

      iamalexzatcepin
      A
      license
      B
      quality
      B
      maintenance
      Provides read-only access to Telegram chats, allowing AI agents to list chats, read messages, and search within chats via local MCP.
      14
      MIT

    • teleloom

      starsinc1708
      A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server enables agents to connect to Telegram accounts and bots to search chats, review unread messages, build sourced digests, inspect media and documents, and prepare or execute confirmed actions with scoped permissions.
      1
      MIT

    • tgmcp

      OEvortex
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with Telegram accounts through MCP, supporting messaging, contacts, groups, media, and admin functions.
      4
      Apache 2.0

    • telegram-mcp

      Maxsh
      A
      license
      B
      quality
      D
      maintenance
      Enables users to read, search, and manage Telegram messages in channels, groups, and private chats through MCP tools.
      8
      MIT

    • telegram-bot

      Evr1kys
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to read allowlisted Telegram chats and send messages as a bot, with access control, local secrets, and duplicate send protection.
      1
      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

    A4/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct read operation or resource: chat metadata, message lists, specific message fetches, threads, media, members, reactions, contacts, folders, and shared chats. Even the message-related tools (read_chat, get_messages, read_thread) are clearly separated by scope and purpose.

    Naming Consistency4/5

    The vast majority of tools follow a clear verb_noun pattern (list_*, get_*, read_*, search_*), with three exceptions: chat_info, whoami, and common_chats. These deviations are minor and still readable, but they prevent a perfect consistency score.

    Tool Count5/5

    At 15 tools, the server sits at the upper edge of the well-scoped range, and every tool earns its place for a read-only Telegram interface. The count is substantial but not bloated, with each tool covering a distinct aspect of the domain.

    Completeness5/5

    The read surface is remarkably comprehensive: chat enumeration, message retrieval, search, threads, pinned messages, media, members, reactions, contacts, folders, public directory search, and account info are all present. The only excluded capability, media downloading, is explicitly documented as out of scope, so there are no hidden gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources