Compared · telegram
12 Telegram MCP servers. Which one to use.
Every Telegram server we index, with whether its source is still reachable and whether we hold a screening verdict. 3 of 12 have a source repository that is no longer publicly reachable.
Scope: 12 servers indexed from the MCP registry as of 2026-07-25. Servers whose authors never published to the registry are not listed here, so treat this as the registry's view rather than a complete census.
| Server | Publisher | Source | Screened | Quality | Install |
|---|---|---|---|---|---|
| Telegram (mcp-telegram) | io.github.mcp-telegram | no flag | REVIEW | 90 | npm @overpod/mcp-telegram |
| Better Telegram MCP | io.github.n24q02m | no flag | REVIEW | 90 | pypi better-telegram-mcp |
| Telegram MCP Server | io.github.tolboy | no flag | REVIEW | 90 | docker ghcr.io/tolboy/telegram-mcp-tdlib:1.9.0-stdio |
| io.github.Shreyas-Profile/telegram-mcp | io.github.Shreyas-Profile | no flag | not screened | 80 | remote endpoint |
| io.github.jgalea/telegram-mcp | io.github.jgalea | no flag | REVIEW | 79 | pypi telegram-mcp-jgalea |
| io.github.ParthJadhav/telegram-notify-mcp | io.github.ParthJadhav | no flag | REVIEW | 76 | npm @parthj/telegram-notify-mcp |
| io.github.auroracapital/claude-ops-telegram-server | io.github.auroracapital | no flag | REVIEW | 75 | npm claude-ops-telegram-server |
| io.github.GeiserX/telegram-archive-mcp | io.github.GeiserX | no flag | REVIEW | 74 | npm telegram-archive-mcp |
| io.github.daedalus/mcp-telegram-bot | io.github.daedalus | no flag | REVIEW | 68 | pypi mcp-telegram-bot |
| Limzo Telegram Group Stats | com.limzo | repo unreachable | REVIEW | 95 | npm limzo-mcp |
| io.github.leshchenko1979/fast-mcp-telegram | io.github.leshchenko1979 | repo unreachable | REVIEW | 84 | pypi fast-mcp-telegram |
| io.github.khadinakbaronline/telegram-channel-scraper-mcp | io.github.khadinakbaronline | repo unreachable | REVIEW | 79 | npm telegram-channel-scraper-mcp-server |
“Repo unreachable” means the source returned a not-found from two vantage points, which can also happen when a repository is made private or moved - see source liveness. “Screened” is the advisory verdict on the listing text, never a safety clearance; the methodology spells out what each dimension does and does not test.