Telegram MCP (chaindead): MCP server, setup and security

What Telegram MCP (chaindead) does

According to its repository: “Telegram API integration: access user data, manage dialogs (chats, channels, groups), retrieve messages and handle read status.”

An MCP server gives an AI agent extra tools it calls during the conversation: the agent reads their description, decides to use them and gets the result back. Telegram MCP (chaindead) is listed under Messaging and email, a category of 107 servers in the directory, where it ranks #16 by stars.

Topics declared by the repository: telegram, mtproto, telegram-api.

Installing and connecting Telegram MCP (chaindead)

No package or remote server is declared in the official MCP registry: you install it from source, following the repository README.

Like any MCP server, you declare it in your client's configuration (Claude Desktop, Claude Code, Cursor, VS Code, Codex…): a name, the command that starts it or its URL, and any environment variables. The client then starts it and lists its tools. Project language: Go.

Security: what to check

An MCP server runs code with the rights you give it, and the model reads its tool descriptions: a malicious or compromised server can hijack the agent. Read the code, or pick a maintained and widely used server, before connecting it.

None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to Telegram MCP (chaindead). That does not replace reading the code.

Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.

Project activity and maintenance

Created on April 1, 2025, the chaindead/telegram-mcp repository has 349 stars and 60 forks, with 5 open issues. It has more stars than 84% of the servers in the directory. Last change 5 months ago.

Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.