Skip to main content
Glama
Telegram MCP Server

Telegram MCP Server

电报-mcp

要求

Related MCP server: io.github.daedalus/mcp-telegram-bot

用法

  1. 安装依赖项

pip3 install uv
uv venv
source .venv/bin/activate
uv sync
  1. 使用您的电报 api id 和哈希(我的电报)编辑 .env 文件,不要与他人分享。

  2. 启动 http 服务器

uv run http-server/http-server.py

  1. 安装 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 并重试

执照

麻省理工学院

Available Tools

6 tools
get_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

    B3.1/5.0

    Scored across 6 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An 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 npm
      3
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server that exposes a Telegram bot, enabling sending messages and retrieving updates through natural language.
      3
      42 PyPI
      1
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      An 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.
      5
      52 npm
      8
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An 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 npm
      MIT