mcp · Global

telegram-mcp-server

Telegram MCP server — Telethon, 9 grouped tools, multi-session pool, flood-safe

Feature or claim this listing

Feature this listing — founding Featured slots are 50% off for 6 months

Represent telegram-mcp-server? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.

Explore paid sponsorship →

What's in it

Data offered llm-inferred: Send, forward, delete and reply to messages · List chats, chat info and members; leave chats · Search messages, users and channels · Chat message, media and file history · Create, join and leave channels; channel info · User info, block and unblock · Send photos, videos, files and voice notes · Save, list and delete draft messages
Formats llm-inferred: MCP stdio
Access docs-verified: MIT licence; requires Telegram API ID and API Hash from my.telegram.org, plus a user login (2FA supported) or a bot token

Useful for

Use cases llm-inferred: Send site incident or flood-warning notifications to a project team Telegram group · Export photos and files shared in a monitoring channel as an evidence log · Route field-visit photos and files from site staff into a client group chat
Audience llm-inferred: flood consultants · site managers and field teams · developers building messaging automation

Limitations

Constraints llm-inferred: Send actions capped at 5/min; read actions unlimited · FloodWaitError auto-retried, waiting up to 5 min · Not a hydrological or flood data source: docs describe no gauge, rainfall or model data; 'flood' category appears to refer to flood-wait handling · Requires a Telegram account or bot token plus API credentials; session files stored locally · ENTRY tool names (send, members, etc.) do not match the 9 grouped tools in docs (tg_session, tg_message, etc.)

Licence: Unknown — check provider terms
Authentication: Unknown — review source docs
GitHub stars: 1
Last commit: 22/08/2026
Last successful page check: 14/10/2026
Page health: healthy
Package: Not recorded
Verification: Not independently verified

Auto-extracted, unverified fields: tools, install, auth. Check upstream documentation.

Provenance & evidence

Tools/install/auth auto-extracted from README; quality score heuristic (stars, recency, tool count, licence).

Metadata observed 16/10/2026 · research sweep: github-search