Related MCP server: io.github.daedalus/mcp-telegram-bot
依存関係をインストールする
pip3 install uv
uv venv
source .venv/bin/activate
uv sync.env ファイルを Telegram API ID とハッシュ ( My Telegram ) で編集します。他のユーザーと共有しないでください。
httpサーバーを起動する
uv run http-server/http-server.py
MCPサーバーをインストールする
uv run mcp install mcp-server/mcp-server.py
MCP サーバーは次の機能を提供します。
get_unread_entities : 未読メッセージがあるエンティティを取得する
get_unread_messages(id) : 指定されたエンティティIDからすべての未読メッセージを取得する
get_messages(id, count) : エンティティからカウントで制限されたメッセージを取得します
get_entities : 現在のセッション内のすべてのエンティティを取得する
get_entity_by_id(id) : 現在のセッションからエンティティを取得する
send_message(entity_id, content, reply_to_message_id) : オプションのマークアップと返信を付けてエンティティにメッセージを送信する
Claude は MCP サーバーを実行できません >> brew で uv をインストールします: brew install uv
Telegramで新しいアプリを作成できません >> VPNを切断して再試行してください
Get all entities in the current session
Inputs: no named parameters.
Get an entity from the current session
Inputs: id.
Get messages limited by a count from an entity
Inputs: id (required), count.
get entitites which have unread messages in it
Inputs: no named parameters.
get all unread messages from a given entity id
Inputs: id.
Send a message to an entity with optional markup and reply
Inputs: entity_id (required), content, reply_to_message_id.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 6 tools
Most tools have distinct purposes, but there is some overlap between get_entities and get_unread_entities, as both retrieve entities, which could cause confusion about which to use. However, the descriptions clarify that one gets all entities and the other gets only those with unread messages, mitigating ambiguity.
All tool names follow a consistent verb_noun pattern with snake_case, such as get_entities, send_message, and get_unread_messages. There are no deviations in naming conventions, making the set predictable and easy to understand.
With 6 tools, this server is well-scoped for managing Telegram sessions, covering key operations like retrieving entities, messages, and sending messages. The count is appropriate, avoiding bloat while providing essential functionality.
The toolset covers core messaging workflows, including reading and sending messages, but lacks operations for updating or deleting messages, which might be expected in a messaging domain. However, the provided tools handle the primary use cases effectively.
Telegram bridge for your MCP-compatible agent. Bidirectional, no LLM in our stack.
Unofficial Telegram MCP server — read, search, reply and react in your own Telegram account.
Hosted Telegram MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Unified messaging MCP server: WhatsApp, Instagram, Telegram, SMS, Messenger & email support inbox