telegram
Developer not provided
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 att...
From the developer
Works with
Claude Code
Description
From the marketplace listing
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.
What changed
No changes recorded yet. Follow this plugin to keep track of future changes.
Similar plugins
Find competitors to follow as you develop your plugin.
-
Microsoft Teams channel for Claude Code. Connects a Claude Code session to Microsoft Teams via an MCP server with Bot Framework webhook. ...
Shared terms: bot, channel, inbound, message
-
This plugin connects Feishu (Lark) IM to Claude Code as a messaging channel. It runs an MCP server with tools such as reply, react, pair,...
Shared terms: attachment, channel, message, reply
-
Feishu (Lark) channel for Claude Code — messaging bridge that connects a Feishu bot to Claude Code via MCP server. Receives messages thro...
Shared terms: bot, channel, forward, message
-
Rust-based Telegram channel for Claude Code. Drop-in replacement for the official Bun-based Telegram plugin — same features, 20x lighter....
Shared terms: channel, telegram, code, allowlist
-
An MCP server that connects Mattermost to Claude Code — send and receive messages, manage files, and control access through a bot account.
Shared terms: bot, message, server, mcp
Files & skills
telegram · catalog manifest
Saved declaration
{}
telegram · catalog manifest
Saved declaration
{
"name": "telegram",
"source": {
"ref": "feat",
"url": "mjavadalavi/claude-plugins-official",
"path": "telegram-topic-routing",
"source": "git-subdir"
},
"homepage": "https://github.com/anthropics/claude-plugins-official",
"description": "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 \n api.telegram.org is blocked or rate-limited."
}
Catalog declarations and available plugin.json metadata are saved. Referenced skills and executable source files are not downloaded or tested. Missing components in a manifest do not prove that the plugin has none.
Installation instructions
Community
/plugin marketplace add anthropics/claude-plugins-community
/plugin install telegram@claude-communityTechnical details
- Sources
- Community
- First seen
- Oct 3, 2026 · 22:13 UTC
- Last seen
- Nov 7, 2026 · 18:00 UTC
- Latest observed change
- Oct 3, 2026 · 22:13 UTC
- Collection status
- Listed
- Reported installs
- Not provided
Installation counts are source-reported, not independently verified active users. Observation dates are not release dates.
Download plugin data (JSON)Plugin history: freshly prepared. Prepared . Refreshed when catalog data changes or after 6 hours. Your account and Follow status are live.