Telegram MCP Server
텔레그램-mcp
요구 사항
Related MCP server: io.github.daedalus/mcp-telegram-bot
용법
종속성 설치
지엑스피1
텔레그램 API ID와 해시( 내 텔레그램 )로 .env 파일을 편집하고, 다른 사람과 공유하지 마세요.
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 uvTelegram에서 새 앱을 만들 수 없습니다 >> VPN 연결을 끊고 다시 시도하세요
특허
Available Tools
6 toolsget_entitiesB
Get all entities in the current session
Inputs: no named parameters.
get_entity_by_idC
Get an entity from the current session
Inputs: id.
get_messagesC
Get messages limited by a count from an entity
Inputs: id (required), count.
get_unread_entitiesC
get entitites which have unread messages in it
Inputs: no named parameters.
get_unread_messagesC
get all unread messages from a given entity id
Inputs: id.
send_messageC
Send a message to an entity with optional markup and reply
Inputs: entity_id (required), content, reply_to_message_id.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
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.
Maintenance
Related MCP Connectors
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
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables interaction with Telegram to send, read, and search messages across chats and dialogs. It supports waiting for incoming messages and retrieving conversation history through natural language commands.31 npm3MIT
- AlicenseAqualityDmaintenanceMCP server that exposes a Telegram bot, enabling sending messages and retrieving updates through natural language.342 PyPI1MIT
- FlicenseAqualityDmaintenanceAn MCP server for interacting with Telegram bots and channels using the Telegraf library. It allows AI agents to send messages, manage channels, forward content, and intelligently respond to Telegram conversations.552 npm8-
- AlicenseNot gradedqualityDmaintenanceAn MCP server for sending and receiving Telegram messages via a bot, enabling AI assistants to interact directly through Telegram by sending messages, reading recent messages, and sending photos.620 npmMIT