The server is a bridge between the Telegram API and the AI assistants and is based on the Model Context Protocol.
telegram-mcp is an MCP project maintained in the chaindead/telegram-mcp repository. The maintainer describes its purpose as “The server is a bridge between the Telegram API and the AI assistants and is based on the Model Context Protocol”. Read the project documentation for the complete scope.
The documented npm package is @chaindead/telegram-mcp. The configuration below comes from the maintainer’s example; adapt its paths and account values to your environment.
The example declares TG_APP_ID, TG_API_HASH. Secret-looking values have been replaced with placeholders. Required and optional labels are shown only when the documentation states them.
Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.
{
"mcpServers": {
"telegram": {
"command": "npx",
"args": [
"-y",
"@chaindead/telegram-mcp"
],
"env": {
"TG_APP_ID": "<your-api-id>",
"TG_API_HASH": "<your-api-hash>"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| TG_APP_ID | Declared in the maintainer’s client configuration. | Check documentation |
| TG_API_HASH | Declared in the maintainer’s client configuration. | Check documentation |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Official MCP server for Sequenzy, the AI-powered email marketing platform.
Voice Calls, SMS, and WhatsApp for Claude Code with cross-channel context sharing.
Connect AI agents to Marvenn for outbound growth via email, voice, and LinkedIn.
MCP server for MTS Exolve — SMS, calls, recordings, Viber messaging (Russia)