Telegram MCP servers compared
Several open-source projects connect AI agents to a personal Telegram account. This table compares what each one ships, taken from its README and manifest in November 2026.
| 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 |
If something here is out of date, open an issue on GitHub.
When Better-TG-CLI fits
- You want the same tool as a CLI for agents with a shell (Claude Code, Codex) and as an MCP server for the others.
- You want each send approved: mode
askshows the exact text and runs it only after your yes. - You want output that is cheap on tokens: one compact line per item, single-line JSON.
- You want one file with no runtime dependencies, or a standalone binary.