Plugin
telegram
Connect a Telegram bot to your Claude Code session over MCP. The server logs in as a bot, forwards inbound messages into the session as <channel> notifications, and exposes tools to reply (with attachments up to 50MB), react with emoji, edit prior messages, and download inbound files. Built-in access control supports DM pairing flows and group/supergroup allowlists managed through the /telegram:access skill. Forum-topic routing via TELEGRAM_TOPIC_IDS lets a single bot fan out to multiple parallel Claude Code sessions, each bound to its own supergroup topic, so four sessions can work on four projects without racing for inbound messages. Proxy-aware transport (TELEGRAM_PROXY / HTTPS_PROXY) routes both text and multipart uploads through an HTTP proxy for use in regions where api.telegram.org is blocked or rate-limited.
- Analysed
- Last observed
What the code does
Static analysis found none of the capabilities we track, such as shell commands, network requests or file writes, in the latest version.
Having a capability is not wrongdoing; many tools need these to do their job. It tells you what to check before you install.
This is public metadata, not a safety certification or complete assessment. Static analysis cannot establish what a tool does at runtime.
Risk
Sign in to see this tool's overall risk level and what drives it. Free.
Coverage
Detailed report
No findings in the latest analysis. The report shows what was examined and any changes between versions.
Using this tool across your team? We can assess your whole inventory.
Request an inventory assessment