fast-mcp-telegram and telegram-mcp
These are complementary tools—the first provides a bridge/server infrastructure for Telegram integration while the second offers higher-level dialog and message management capabilities that could run on top of that infrastructure.
About fast-mcp-telegram
leshchenko1979/fast-mcp-telegram
Telegram MCP Server and HTTP-MTProto bridge | Multi-user auth, intelligent search, file sending, web setup | Docker & PyPI ready
Implements a dual-transport MCP server exposing Telegram's MTProto API with automatic entity resolution and safety guardrails, enabling both stdio-based development and HTTP-authenticated production deployments. The architecture consolidates functionality into fewer, context-efficient tools (e.g., unified `get_messages` for search/browse/read-by-ID/replies) following an LLM-optimized design philosophy, while the HTTP-MTProto bridge provides raw API access via curl for edge cases. Built on async Telethon with session persistence, LRU cache management, and structured logging for reliability.
About telegram-mcp
chaindead/telegram-mcp
Telegram MCP for managing dialogs, messages, drafts, read statuses, and more.
Implements the Model Context Protocol to expose Telegram's TDLib client library through a standardized MCP server interface, enabling AI assistants like Claude Desktop and Cursor to autonomously manage conversations. Built in Go with support for multi-factor authentication and persistent session management via environment variables. Exposes five core tools—account info, dialog listing, message retrieval, read status updates, and draft sending—allowing AI agents to perform end-to-end message workflows programmatically.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work