Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
作者提供的说明(英文原文)
Multi-tenant Telegram gateway for AI agents — HTTP+stdio, 8 tools, MTProto User API
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
API_ID, API_HASH, SERVER_MODE, SESSION_DIR标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://tg-mcp.l1979.ru/v1/mcp打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"fast-telegram": {
"command": "uvx",
"args": [
"fast-mcp-telegram"
],
"env": {
"API_ID": "your-value",
"API_HASH": "your-value",
"SERVER_MODE": "your-value",
"SESSION_DIR": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http fast-telegram https://tg-mcp.l1979.ru/v1/mcpclaude mcp add fast-telegram --env API_ID=your-value --env API_HASH=your-value --env SERVER_MODE=your-value --env SESSION_DIR=your-value -- uvx fast-mcp-telegram运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"fast-telegram": {
"url": "https://tg-mcp.l1979.ru/v1/mcp"
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"fast-telegram": {
"command": "uvx",
"args": [
"fast-mcp-telegram"
],
"env": {
"API_ID": "your-value",
"API_HASH": "your-value",
"SERVER_MODE": "your-value",
"SESSION_DIR": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"fast-telegram": {
"type": "http",
"url": "https://tg-mcp.l1979.ru/v1/mcp"
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"fast-telegram": {
"type": "stdio",
"command": "uvx",
"args": [
"fast-mcp-telegram"
],
"env": {
"API_ID": "your-value",
"API_HASH": "your-value",
"SERVER_MODE": "your-value",
"SESSION_DIR": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://tg-mcp.l1979.ru/v1/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
SERVER_MODE envSESSION_DIR env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
工具名称和描述与服务器在 2026年11月7日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
search_messages_globallySearch all Telegram chats at once (not scoped to one chat). Comma-separated query terms; optional filters by date, chat kind, and public username. Results are ordered by ascending date-time (oldest first); limit selects the newest N. Success: message list and metadata dict. Globa
get_messagesRead or search messages in one chat: browse latest, search text, fetch by ids, or load replies to a message (comments, forum topics, threads). Use from_user to filter by sender (server-side, per-chat only). Use context to include neighboring messages and reply chains around each
send_messageSend text and optional file attachments to a Telegram chat. Supports reply-to (including forum topics and channel discussion groups), parse_mode: classic markdown/html/auto (entities) or rich (Rich Message document; dialect auto-detected). parse_mode=rich cannot be combined with
edit_messageReplace the text of an existing message in a Telegram chat. Only works on messages sent by the authenticated account. Cannot edit media or other message attributes — text only. parse_mode: classic markdown/html/auto or rich (Rich Message; dialect auto-detected). schedule_date (IS
find_chatsFind users/groups/channels by name, username, or phone. Comma-separated usernames are searched in parallel and results are merged round-robin. Global search (query required) searches all Telegram; with min_date, max_date, or filter, search uses dialog list or a named filter; incl
get_chat_infoLoad profile and metadata for one user, bot, group, or channel. Success: info dict; forum chats may include topics up to topics_limit; user targets may include common_chats up to common_chats_limit. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main
send_message_to_phoneSend to a phone number: may create a temporary contact, then send text or files. Supports parse_mode: classic markdown/html/auto or rich (Rich Message; dialect auto-detected). parse_mode=rich cannot be combined with files. schedule_date (ISO 8601, future) queues the message inste
invoke_mtprotoLow-level Telegram API (MTProto) invoke for methods not wrapped by other tools. Dangerous methods require allow_dangerous=true. Success: API result dict or normalized error. PII and credential-shaped fields (phone, access_hash) are dropped from a successful result by default; pas
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
注册名称已通过 GitHub 账户 leshchenko1979 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
在 1089 毫秒内响应(HTTP 200)
无需登录
已读取 8 个工具描述,未发现针对 AI 的隐藏指令
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:API_ID, API_HASH
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(0.46.1)于19天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Vexa, emailmd, MCP WhatsApp Cloud
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Telegram MCP Server — Model Context Protocol (MCP) gateway for Telegram. 8 context-efficient tools, multi-tenant, MTProto bridge.
Then choose your path:
MCP Client (AI assistants)
mcp.json fileDirect API (curl)
curl -X POST "https://tg-mcp.l1979.ru/mtproto-api/messages.SendMessage" \
-H "Authorization: Bearer TOKEN" \ -H "Content-Type: application/json" \ -d '{"params": {"peer": "me", "message": "Hello!"}}'
This server sits between your AI agent and Telegram's API:
Your agent → MCP/HTTP → this server → MTProto → Telegram
What it does: Authenticates you with Telegram (QR or phone/bot token), exposes 8 AI-friendly tools instead of 80+ micro-APIs, and bridges raw MTProto for power users. Multi-tenant — one server, many users, isolated sessions.
| Feature | Description |
|---|---|
| :building_construction: [Dual Transport](docs/Installation.md#overview) | Stdio for local MCP clients, HTTP for remote deploys (http-auth production, optional http-no-auth for dev) |
| :closed_lock_with_key: [Multi-User Authentication](docs/Installation.md#remote-setup-http-auth) | Shared http-auth server: one Bearer token per user, one Telegram account per MCP connection. QR login for instant auth — no phone/OTP/2FA. |
| :dart: [AI-Optimized](docs/Tools-Reference.md#overview) | 8 consolidated tools vs 80+ micro-tools — context-efficient design, LLM-friendly API, MCP ToolAnnotations |
| :globe_with_meridians: [HTTP-MTProto Bridge](docs/MTProto-Bridge.md#key-benefits) | Direct curl access to any Telegram API method with entity resolution and safety guardrails |
| :shield: [Session ACL](docs/Installation.md#session-acl-http-auth) | Opt-in per-principal limits on http-auth (ACL_ENABLED) — chat lanes, read_only, blocked_peers, allow_mtproto, ACL_DENY_UNLISTED_PRINCIPALS; see SECURITY.md |
| :tv: [QR & Web Setup](docs/Installation.md#web-setup-interface) | Scan QR from Telegram mobile for instant auth (no phone/OTP/2FA) or use phone/code/2FA fallback — live at /setup |
| :label: [One Agent, Multiple Accounts](docs/Installation.md#multi-account-mcp-tool-prefix) | Optional PREFIX_MCP_TOOLS_WITH_ACCOUNT — when one agent uses several MCP connections (same server, different tokens), prefixes tool names so they do not collide; not needed for standard multi-user hosting |
| :rocket: [MTProto Proxy Support](docs/Installation.md#mtproto-proxy) | Connect via MTProto proxy with automatic Fake TLS (EE prefix) and standard proxy detection |
| :card_file_box: [Unified Session Management](docs/Installation.md#configuration-reference) | Single configuration system for setup and server; per-token session files on shared multi-user hosts |
| :cloud: [S3 Session Storage](docs/Installation.md#s3-session-storage-optional) | Store sessions in S3-compatible object storage for ephemeral hosted deployments (Smithery, Fly.io, Railway) |
| :mag_right: [Intelligent Search](docs/Search-Guidelines.md#what-works) | Global & per-chat message search with multi-query support and intelligent deduplication |
| :mag: [Unified Message API](docs/Tools-Reference.md#2-read) | Single get_messages tool for search, browse, read by IDs, and replies - 5 modes in one |
| :speech_balloon: [Universal Replies](docs/Tools-Reference.md#2-read) | Get replies from channel posts, forum topics, or any message with one parameter |
| :busts_in_silhouette: [Smart Contact Discovery](docs/Tools-Reference.md#1-discovery) | Search users, groups, channels with uniform entity schemas, forum detection, profile enrichment |
| :file_folder: [Folder Filtering](docs/Tools-Reference.md#1-discovery) | Filter chats by dialog folder (archived, custom folders) with integer ID or name matching |
| :envelope: [Advanced Messaging](docs/Tools-Reference.md#3-write) | Send, edit, reply, post to forum topics, formatting, file attachments, and phone number messaging |
| :paperclip: [Secure File Handling](docs/Tools-Reference.md#3-write) | Rich media sharing with SSRF protection, size limits, album support, optional HTTP attachment streaming |
| :outbox_tray: [Inline File Uploads](docs/Tools-Reference.md#3-write) | Data: URI (base64) file uploads in files param — work in all transport modes, filenames preserved, images sent as photos |
| :microphone: [Voice Transcription](docs/Tools-Reference.md#get_messages) | Automatic speech-to-text for Premium accounts with parallel processing and polling |
| :zap: High Performance | Async operations, parallel queries, and memory-conscious batching |
| :shield: Production Reliability | Auto-reconnect, configurable logging, comprehensive error handling |
Quickest path (remote server): Open /setup → scan QR → copy token (see Try the Demo).
CLI path (local stdio): Run fast-mcp-telegram-setup once to create a Telegram session — then fast-mcp-telegram serves it:
uvx --from fast-mcp-telegram fast-mcp-telegram-setup \
--api-id="your_api_id" \ --api-hash="your_api_hash" \ --phone-number="+123456789"
Bot token alternative (no phone, no OTP): Set BOT_API_TOKEN instead of --phone-number. See Installation Guide.
stdio mode (local): Add to your MCP client config (e.g. claude_desktop_config.json) — stdio (standard input/output) is the default transport for local MCP clients:
{
"mcpServers": { "telegram": { "command": "uvx", "args": ["fast-mcp-telegram"], "env": { "API_ID": "your_api_id", "API_HASH": "your_api_hash" } } } }
http-auth mode (remote): Add to your MCP client config (e.g. claude_desktop_config.json):
{
"mcpServers": { "telegram": { "url": "https://tg-mcp.l1979.ru/mcp", "headers": { "Authorization": "Bearer YOUR_TOKEN" } } } }
Get your token by scanning the QR code on the setup page or see Installation Guide for deploying your own server.
{"tool": "search_messages_globally", "params": {"query": "hello", "limit": 5}}
{"tool": "get_messages", "params": {"chat_id": "me", "limit": 10}} {"tool": "send_message", "params": {"chat_id": "me", "message": "Hello!"}}
Deploy your own MCP server on a VDS — see Installation Guide for step-by-step instructions.
| Tool | Purpose | Key Features |
|---|---|---|
search_messages_globally | Search across all chats | Multi-term queries, date filtering, chat type filtering |
get_messages | Unified message retrieval | Search/browse, read by IDs, get replies (posts/topics/messages), date filtering in all modes |
send_message | Send new message | File attachments (URLs/local/data URIs), classic formatting (markdown/html), parse_mode=rich Rich Messages, reply to forum topics |
edit_message | Edit existing message | Classic or parse_mode=rich formatting |
find_chats | Find users/groups/channels | Multi-term search, contact discovery, folder filtering, username/phone lookup |
get_chat_info | Get detailed profile info | Member counts, bio/about, online status, forum topics, common groups, enriched data |
send_message_to_phone | Message phone numbers | Auto-contact management, optional cleanup, file support (URLs/data URIs), parse_mode=rich |
invoke_mtproto | Direct Telegram API (power user) | Raw MTProto methods, entity resolution, PII/credential fields dropped by default (include_sensitive=true for raw) — see MTProto Bridge |
See Tools Reference for detailed documentation with examples.
Anonymous tool telemetry since v0.30.1 — heartbeat every 6h, no credentials or message content collected. Opt out with DO_NOT_TRACK=1. See ADR 0005.
Auth flow telemetry since v0.38.0 — atomic events during setup (phone, QR, bot token, reauthorize). Buffered flush on flow completion. See ADR 0008.
MIT License - see LICENSE
mcp-name: io.github.leshchenko1979/fast-mcp-telegram