overpod/mcp-telegram

What's new

Docker support

Self-host mcp-telegram with the official multi-stage alpine Dockerfile. ~50MB image, no bloat.

Build:

docker build -t mcp-telegram https://github.com/overpod/mcp-telegram.git

Login (once, interactive):

docker run -it --rm \
  -e TELEGRAM_API_ID=YOUR_ID \
  -e TELEGRAM_API_HASH=YOUR_HASH \
  -v ~/.mcp-telegram:/root/.mcp-telegram \
  --entrypoint node mcp-telegram dist/qr-login-cli.js

Run as MCP server:

docker run -i --rm \
  -e TELEGRAM_API_ID=YOUR_ID \
  -e TELEGRAM_API_HASH=YOUR_HASH \
  -v ~/.mcp-telegram:/root/.mcp-telegram \
  mcp-telegram

Non-blocking startup

MCP server now starts immediately and connects to Telegram in the background. Previously, slow session loads or network issues could delay the server becoming available.

Local QR fallback

QR login code is now saved to ~/.mcp-telegram/qr-login.png as a local fallback. Removed the previous api.qrserver.com remote fallback — no login data ever leaves your machine.

Security

• sessionDir getter added to TelegramService for clean path resolution
• Explicit note in README: all MTProto communication goes directly to Telegram, no third-party services

Thanks to @andrejbestuzhev for the original PR #3 with the Docker, non-blocking startup, and privacy ideas!