Telegram Drive MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TG_API_ID | Yes | Your Telegram API ID from my.telegram.org | |
| TG_SESSION | Yes | Your Telegram session string obtained after the first login | |
| TG_API_HASH | Yes | Your Telegram API hash from my.telegram.org |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| td_list_filesC | List files in a Telegram dialog (Saved Messages, channel, etc.) |
| td_search_filesA | Search for files by filename in a dialog |
| td_get_file_infoC | Get detailed info about a specific file (message with media) |
| td_upload_fileB | Upload a local file to a Telegram dialog |
| td_download_fileB | Download a file from Telegram to a local path |
| td_delete_fileB | Delete a file (message) from a dialog |
| td_forward_fileC | Copy/forward a file from one dialog to another |
| td_bulk_deleteC | Delete multiple files at once |
| td_bulk_forwardB | Forward multiple files to another dialog |
| td_send_messageB | Send a text message to a dialog |
| td_edit_messageC | Edit an existing message |
| td_delete_messagesC | Delete multiple messages at once |
| td_search_messagesB | Search for messages in a dialog |
| td_get_message_historyC | Get message history from a dialog |
| td_list_dialogsA | List all Telegram dialogs (chats, channels, saved messages) |
| td_join_channelA | Join a public Telegram channel or via invite link |
| td_leave_channelB | Leave a Telegram channel |
| td_storage_overviewA | Get storage overview: file counts and sizes per dialog |
| td_get_media_infoB | Get detailed media info (duration, resolution, file type) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
Several tools have overlapping boundaries: delete_file vs delete_messages, get_file_info vs get_media_info, and search_files vs search_messages could easily be confused. Bulk variants also blur the line with their singular counterparts.
Tools consistently use a td_ prefix with a snake_case verb_noun pattern like list_files, upload_file, and join_channel. Minor deviations like bulk_delete, bulk_forward, and storage_overview weaken the pattern slightly.
19 tools is on the heavy side, though most serve distinct file or message operations. The bulk and message-management additions push it into the borderline range for a Telegram Drive server.
Core file lifecycle operations are covered: upload, download, list, search, info, delete, forward, and storage overview. Minor gaps like caption editing, renaming, or file link generation exist but are workable.