Claude Connectors for Telegram: Options and Boundaries

There is no official Telegram connector in Claude's standard connector settings, but Claude can interact with Telegram through Telegram's Bot API — a well-documented interface that lets applications send and receive messages in groups and channels where a bot has been added. The distinction between reading messages and sending them matters: reading is lower risk, sending is an action that reaches real people. Understanding that boundary, and recording which actions you have approved, keeps the workflow safe. Tools like fenbs preserve approved actions and shared context from the work between sessions.

Check Claude's connector settings for any current Telegram option. If nothing appears, the Bot API route described below is the practical path. For Telegram's current Bot API documentation, see Telegram's developer reference↗ (opens in a new tab).

How Claude can interact with Telegram

Telegram's Bot API lets a bot read messages in any chat where it has been added, and send messages to those same chats. To connect Claude to Telegram, you create a Telegram bot using BotFather, which issues a bot token. That token can be exposed to Claude through an MCP server that wraps the Bot API.

A Claude MCP server for Telegram would give Claude tools like "read recent messages from a channel" or "send a message to a group." You configure which chats the bot can access by adding the bot to those chats. The bot only sees messages from chats it is in — it cannot read private conversations between people who have not added it.

Reading messages versus sending them

Reading Telegram messages lets Claude summarize a channel, answer questions about recent discussions, or monitor updates without anyone else knowing the AI is involved. Sending messages is a different action: it creates a visible record in the chat, may notify members, and reflects on whoever controls the bot.

Before giving Claude the ability to send messages to a Telegram chat, decide: does every send need a person to approve the draft first? In most professional or customer-facing contexts, the answer is yes. A message that goes to a live group cannot be unsent after people have read it.

A useful middle ground is read-only access first. Claude reads the channel to summarize discussions, surface items that need follow-up, or monitor for specific mentions. Sending messages stays with a person. This keeps Claude in a supporting role without giving it the ability to post directly to a live channel — a boundary that is easy to maintain and easy to explain to other channel members.

Setting up a Telegram bot for Claude

1. Open Telegram and start a conversation with BotFather. Use the /newbot command to create a bot and receive its API token.
2. Add the bot to the Telegram chats or channels it needs to access.
3. Configure an MCP server with the bot token, exposing only the actions Claude needs: reading messages, sending to specific chats.
4. Store the bot token as an environment variable, not in a config file that could be committed to source control.
5. Test the bot in a private test group before adding it to any live channel.

For Claude Code, add the MCP server configuration to your Claude Code settings file. For Claude chat, check whether an MCP-based Telegram integration is available through Claude's connector settings or a community integration.

What Claude cannot access in Telegram

A Telegram bot — and by extension Claude through a bot — cannot read private one-on-one conversations between users, conversations in groups or channels it has not been added to, or the message history from before the bot was added to a chat. This is a deliberate privacy limit in Telegram's design.

The Bot API also does not give access to contacts, profile information, or any data outside the chats the bot is a member of. Claude through a Telegram bot has a narrowly scoped view of Telegram, not a broad view of anyone's account.

Recording approved actions

When Claude sends a message to a Telegram channel, that action should be traceable: who approved the send, what the message said, and when it was sent. For low-stakes automated messages, this might be a log. For customer-facing or public-channel messages, a formal approval step and a record of each decision is worth the extra step.

How to do this with fenbs

1. Create a free account and add a project for the Telegram channel or group work.
2. Record which Telegram actions are approved: reading only, sending to specific chats, and under what conditions.
3. Add a standing rule if any send must be reviewed by a person before Claude sends it.
4. Connect your AI via Integrations so it reads the approved actions before working with the Telegram bot.
5. After each session, save progress: what was read, what was sent, what is waiting for a person to review.

For a broader look at Claude connector types, see Claude Connectors Explained. For how OAuth works in Claude connectors, see Claude Connectors and OAuth. More connector guides are in the connect-ai topic.