telegram
v0.0.16Telegram channel for Claude Code — messaging bridge with built-in access control. Durable inbound store so messages survive a disconnected session (replayed on restart with a structured replay flag), forward/reply attribution, the sender's highlighted quote, and ask_decision buttons. Manage pairing, allowlists, and policy via /telegram:access.
By fateLiangLicense: Apache-2.01 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 3 skill or MCP entries
- Source updated
- Sep 17, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install telegram for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install telegram-3@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/fateLiang/my-claude-pluginsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is external_plugins/telegram/.
Plugin files
├── .claude-plugin/plugin.json├── skills/access/SKILL.md├── skills/configure/SKILL.md└── .mcp.json
Included Skills2
Manage Telegram channel access — approve pairings, edit allowlists, set DM/group policy. Use when the user asks to pair, approve someone, check who's allowed, or change policy for the Telegram channel.
Set up the Telegram channel — save the bot token and review access policy. Use when the user pastes a Telegram bot token, asks to configure Telegram, asks "how do I set this up" or "who can reach me," or wants to check channel status.
MCP servers1
- command
- bun
- args
- run --cwd ${CLAUDE_PLUGIN_ROOT} --shell=bun --silent start
MCP configuration uses runtime-provided plugin path placeholders such as ${PLUGIN_ROOT} or ${CLAUDE_PLUGIN_ROOT}. Review the manifest for the runtime-specific expansion rules.
Plugin manifests1
{
"name": "telegram",
"description": "Telegram channel for Claude Code — messaging bridge with built-in access control. Durable inbound store so messages survive a disconnected session (replayed on restart with a structured replay flag), forward/reply attribution, the sender's highlighted quote, and ask_decision buttons. Manage pairing, allowlists, and policy via /telegram:access.",
"version": "0.0.16",
"keywords": [
"telegram",
"messaging",
"channel",
"mcp"
],
"author": {
"name": "fateLiang",
"url": "https://github.com/fateLiang"
},
"homepage": "https://github.com/fateLiang/my-claude-plugins/tree/main/external_plugins/telegram",
"repository": "https://github.com/fateLiang/my-claude-plugins",
"license": "Apache-2.0"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[telegram on Agent Plugins Marketplace](https://pluginsmp.com/plugins/telegram-3)