This MCP server is feature-rich, offering 80+ tools covering Telegram messaging, groups, media, contacts, and admin functions. It requires a user-level session string, so permissions are broad; users should store credentials carefully. The project includes security measures (e.g., read-only mode, path restrictions, prompt injection protections), but risks remain. Installation must be done via cloning or Git install to avoid the PyPI package of the same name.
Strongest · Documentation 17/20 Weakest · Reliability 9/20
Static review · not runListed 2026-08-07
Read the FMRS scoring method →Runtime：Python 3.10+ · Docker · Node.js
TELEGRAM_API_ID
Telegram API ID from my.telegram.org/apps; required.
TELEGRAM_API_HASH
Telegram API hash obtained together with the API ID at my.telegram.org/apps; secret credential.
TELEGRAM_SESSION_STRING
Authorized session string generated with the repo's session_string_generator.py; grants account access, keep secret.
TELEGRAM_SESSION_STRING_WORK
Optional; session string for the 'work' account in multi-account mode.
TELEGRAM_SESSION_STRING_PERSONAL
Optional; session string for the 'personal' account in multi-account mode.
TELEGRAM_SESSION_STRINGS
Optional; multiple session strings (session pool) so several clients can share one account.
TELEGRAM_PROXY_PASSWORD
Optional; proxy authentication password; secret credential.
TELEGRAM_PROXY_SECRET
Optional; MTProxy secret required for mtproxy proxies; secret credential.
TELEGRAM_EXPOSED_TOOLS
Optional; set to read-only to expose only read-only tools, or read-only+tool names to add specific write tools.
TELEGRAM_CONTACT_FUZZY
Optional; set to 0 to disable fuzzy suggestions for contact aliases.
TELEGRAM_ALIASES_FILE
Optional; overrides the path of the contact aliases storage file.
TELEGRAM_EVENT_FEED
Optional; set to 1 to auto-enable the incoming event feed (callback mode).
TELEGRAM_EVENT_FEED_FILE
Optional; overrides the path of the incoming feed JSONL file.
TELEGRAM_SESSION_NAME
Optional; fallback session identifier (file session name).
TELEGRAM_DEVICE_MODEL
Optional; device model name shown under Telegram Settings > Devices.
TELEGRAM_SYSTEM_VERSION
Optional; system version shown in the devices list.
TELEGRAM_APP_VERSION
Optional; app version shown in the devices list.
TELEGRAM_PROXY_TYPE
Optional; proxy type: socks5, socks4, http, or mtproxy.
TELEGRAM_PROXY_HOST
Optional; proxy server host.
TELEGRAM_PROXY_PORT
Optional; proxy server port.
TELEGRAM_PROXY_USERNAME
Optional; proxy authentication username.
TELEGRAM_PROXY_RDNS
MCP_TRANSPORT
Optional; MCP transport: stdio (default), http, or sse.
MCP_HOST
Optional; bind address for http/sse transports, default 127.0.0.1.
MCP_PORT
Optional; port for http/sse transports, default 8765.
MCP_ALLOWED_HOSTS
Optional; allowed Host headers to enable DNS-rebinding protection.
MCP_ALLOWED_ORIGINS
Optional; allowed Origin list.
TELEGRAM_ALLOW_SERVER_ROOTS_FALLBACK
Optional; set to 1 to fall back to server CLI roots when client Roots are empty or fail.
git clone https://github.com/chigwell/telegram-mcp.git && cd telegram-mcp && uv sync.uv run session_string_generator.py --qr (recommended) or --phone.uv run main.py, or configure your MCP client with uv --directory /path/to/telegram-mcp run main.py and the environment variables.{
"mcpServers": {
"telegram-mcp": {
"command": "uv",
"args": [
"--directory",
"/full/path/to/telegram-mcp",
"run",
"main.py"
],
"env": {
"TELEGRAM_API_ID": "your_api_id_here",
"TELEGRAM_API_HASH": "your_api_hash_here",
"TELEGRAM_SESSION_STRING": "your_session_string_here"
}
}
}
}
Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.
{
"servers": {
"telegram-mcp": {
"command": "uv",
"args": [
"--directory",
"/full/path/to/telegram-mcp",
"run",
"main.py"
],
"env": {
"TELEGRAM_API_ID": "your_api_id_here",
"TELEGRAM_API_HASH": "your_api_hash_here",
"TELEGRAM_SESSION_STRING": "your_session_string_here"
}
}
}
}
Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).
claude mcp add telegram-mcp -e TELEGRAM_API_ID=your_api_id_here -e TELEGRAM_API_HASH=your_api_hash_here -e TELEGRAM_SESSION_STRING=your_session_string_here -- uv --directory /full/path/to/telegram-mcp run main.py
Run it in a terminal; replace any <…> placeholders with your own values first.
After configuring the server in your MCP client and restarting, tools such as list_accounts and get_me should appear in the client's tool list; calling get_me and getting your Telegram account info back confirms the connection works.
Once connected, you can ask your AI assistant things like:
No matching tools
Listed from the project's documentation, not tested by this site.
telegram-mcp is a Model Context Protocol (MCP) server built on Telethon that provides full Telegram integration for MCP-compatible clients like Claude, Cursor, and Codex. It exposes 80+ tools for managing Telegram accounts, chats, messages, contacts, media, folders, and admin operations. Supports stdio, HTTP, and SSE transports, multi-account setups, proxy support, contact alias memory, read-only mode, file path security, Docker deployment, and prompt injection protections.
MCP server providing web search and content fetching via DuckDuckGo
Your AI never forgets again.
Official MCP server for Hostinger API.
Utilize Figma's rich data in your coding agent. Implement designs in Flutter way!
Source revision 091017028552 Data synced 2026-10-11 Read the FMRS scoring method