Kiro - Telegram MCP Server

Telegram is where many developer communities actually operate. Questions, feedback, links, event updates, and scheduled announcements often live inside fast-moving chats and channels. I wanted Kiro to help with that workflow without giving it unsafe direct control over Telegram.

So I built a Telegram MCP server for Kiro using Node.js, TypeScript, GramJS, and the Model Context Protocol.

The MCP lets Kiro read selected Telegram chats, search recent or cached messages, summarize conversations, extract links, find unanswered questions, inspect reactions and polls, and manage scheduled channel messages. It also supports useful actions like sending replies, scheduling posts, forwarding messages, pinning announcements, and marking chats as read.

The important part is safety. Telegram is sensitive, so every write action is confirmation-gated. Safe mode requires the exact outgoing text to be repeated before sending. Media sends also require the file path to be confirmed. Optional allowed chat IDs can restrict write tools to only approved chats or channels.

The project stores the Telegram session locally, keeps the cache in a local SQLite database, and avoids committing secrets. The npm package only includes the compiled server, examples, README, license, and `.env.example`.

A typical Kiro MCP config looks like this:

```json
{
"mcpServers": {
"telegram": {
"command": "kiro-telegram-mcp",
"env": {
"TELEGRAM_API_ID": "${TELEGRAM_API_ID}",
"TELEGRAM_API_HASH": "${TELEGRAM_API_HASH}",
"KIRO_TELEGRAM_SAFE_MODE": "true"
}
}
}
}