Set up the Telegram plugin for Claude Code
Create a Telegram bot, install Anthropic's official plugin, and configure access control via pairing or an allowlist.
- Skill Road
- Set up the Telegram plugin for Claude Code
Published on 24.09.2026
This guide sets up Anthropic's official Telegram plugin for Claude Code through the documented marketplace route. Before relying on it in production, review the full [README](https://github.com/anthropics/claude-plugins-official/tree/main/external_plugins/telegram) and the [access control documentation](https://github.com/anthropics/claude-plugins-official/blob/main/external_plugins/telegram/ACCESS.md) in the repository.
Check the prerequisites
The plugin requires a current version of Claude Code (check with claude --version) and the Bun JavaScript runtime. If Bun is missing, install it with curl -fsSL https://bun.sh/install | bash.
Create a Telegram bot
In Telegram, message [@BotFather](https://t.me/BotFather) with the command /newbot, choose a display name, and pick a unique username ending in "bot". @BotFather returns a token in the format 123456789:AAHfiqksKZ8..., which you'll need in the next step.
Install and configure the plugin
In Claude Code, run these commands in order:
/plugin install telegram@claude-plugins-official
/telegram:configure [TOKEN]
claude --channels plugin:telegram@claude-plugins-officialReplace [TOKEN] with the token you received from @BotFather. The third command starts Claude Code with the Telegram channel active.
Grant access
Send the bot a direct message; it replies with a six-digit pairing code. Enter it in Claude Code with /telegram:access pair [CODE] to pair yourself. For team setups, use a maintained allowlist instead via /telegram:access allow <ID>; groups stay disabled by default and can be enabled individually with /telegram:access group add <ID>.
Keep security in mind
Choose the access policy deliberately to match your use case: pairing for personal use, a maintained allowlist for multiple participants, or /telegram:access policy disabled to lock the channel entirely for a while. Because a connected bot can potentially trigger far-reaching actions in the running Claude Code session, the access.json configuration under ~/.claude/channels/telegram/ deserves a periodic review, especially before enabling new groups.
Frequently asked questions
Is the Telegram plugin actually official from Anthropic?
Yes. It lives in the official, Anthropic-maintained claude-plugins-official repository and carries an "Anthropic verified" badge on its marketplace page at claude.com/plugins/telegram.
How does it differ from the separately listed Telegram MCP server?
This plugin is Anthropic's own solution built into Claude Code, specifically for a personal bot channel. The separately listed Telegram MCP server is an independent third-party project for general Telegram access outside Claude Code.
Does the plugin cost anything?
No, the plugin's source code and use are free under the Apache-2.0 license per the repository. Claude Code itself may carry its own costs depending on the plan chosen.
Can any Telegram user control the bot immediately?
No. In the default "pairing" mode, every new sender must first be approved via a six-digit code entered in the Claude Code terminal; unauthorized messages are dropped or ignored.
Does the plugin work in Telegram groups too?
Yes, but groups are disabled by default and must be enabled individually via /telegram:access group add. There, by default, the bot only responds to @-mentions or direct replies.