Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
제작자가 쓴 설명(영어 원문)
Telegram on your own account: read, search, send and press bot buttons. Writes need your approval.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
TG_PROFILE필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요
{
"mcpServers": {
"better-tg-cli": {
"command": "npx",
"args": [
"-y",
"better-tg-cli",
"mcp"
],
"env": {
"TG_PROFILE": "your-value"
}
}
}
}터미널에서 이 명령어를 실행하세요
claude mcp add better-tg-cli --env TG_PROFILE=your-value -- npx -y better-tg-cli mcp실행하기 전에 빈 값을 채워 주세요.
프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"better-tg-cli": {
"command": "npx",
"args": [
"-y",
"better-tg-cli",
"mcp"
],
"env": {
"TG_PROFILE": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"better-tg-cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"better-tg-cli",
"mcp"
],
"env": {
"TG_PROFILE": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
TG_PROFILE env이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
레지스트리 이름이 GitHub 계정 TheVilfer 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.39.5)은 오늘 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Node.js도 있어야 해요.
같은 카테고리에는: Vexa, emailmd, MCP WhatsApp Cloud
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ 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, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Install · Reference · Security · Issues · Русский · Español
https://github.com/user-attachments/assets/d143f7c7-7d50-439c-b373-cbcbff5a6675
Better-TG-CLI is a Telegram CLI and MCP server for AI agents (Claude Code, Codex, Cursor, Claude Desktop, Gemini CLI) that works on your own Telegram account: agents read, search and send messages and press bot buttons, and you approve every send.
It is an unofficial, open-source client (MTProto via teleproto, TL layer 229). The command is telegram: about 60 commands for reading, searching, writing, bots, groups and exports, built so that agents can drive it cheaply and safely. It also ships as an MCP server (telegram mcp) and an agent skill.
$ telegram inbox -n 3
48 unread in 7 chats (showing 3) 1234567890 user unread=2 Alice @alice | see you at 7? -1001234567 supergroup muted unread=41 Rust Seattle @rust_sea | anyone tried 1.90? -1009876543 channel unread=5 Changelog | v2.4 is out $ telegram read @alice -n 1 --json {"chatTitle":"Alice","messages":[{"id":812,"date":"2026-09-27T10:02:11.000Z","sender":"Alice","senderId":"1234567890","text":"see you at 7?"}]}
[!WARNING]
Your account, your risk. This is an unofficial client that logs in as you. Telegram may
limit or freeze accounts that behave like bots. The risk is highest for new accounts, bulk
messaging, mass joins or invites, and anything that looks like spam. Use it the way you would
use Telegram yourself, keep writes off unless you need them, and read SECURITY.md
before letting an agent write. The authors are not responsible for restricted accounts.
Contents: Why Better-TG-CLI · Install · Log in · Usage · MCP server · FAQ · Development · Privacy · License
Made for agents:
(no text). You can press bot buttons (click) and walk bot menus.--max-text trims long posts. telegram help-all -g prints every flag, generated from the code.--since/--until, --unread, threads and channel comments, forum topics, get by ID, search filters by type, sender or date, and me / Избранное for Saved Messages.write-access on) needs your own confirmation in a terminal or a macOS dialog. Every write is logged to ~/.config/tg/audit.jsonl. Secrets live in the macOS Keychain, the Linux Secret Service or 1Password.It started as a fork of skillhq/telegram and has since been reworked throughout.
| Better-TG-CLI | chigwell/telegram-mcp | chaindead/telegram-mcp | WireCatLabs/tg-cli | |
|---|---|---|---|---|
| What you get | CLI, MCP server, agent skill | MCP server | MCP server | CLI, MCP server, agent skill |
| Language | TypeScript (Node 20+ or a standalone binary) | Python | Go | TypeScript |
| Telegram library | teleproto (GramJS fork, layer 229) | Telethon | gotd/td | mtcute |
| Runtime dependencies | none (one file) | Python packages | one Go binary | npm packages |
| Install | Homebrew, Scoop, npm, binaries | pip, uvx, Docker | Homebrew, npx, go install | npm, bun |
Taken from each project's README and manifest in November 2026; open an issue if something here is out of date. What sets Better-TG-CLI apart is the write model (read-only, ask, on, with approvals bound to the exact text) and output made for agents.
brew install thevilfer/tap/better-tg-cli # standalone binary, macOS and Linux
npm install -g better-tg-cli # Node >= 20, any OS
On Windows (experimental), with Scoop or npm:
scoop bucket add thevilfer https://github.com/TheVilfer/scoop-bucket
scoop install better-tg-cli
The Windows telegram.exe is not code-signed, so SmartScreen may warn about the release download.
telegram update upgrades an existing install, whichever of these you used. On a terminal the CLI checks for new versions once a day. Agents and pipes never see that notice, and TG_NO_UPDATE_CHECK=1 turns it off.
Downloading a binary from Releases by hand on macOS? It is not notarized, so remove the quarantine flag once: xattr -d com.apple.quarantine ./telegram. Homebrew handles this for you.
Do not install @skillhq/telegram. It is the old upstream build on GramJS (layer 198).
Every channel ships the same version from one release:
| Where | What you get | Install |
|---|---|---|
| Homebrew | standalone binary | brew install thevilfer/tap/better-tg-cli |
| npm | CLI and MCP server (Node 20+) | npm install -g better-tg-cli |
| Scoop (Windows, experimental) | standalone telegram.exe | scoop bucket add thevilfer https://github.com/TheVilfer/scoop-bucket then scoop install better-tg-cli |
| GitHub Releases | binaries and SHA256SUMS | download by hand |
| Claude Code plugin | skill (uses the installed CLI) | see below |
| Claude Desktop extension | MCP server, runs on Claude's built-in Node | download .mcpb and open it |
| Grok Build plugin | skill and MCP server | see below |
| Gemini CLI extension | skill and MCP server | gemini extensions install https://github.com/TheVilfer/better-tg-cli |
| Cursor, VS Code | MCP server | one-click buttons |
| Grok Bot | MCP server over HTTP from your Mac | see below |
| The CLI itself | agent skill for Claude Code, Codex, Cursor, Gemini CLI and 7 more | telegram skill install |
| skills.sh | agent skill for any shell agent | npx skills add TheVilfer/better-tg-cli |
| MCP Registry | MCP server entry io.github.TheVilfer/better-tg-cli | through your MCP client |
The skill as a plugin, kept up to date by Claude Code:
/plugin marketplace add TheVilfer/better-tg-cli
/plugin install better-tg-cli@better-tg-cli
The plugin is the skill alone, so install the CLI first (above) and log in once with telegram onboard in a terminal. Claude Code then runs telegram itself. Anthropic's plugin directory accepts MCP servers that run on your computer only from Verified organizations, so the MCP server is added on its own if you want it: claude mcp add telegram -- telegram mcp.
The skill and the MCP server as a Codex plugin (also shows up in the ChatGPT desktop app):
codex plugin marketplace add TheVilfer/better-tg-cli
codex plugin add better-tg-cli@better-tg-cli
Grok Build installs the plugin with the skill and the MCP server together:
grok plugin install TheVilfer/better-tg-cli --trust
grok plugin marketplace add TheVilfer/better-tg-cli && grok plugin install better-tg-cli --trust
The skill (skills/better-tg-cli) teaches any agent with a shell (Claude Code, Codex, Cursor, Gemini CLI, OpenCode and others) to use the CLI safely. It checks the setup, never logs in on its own, keeps writes behind your approval, and avoids ban-prone patterns. The CLI carries the skill and installs it itself, so it always matches your version:
telegram skill install # every supported agent found on this machine
telegram skill install -a claude-code codex telegram skill status # installed, outdated, linked or missing, per agent
It knows Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Grok Build, OpenCode, Goose, Droid, Windsurf and Pi (telegram skill status lists the folders). Run it again after telegram update to refresh the skill. A skill folder that is a symlink is left alone unless you pass --force. For other agents, use the skills CLI:
npx skills add TheVilfer/better-tg-cli # pick agents interactively
npx skills add TheVilfer/better-tg-cli -g -a claude-code -a codex -y
Through your agent (easiest): ask it to set up Telegram, or run telegram onboard yourself. It opens a page on 127.0.0.1 where you get a login key from better-tg-cli.com (it comes back to the page by itself) or enter your own keys, scan a QR code and type your 2FA password. The agent only starts the command and waits: it never sees the login key, the QR code or the password. The page answers only on a random secret path and closes when you're done.
With your own API keys (the default):
api_id and api_hash.telegram auth --qr and enter them. Then, on your phone, go to Settings → Devices → Link Desktop Device and scan the QR code. Enter your 2FA password if you have one. Plain telegram auth asks for y앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요