Skip to content

Commit df30843

Browse files
OlegNickeshinclaude
OlegNickeshin
and
claude
committed
feat(lemma-telepath): add Telegram MCP connector
Telepath connects a person's own Telegram account to ZCode over a hosted MCP server: full-text search across their chat archive, reading the documents, photos and transcribed voice inside it, and replying as themselves. It is not another channel for talking to an assistant through Telegram — it gives the assistant the conversations the user already has. It runs on Telegram's official business-bot API, a bot the user adds to their own account under Settings → My Account → Chat automation, which is open to every account and needs no Telegram Premium. No MTProto user session is involved. The package ships manifests and documentation only — no code, no hooks, no commands, no local writes. Both READMEs document the three endpoints it calls, the OAuth 2.1 flow, the capabilities and their real side effects (a send reaches an actual person), the optional paid features, and the fact that the hosted service is not end-to-end encrypted. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LwR27tqA86qU2jPwP9uF3S
1 parent ded8021 commit df30843

5 files changed

Lines changed: 242 additions & 0 deletions

File tree

‎marketplace.json‎

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1278,6 +1278,33 @@
12781278
"watermark",
12791279
"video"
12801280
]
1281+
},
1282+
{
1283+
"name": "lemma-telepath",
1284+
"displayName": "Telepath",
1285+
"displayName_i18n": {
1286+
"en": "Telepath",
1287+
"zh-CN": "Telepath"
1288+
},
1289+
"source": "./plugins/lemma-telepath",
1290+
"description": "Connect your Telegram to ZCode: search your chat archive, read the documents, photos and transcribed voice inside it, and reply as yourself — through a hosted MCP server.",
1291+
"description_i18n": {
1292+
"en": "Connect your Telegram to ZCode: search your chat archive, read the documents, photos and transcribed voice inside it, and reply as yourself — through a hosted MCP server.",
1293+
"zh-CN": "将你的 Telegram 接入 ZCode：全文检索聊天归档，读取其中的文档、图片与语音转写，并以你本人的身份回复——通过托管的 MCP 服务器。"
1294+
},
1295+
"version": "0.1.0",
1296+
"author": {
1297+
"name": "Lemma",
1298+
"url": "https://lemma.company"
1299+
},
1300+
"category": "productivity",
1301+
"keywords": [
1302+
"telegram",
1303+
"telepath",
1304+
"mcp",
1305+
"messaging",
1306+
"search"
1307+
]
12811308
}
12821309
]
12831310
}

‎plugins/lemma-telepath/.mcp.json‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
{
2+
"mcpServers": {
3+
"telepath": {
4+
"type": "http",
5+
"url": "https://telepath.lemma.company/mcp"
6+
}
7+
}
8+
}

‎plugins/lemma-telepath/.zcode-plugin/plugin.json‎

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
{
2+
"name": "lemma-telepath",
3+
"description": "Connect your Telegram to ZCode: search your chat archive, read the documents, photos and transcribed voice inside it, and reply as yourself — through a hosted MCP server.",
4+
"description_i18n": {
5+
"en": "Connect your Telegram to ZCode: search your chat archive, read the documents, photos and transcribed voice inside it, and reply as yourself — through a hosted MCP server.",
6+
"zh-CN": "将你的 Telegram 接入 ZCode：全文检索聊天归档，读取其中的文档、图片与语音转写，并以你本人的身份回复——通过托管的 MCP 服务器。"
7+
},
8+
"version": "0.1.0",
9+
"author": {
10+
"name": "Lemma",
11+
"url": "https://lemma.company"
12+
},
13+
"homepage": "https://telepath.lemma.company",
14+
"repository": "https://github.com/Lemma-Company/telepath-plugin",
15+
"license": "MIT",
16+
"keywords": [
17+
"telegram",
18+
"telepath",
19+
"mcp",
20+
"messaging",
21+
"search"
22+
],
23+
"displayName": "Telepath",
24+
"displayName_i18n": {
25+
"en": "Telepath",
26+
"zh-CN": "Telepath"
27+
},
28+
"mcpServers": ".mcp.json"
29+
}

‎plugins/lemma-telepath/README.md‎

Lines changed: 95 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,95 @@
1+
# Telepath — your Telegram, readable by ZCode
2+
3+
[中文文档](./README_CN.md)
4+
5+
Telepath connects **your own Telegram account** to ZCode through a hosted MCP
6+
server. Not another chat channel for talking to an assistant — it gives the
7+
assistant access to the conversations you already have: search the archive, read
8+
the documents, photos and transcribed voice inside it, and reply as yourself.
9+
10+
It runs on Telegram's official business-bot API — a bot you add to your own
11+
account — not on an MTProto user session. Nothing here logs in as you.
12+
13+
## What it adds
14+
15+
One MCP server, `telepath`, reached over HTTP at
16+
`https://telepath.lemma.company/mcp`. Its tools cover:
17+
18+
- full-text search across your archived chats, captions and voice transcripts;
19+
- reading a chat's recent messages, or a specific message and its context;
20+
- opening attachments by content — PDFs, spreadsheets, documents, photos;
21+
- sending, editing and reacting in your own chats, as yourself;
22+
- a small markdown notes store scoped to your account.
23+
24+
Which of these exist in a session depends on the capabilities you leave enabled;
25+
every one of them is a switch you control from the Telegram bot.
26+
27+
## Setup
28+
29+
1. In Telegram: **Settings → My Account → Chat automation**, add
30+
**@lemma_telepath_bot**, and choose which conversations it may access. This
31+
entry is open to every account — **Telegram Premium is not required**.
32+
2. Install this plugin. ZCode registers the remote MCP server and asks you to
33+
authorize it.
34+
3. Sign in with Telegram when the browser opens. That is the whole of the
35+
authentication; there is no API key and nothing to paste into chat.
36+
37+
From that moment, new messages in the chats you picked are archived and become
38+
searchable from ZCode. Nothing older is imported unless you ask for it.
39+
40+
Walkthrough with screenshots: https://telepath.lemma.company/start
41+
42+
## Network access
43+
44+
The plugin itself ships no code — only this manifest and documentation. Every
45+
request goes to one domain:
46+
47+
| Endpoint | Why |
48+
|---|---|
49+
| `https://telepath.lemma.company/mcp` | the MCP server itself (streamable HTTP) |
50+
| `https://telepath.lemma.company/authorize`, `/token`, `/register` | OAuth 2.1 with PKCE and dynamic client registration |
51+
| `https://telepath.lemma.company/oauth/login` | the sign-in page, which loads the Telegram Login widget from `oauth.telegram.org` |
52+
53+
No `curl | bash`, no downloaded executables, no `postinstall` step, no hooks, no
54+
commands, no local file writes.
55+
56+
## Permissions and side effects
57+
58+
- **It reads your messages.** Only the chats you chose in Telegram, only from the
59+
moment you connected the bot.
60+
- **It can send and edit messages as you**, if you leave that capability on.
61+
This is a real side effect in the world: a tool call reaches an actual person.
62+
Telegram allows it only in private chats that received an incoming message
63+
within the last 24 hours.
64+
- **Voice transcription is optional and paid.** When enabled, audio is sent to
65+
Mistral (Voxtral, EU) to be turned into text; it is not reused for training,
66+
and no copy is kept once the transcript is stored. Everything else stays on
67+
our server.
68+
- **Group archiving, history import and bringing your own bot** are optional and
69+
off by default.
70+
71+
Turn any of this off, or erase everything, from the bot: `/settings`,
72+
`/deletedata`.
73+
74+
## Honest limits
75+
76+
Telepath is a **hosted service**, and it is **not end-to-end encrypted** — to
77+
search and transcribe for you, our servers process your messages, so we can
78+
technically access them. We say so plainly rather than implying otherwise.
79+
80+
Each account gets a physically separate database, the disk is encrypted at rest
81+
(LUKS full-disk), and credentials are encrypted or hashed on top. If you need a
82+
guarantee that no operator can ever read it, the connector is also available to
83+
self-host, single-tenant, as the same code.
84+
85+
- Privacy policy: https://telepath.lemma.company/privacy
86+
- Terms: https://telepath.lemma.company/terms
87+
- Support: https://telepath.lemma.company/support
88+
89+
## Licensing and provenance
90+
91+
This plugin package is **MIT** — see the
92+
[source repository](https://github.com/Lemma-Company/telepath-plugin). It
93+
contains manifests and documentation only; none of the server's code is in it.
94+
The hosted service it points at is operated by Lemma under the terms linked
95+
above. Telepath is not affiliated with Telegram or Z.ai.

‎plugins/lemma-telepath/README_CN.md‎

Lines changed: 83 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
1+
# Telepath —— 让 ZCode 读懂你的 Telegram
2+
3+
[English](./README.md)
4+
5+
Telepath 通过托管的 MCP 服务器，把**你本人的 Telegram 账号**接入 ZCode。它不是又一个
6+
"用 Telegram 和 AI 聊天"的通道，而是让助手能够使用你已有的对话：检索归档、读取其中的
7+
文档、图片与语音转写，并以你本人的身份回复。
8+
9+
它运行在 Telegram 官方的 business-bot API 之上——你把一个机器人添加到自己的账号——
10+
而不是 MTProto 用户会话。这里没有任何东西会以你的身份登录。
11+
12+
## 它提供什么
13+
14+
一个名为 `telepath` 的 MCP 服务器，通过 HTTP 连接到
15+
`https://telepath.lemma.company/mcp`。其工具包括：
16+
17+
- 对已归档的聊天、图片说明与语音转写进行全文检索；
18+
- 读取某个会话的最近消息，或某条具体消息及其上下文；
19+
- 按内容打开附件—— PDF、表格、文档、图片；
20+
- 在你自己的会话中以你本人的身份发送、编辑消息和添加表情回应；
21+
- 一个仅限你账号使用的小型 Markdown 笔记库。
22+
23+
一次会话中实际存在哪些工具，取决于你保留启用的权限；每一项都是你在 Telegram 机器人里
24+
可以自行开关的开关。
25+
26+
## 安装与配置
27+
28+
1. 在 Telegram 中打开 **设置 → 我的账号 → 聊天自动化（Settings → My Account → Chat
29+
automation）**，添加 **@lemma_telepath_bot**，并选择它可以访问哪些会话。该入口对
30+
**所有账号开放——不需要 Telegram Premium**。
31+
2. 安装本插件。ZCode 会注册该远程 MCP 服务器，并提示你进行授权。
32+
3. 浏览器打开后用 Telegram 登录。这就是全部的身份验证过程：没有 API key，也不需要把
33+
任何凭据粘贴到对话里。
34+
35+
从这一刻起，你所选会话中的新消息会被归档，并可在 ZCode 中检索。除非你主动要求，否则
36+
不会导入此前的历史记录。
37+
38+
图文教程：https://telepath.lemma.company/start
39+
40+
## 网络访问
41+
42+
插件本身不包含任何代码——只有清单文件与文档。所有请求都指向同一个域名：
43+
44+
| 地址 | 用途 |
45+
|---|---|
46+
| `https://telepath.lemma.company/mcp` | MCP 服务器本身（streamable HTTP） |
47+
| `https://telepath.lemma.company/authorize`、`/token`、`/register` | OAuth 2.1，含 PKCE 与动态客户端注册 |
48+
| `https://telepath.lemma.company/oauth/login` | 登录页面，其中加载来自 `oauth.telegram.org` 的 Telegram 登录控件 |
49+
50+
没有 `curl | bash`，不下载可执行文件，没有 `postinstall` 步骤，没有 hooks、没有
51+
commands，也不写入本地文件。
52+
53+
## 权限与副作用
54+
55+
- **它会读取你的消息。** 仅限你在 Telegram 中选择的会话，且仅从你连接机器人的那一刻起。
56+
- **在你保留该权限时，它能以你的身份发送和编辑消息。** 这是会作用于现实世界的副作用：
57+
一次工具调用会真正送达某个人。Telegram 仅允许在最近 24 小时内收到过对方消息的私聊中
58+
这样做。
59+
- **语音转写是可选的付费功能。** 启用后，音频会发送至 Mistral（Voxtral，欧盟）转为文字；
60+
不会被用于训练，转写结果保存后也不保留音频副本。其余处理都在我们自己的服务器上完成。
61+
- **群组归档、历史记录导入、使用你自己的机器人**均为可选项，默认关闭。
62+
63+
以上任何一项都可以在机器人中关闭或彻底清除：`/settings`、`/deletedata`。
64+
65+
## 需要如实说明的限制
66+
67+
Telepath 是**托管服务**，并且**不是端到端加密的**——为了替你检索和转写，我们的服务器
68+
必须处理你的消息，因此技术上我们能够访问它们。我们选择把这一点讲清楚，而不是含糊其辞。
69+
70+
每个账号拥有物理隔离的独立数据库，磁盘整体静态加密（LUKS 全盘加密），凭据在此之上另行
71+
加密或哈希存储。如果你需要"运营方绝无可能读取"的保证，该连接器同样可以自行部署——
72+
单租户、同一套代码。
73+
74+
- 隐私政策：https://telepath.lemma.company/privacy
75+
- 服务条款：https://telepath.lemma.company/terms
76+
- 技术支持：https://telepath.lemma.company/support
77+
78+
## 许可与来源
79+
80+
本插件包采用 **MIT** 许可，见
81+
[源仓库](https://github.com/Lemma-Company/telepath-plugin)。其中仅包含清单文件与文档，
82+
不含服务端的任何代码。它所指向的托管服务由 Lemma 运营，适用上面链接的条款。Telepath
83+
与 Telegram、Z.ai 均无从属关系。

0 commit comments

Comments
 (0)