How Chatroost accesses Telegram
Last updated: September 30, 2026
Chatroost is an unofficial client for Telegram. It is not a bot and it does not scrape Telegram: each person signs in to their own Telegram account, and the assistant they connect works only with that account. This page explains how the access works, what Chatroost adds on top of Telegram's API, and how it follows Telegram's rules for third-party apps.
How access works
- Telegram's public client API — Chatroost talks to Telegram through MTProto, the API Telegram publishes for third-party apps. Telegram invites developers to build clients on it free of charge, as long as they follow its API Terms of Service. Chatroost uses its own registered application ID, as those terms require.
- Your own account, signed in by you — You connect by scanning a QR code with the Telegram app, the same way you link Telegram Desktop. The connection shows up in Telegram under Settings → Devices, and you can end it there at any moment.
- Only what your account can see — The assistant sees the same chats and channels your Telegram app shows you, and nothing more. There are no shared accounts and no access to accounts that have not signed in.
- Only when you ask — A tool runs when the assistant you connected calls it for your request. Chatroost does not act on a schedule of its own.
What Chatroost adds on top of the API
- Clear labels on every tool — Every tool has a name, a title and a label that says whether it only reads, changes something, or does something that cannot be undone. AI clients use these labels to ask you before a tool acts.
- Irreversible actions off by default — Deleting messages, leaving groups, banning members and similar actions stay off until you switch them on in your settings. Even then they are limited to 20 a day, and every attempt is recorded in a log you can read.
- Confirmation before sending — The Chatroost skills for Claude and ChatGPT tell the assistant to show you the exact text and the recipient, and to wait for your approval before it sends a message.
- Limits that protect your account — Requests are rate-limited for each connection, and when Telegram asks a client to slow down, Chatroost waits instead of retrying at once. An assistant stuck in a loop cannot flood Telegram from your account.
- Nothing kept — Messages pass from Telegram to your assistant and are not stored or logged. The server keeps only what it needs to stay connected; the privacy policy lists exactly what that is.
- Open source — The server is open source under the MIT license, so anyone can check these claims or run their own copy: github.com/mcp-telegram/mcp-telegram-cloud.
How Chatroost follows Telegram's API terms
Telegram's API Terms of Service set the rules for every third-party client. These are the points that matter most for an AI connector:
- Actions only with your knowledge — Telegram forbids clients from acting for a user without the user's knowledge and consent. Chatroost acts only on requests from the assistant you connected, tools that change something are labelled as such, and irreversible ones need your opt-in.
- No AI training — Chatroost does not use Telegram data to train or fine-tune any model, and it does not collect or aggregate message content.
- Clear naming — The app's name does not contain the word Telegram, and the app does not use the Telegram logo. It is described everywhere as an unofficial client for Telegram that is not affiliated with Telegram.
- Your privacy — Chatroost reaches Telegram only through the session you created, deletes that session when you disconnect, and you can always end it from Telegram itself.
For app directory reviewers
Chatroost owns and operates its server at mcp-telegram.com and this website. The Telegram API is a third-party API that Chatroost does not control. It is used under Telegram's public terms for client apps, and each user authorizes access to their own account. Questions: GitHub Issues.