Telegram Context MCP

Name: Telegram Context MCP
Author: egor-fedorov

作者：egor-fedorov版本 0.8.0i★ –i在你的电脑上运行

注册名称io.github.egor-fedorov/telegram-mcp

安装

概览

作者提供的说明（英文原文）

Read permitted Telegram chats, track changes and optionally confirm outbound actions locally.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i非常新↓ 284/周 · ★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 聊天与邮件

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "telegram": {
      "command": "uvx",
      "args": [
        "telegram-context-mcp",
        "serve"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add telegram -- uvx telegram-context-mcp serve

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "telegram": {
      "command": "uvx",
      "args": [
        "telegram-context-mcp",
        "serve"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "telegram": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "telegram-context-mcp",
        "serve"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 egor-fedorov 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“聊天与邮件”中的其他服务器比较i

星标数多于此分类中其他 1849 个服务器的 0%
发布到注册中心的时间比此分类中其他 1849 个服务器的 90% 更新
基础检查结果等于或优于此分类中其他 1849 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Telegram Context MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.8.0）于前天进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Vexa, emailmd, MCP WhatsApp Cloud

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Vexa

Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.

作者：Vexa-ai广泛使用★ 29492个月前更新

在云端运行✓ vexa.ai

安装

emailmd

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

作者：anypost正在增长↓ 5342/周★ 138532天前更新

电脑或云端✓ emailmd.dev

安装

MCP WhatsApp Cloud

MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API

作者：codespar起步阶段↓ 63/周★ 2775个月前更新

在你的电脑上运行

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Telegram Context MCP

Read Telegram through your own account from an MCP client. Find permitted conversations, search and read original posts, navigate topics and replies, and inspect albums, reactions, and polls. Connect several local clients to one session-owning process, or run standalone STDIO.

Supports Windows, macOS, and Linux with Python 3.12–3.15. The server uses Telethon and preserves original text, dates, links, entities, and available metadata. It is read-only by default, never joins channels or marks messages read. Version 0.4 adds opt-in selected attachment downloads, durable change checkpoints, named subscriptions, and JSONL/Markdown exports with optional permanent copies. Subscriptions poll only when requested and retain a batch until acknowledged. It also bounds scope previews, returns restricted search results earlier, reuses dialog snapshots and accepts concurrent calls. See the 0.4 migration guide before upgrading from 0.3.

Version 0.5 adds bounded history across chats or folders, watch batches saved before acknowledgement, and watch_digest / period_digest prompts with local watch-name completion. When upgrading, restart the server and client proxies and refresh tools and prompts. The 0.5 changelog describes the additive changes and archive setup. Version 0.5.1 is a security patch: Telegram's service-notification chat, which delivers login codes, is never readable, even with all-chat or folder access. Upgrade every installation.

Version 0.6 adds optional PDF/DOCX text extraction with bounded continuation and source references, terminal QR login, a Claude Desktop MCPB bundle, and an optional Agent Skill. For document extraction, install 'telegram-context-mcp[extraction]==0.8.0' in the session-owning server and enable attachment downloads. See the usage guide for limits and platform coverage.

Version 0.7 adds message buttons, outgoing search, channel membership, authentication-notice omission, and opt-in native drafts, reusable files, confirmed sends and private-bot callbacks. Write capabilities default off; native drafts support plain text only. See outbound workflows for permissions, client confirmation requirements, recovery and validation limits.

Install and log in

Install uv, then run:

uv tool install --python 3.12 telegram-context-mcp==0.8.0

telegram-mcp --version telegram-mcp login telegram-mcp configure telegram-mcp status

These examples target release 0.8.0; check PyPI for published versions. Use the source setup for unreleased revisions. Upgrading from 0.3? Read the migration guide, then restart the server and refresh your client's tool schemas.

Obtain api_id and api_hash from my.telegram.org, then enter them in the local login prompt with your phone number, login code, and any 2FA password. Do not send login codes or credentials to the model.

Version 0.6 also supports telegram-mcp login --qr: scan the terminal QR from Telegram on your phone instead of entering a phone number and login code. See the QR login guide.

configure lets you choose folders/chats and separately enable all-chat access, explicit public-channel reads, or public-channel discovery. Enter keeps the current value. By default, no message sources are permitted. status should report authorized: true after login. Use catalog to find folder and chat IDs locally.

The package name is `telegram-context-mcp`; the executable is `telegram-mcp`. You can also run a pinned version without installing a persistent command:

uvx --python 3.12 --from telegram-context-mcp==0.8.0 telegram-mcp --version

The server is listed in the official MCP Registry as io.github.egor-fedorov/telegram-mcp. The entry launches a local STDIO server through uvx; it does not supply a hosted Telegram service. Complete login and configure locally before connecting a client. Registry publication starts with version 0.5.0. See the release procedure for verification and the client guide for sharing one session between clients.

Connect your clients

Start one server in a terminal and leave it running:

telegram-mcp serve --transport http

On Linux with systemd, the optional user-service setup starts that server at login and keeps it running independently of a terminal.

It listens only on http://127.0.0.1:8765/mcp. Configure each MCP client to launch telegram-mcp connect over STDIO. This small proxy reads the local token and connects to the existing server; it does not start a server or silently fall back to another Telegram session. Closing a client leaves the shared server running.

Client examples cover Codex, Claude Desktop, Claude Code, Cursor, and VS Code, including a pinned uvx command and executable paths for Windows.

A Claude Desktop MCPB bundle is attached to each matching GitHub Release. It uses the same shared server and separate local login; see the guide for installation and current validation coverage.

For one client, standalone STDIO is still available: configure that client to launch telegram-mcp serve. Use either mode for a given session. Stop the session-owning process before running local login, configure, catalog, or status; use the get_status MCP tool while the server is running.

All shared clients use the same Telegram account, read permissions, and cursor store. The HTTP bearer token is created in the local user profile and read by connect; do not paste it into client configuration. This is a local, single-user integration.

Tools

Tool	Purpose
`get_status`	Authorization, connection, permitted sources; running server/proxy build identity
`list_folders`	Folders, IDs, order, inclusion/exclusion rules
`list_chats`	Chats filtered by name, type, or folders
`get_chat`	Description and linked discussion group
`search_public_channels`	Find public broadcast channels by query; metadata only
`get_similar_channels`	Find similar public channels for one specified public source; metadata only
`search_messages`	Search by keywords, chats, folders, dates, sender, media type, or links
`get_history`	Chat or forum-topic history over a time range, in either order; bounded chat/folder periods
`list_topics`	Forum topics with navigation references, optional title query, and pagination
`get_pinned_messages`	Chat-wide or forum-topic pinned messages, newest first
`get_messages`	Messages by links/IDs with authors, dates, attachments, counters, reactions, and polls
`get_album`	Members of a selected album within a bounded neighborhood of one message
`get_context`	Messages before/after an anchor and a chain of parent replies
`get_thread`	Comments on a channel post or replies in a group thread
`download_attachment`	One selected attachment up to 20 MiB as a temporary local file and MCP resource
`extract_attachment_text`	Optional local PDF/DOCX text extraction with bounded continuation and PDF page references
`get_changes`	New messages and recent observed revisions in one chat, with restartable checkpoints
`create_watch` / `list_watches`	Save and discover named chat/folder subscriptions
`get_watch_changes` / `ack_watch_changes`	Poll and acknowledge a durable batch without per-chat tokens; optionally save it first
`delete_watch`	Explicitly discard a subscription and its pending batch
`export_history`	Source-linked JSONL or Markdown history in bounded, restartable parts

When a write capability is enabled, these additional tools appear. Each still checks its own capability flag and explicit recipient permission:

Tool	Purpose
`get_draft` / `list_drafts`	Read native drafts and revisions for permitted recipients
`create_draft` / `update_draft`	Prepare plain-text drafts with conflict checks and local confirmation policy
`register_file` / `list_files`	Register and discover immutable files for reuse in sends
`send_message` / `send_file`	Send one text or file under local permission/form policy with a durable idempotency key
`get_send_status`	Read a stored send/callback receipt by operation ID or idempotency key
`resolve_recipient`	Exact recipient metadata and local send/form policy without history
`verify_sent_message`	Reread only this MCP's sent message and compare text/attachment metadata
`list_operations`	Filter and page through this account's MCP journal; excludes manual sends
`invoke_button`	Invoke one ordinary callback in a selected private bot dialog under local form policy

Version 0.8.0 adds all-chat/one-off recipient modes, independent form settings and outbound inspection/recovery; see outbound policies.

Two prompts package these tools for monitoring: watch_digest turns a named watch into a source-linked digest, saving each batch before acknowledging it; period_digest reads one chat or folder over a fixed period with explicit budgets. They do not add permissions. See monitoring prompts.

An optional Agent Skill guides tool selection, bounded reading, watch acknowledgements and selected attachments. Install it in your client separately from the server; see the skill setup.

First tasks

Ask the client to list the folders you permitted and read a selected conversation over a timezone-qualified date range.
Enable discovery to find candidate public channels, select a source, then read its posts with a separate read permission.
Follow next_cursor with the original filters until it is null. An empty page can still have a cursor. Respect retry_after_seconds after a temporary failure.
For

只显示了开头部分；其余内容请在仓库中阅读

Telegram Context MCP

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“聊天与邮件”中的其他服务器比较i

常见问题

替代选择

Vexa

emailmd

MCP WhatsApp Cloud

作者的 README

Telegram Context MCP

Install and log in

Connect your clients

Tools

First tasks