Skip to main content
Glama
belaytzev

Telebrief

by belaytzev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Telebrief

No user-submitted related servers found.

    Related Servers

    • tg-mcp-tools

      ausievich
      A
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server for Cursor and Claude Desktop that reads Telegram subscriptions over MTProto and exposes channel posts for digests and natural-language queries.
      15 npm
      1
      MIT

    • tg-mcp

      s4relok
      A
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server for Telegram chats and channels that provides digest summaries, message search, and action items.
      15 npm
      MIT

    • telegram-briefing-mcp

      zainbacchus
      A
      license
      Not graded
      quality
      D
      maintenance
      A read-only Telegram MCP server that retrieves messages from your DMs, groups, and channels, enabling Claude to generate executive briefings from Telegram conversations.
      MIT

    • telegram-mcp

      t0uchY233
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that reads Telegram groups and channels via MTProto to produce source-linked summaries with participant contributions, decisions, and risks over specified time ranges.
      110 npm
      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.4/5.0

    Scored across 3 tools

    Disambiguation4/5

    get_digest and get_last_digest are the closest pair, but the descriptions clearly frame one as cached/free/possibly-stale and the other as fresh/slow/costly, which makes the tradeoff easy to reason about. get_channel_messages is clearly distinct as raw per-channel data versus the summarized whole-digest view.

    Naming Consistency5/5

    All three tools use a consistent snake_case verb_noun pattern (get_last_digest, get_digest, get_channel_messages), with the get_ prefix and the digest/channel noun matching the returned resource. No mixed conventions or vague verbs.

    Tool Count4/5

    Three tools is lean but defensible for a focused read-only digest service: cached read, fresh generation, and drill-down into source messages. It errs slightly thin, as there is no discovery or configuration surface, but nothing feels redundant.

    Completeness3/5

    The core lifecycle (view last digest, generate new digest, inspect raw messages) is covered, but get_channel_messages requires a channel name 'as configured' with no tool to list configured channels, creating a discoverability dead end. No way to check freshness windows or configuration also limits self-service.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources