Telebrief
Related Servers
Alternatives to Telebrief
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA local MCP server for Cursor and Claude Desktop that reads Telegram subscriptions over MTProto and exposes channel posts for digests and natural-language queries.13 npm1MIT
- AlicenseNot gradedqualityBmaintenanceRead-only MCP server for Telegram chats and channels that provides digest summaries, message search, and action items.13 npmMIT
- FlicenseNot gradedqualityDmaintenanceModel Context Protocol server for Telegram. Let AI read, search, send, and forward your Telegram messages.15 npm-
- AlicenseNot gradedqualityDmaintenanceA read-only Telegram MCP server that retrieves messages from your DMs, groups, and channels, enabling Claude to generate executive briefings from Telegram conversations.MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that reads Telegram groups and channels via MTProto to produce source-linked summaries with participant contributions, decisions, and risks over specified time ranges.107 npmMIT
- FlicenseAqualityAmaintenanceBridges AI assistants to a Telegram bot to enable two-way messaging, interactive confirmations, and live status updates. It supports automatic voice transcription via local Whisper models and provides secure, single-user communication for MCP-compatible hosts.46-
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose, and the descriptions explicitly differentiate them: get_digest generates fresh summaries, get_last_digest returns cached output, search_messages searches across channels, and get_channel_messages returns raw per-channel messages. No overlap or ambiguity.
All tool names use a consistent snake_case verb_noun pattern (get_digest, search_messages, get_channel_messages, get_last_digest). The verbs are predictable and the names directly reflect their actions.
Four tools is a well-scoped set for a Telegram digest server. Each tool covers a distinct operation (fresh digest, cached digest, search, raw messages) and none feels redundant or missing for the core purpose.
The surface covers the main lifecycle: generating a digest, retrieving the latest digest, searching messages, and reading channel messages. A minor gap is the lack of a tool to list configured channels, which would help agents discover valid channel names without reading config.yaml.